From: Satadru Pramanik <satadru@gmail.com>
To: Rich Felker <dalias@aerifal.cx>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Re: musl getaddr info breakage on older kernels
Date: Thu, 17 Feb 2022 08:30:47 -0500 [thread overview]
Message-ID: <CAFrh3J9Z2s-4iMm97n6qNLs3LO_SSybjCz4yE9XqS9iJsQn=KA@mail.gmail.com> (raw)
In-Reply-To: <20220217132434.GP7074@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 8849 bytes --]
*This is a failure:*
tcpdump -i any -vvv host 192.168.0.115
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture
size 262144 bytes
08:29:38.043849 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.60625 > office.lan.53: [udp sum ok] 0+ A? google.com. (28)
08:29:38.044237 IP (tos 0x0, ttl 64, id 11463, offset 0, flags [DF], proto
UDP (17), length 72)
office.lan.53 > 192.168.0.115.60625: [bad udp cksum 0x820a -> 0x5c7d!]
0 q: A? google.com. 1/0/0 google.com. [2m15s] A 142.250.80.110 (44)
08:29:38.047754 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.60625 > office.lan.53: [udp sum ok] 0+ AAAA? google.com.
(28)
08:29:38.048078 IP (tos 0x0, ttl 64, id 11464, offset 0, flags [DF], proto
UDP (17), length 84)
office.lan.53 > 192.168.0.115.60625: [bad udp cksum 0x8216 -> 0xb42f!]
0 q: AAAA? google.com. 1/0/0 google.com. [4m26s] AAAA
2607:f8b0:4006:80d::200e (56)
08:29:38.048955 IP (tos 0xc0, ttl 64, id 59728, offset 0, flags [none],
proto ICMP (1), length 112)
192.168.0.115 > office.lan: ICMP 192.168.0.115 udp port 60625
unreachable, length 92
IP (tos 0x0, ttl 64, id 11464, offset 0, flags [DF], proto UDP
(17), length 84)
office.lan.53 > 192.168.0.115.60625: [udp sum ok] 0 q: AAAA? google.com.
1/0/0 google.com. [4m26s] AAAA 2607:f8b0:4006:80d::200e (56)
08:29:39.476101 IP (tos 0x0, ttl 64, id 12690, offset 0, flags [DF], proto
TCP (6), length 52)
192.168.0.115.51204 > lga34s35-in-f3.1e100.net.80: Flags [.], cksum
0xa666 (correct), seq 1466707759, ack 3358943837, win 115, options
[nop,nop,TS val 198422160 ecr 2351261566], length 0
08:29:39.478914 IP (tos 0x80, ttl 122, id 6227, offset 0, flags [none],
proto TCP (6), length 52)
lga34s35-in-f3.1e100.net.80 > 192.168.0.115.51204: Flags [.], cksum
0xa5b7 (correct), seq 1, ack 1, win 282, options [nop,nop,TS val 2351306585
ecr 198377148], length 0
^C
7 packets captured
7 packets received by filter
0 packets dropped by kernel
*Two successes and one failure:*
# tcpdump -i any -vvv host 192.168.0.115
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture
size 262144 bytes
08:28:16.906114 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.34033 > office.lan.53: [udp sum ok] 0+ A? google.com. (28)
08:28:16.906243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.34033 > office.lan.53: [udp sum ok] 0+ AAAA? google.com.
(28)
08:28:16.906512 IP (tos 0x0, ttl 64, id 8977, offset 0, flags [DF], proto
UDP (17), length 72)
office.lan.53 > 192.168.0.115.34033: [bad udp cksum 0x820a -> 0xc40b!]
0 q: A? google.com. 1/0/0 google.com. [3m37s] A 142.250.80.110 (44)
08:28:16.906696 IP (tos 0x0, ttl 64, id 8978, offset 0, flags [DF], proto
UDP (17), length 84)
office.lan.53 > 192.168.0.115.34033: [bad udp cksum 0x8216 -> 0x1d02!]
0 q: AAAA? google.com. 1/0/0 google.com. [5s] AAAA 2607:f8b0:4006:820::200e
(56)
08:28:19.257368 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.53048 > office.lan.53: [udp sum ok] 0+ A? google.com. (28)
08:28:19.257466 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.53048 > office.lan.53: [udp sum ok] 0+ AAAA? google.com.
(28)
08:28:19.257680 IP (tos 0x0, ttl 64, id 9078, offset 0, flags [DF], proto
UDP (17), length 72)
office.lan.53 > 192.168.0.115.53048: [bad udp cksum 0x820a -> 0x79c7!]
0 q: A? google.com. 1/0/0 google.com. [3m34s] A 142.250.80.110 (44)
08:28:19.257849 IP (tos 0x0, ttl 64, id 9079, offset 0, flags [DF], proto
UDP (17), length 84)
office.lan.53 > 192.168.0.115.53048: [bad udp cksum 0x8216 -> 0xd2bd!]
0 q: AAAA? google.com. 1/0/0 google.com. [2s] AAAA 2607:f8b0:4006:820::200e
(56)
08:28:20.354244 IP (tos 0x0, ttl 64, id 52155, offset 0, flags [DF], proto
TCP (6), length 52)
192.168.0.115.53400 > lga34s35-in-f4.1e100.net.443: Flags [.], cksum
0xf854 (correct), seq 2594363947, ack 50065344, win 135, options
[nop,nop,TS val 198343040 ecr 3566225862], length 0
08:28:20.358922 IP (tos 0x0, ttl 122, id 3787, offset 0, flags [none],
proto TCP (6), length 52)
lga34s35-in-f4.1e100.net.443 > 192.168.0.115.53400: Flags [.], cksum
0xa7b0 (correct), seq 1, ack 1, win 276, options [nop,nop,TS val 3566270916
ecr 198252953], length 0
08:28:20.482219 IP (tos 0x0, ttl 64, id 27145, offset 0, flags [DF], proto
TCP (6), length 52)
192.168.0.115.54184 > bc-in-f188.1e100.net.5228: Flags [.], cksum
0x4e35 (correct), seq 2783933939, ack 881888313, win 249, options
[nop,nop,TS val 198343168 ecr 855506216], length 0
08:28:20.492954 IP (tos 0x0, ttl 59, id 49690, offset 0, flags [none],
proto TCP (6), length 52)
bc-in-f188.1e100.net.5228 > 192.168.0.115.54184: Flags [.], cksum
0xfdcb (correct), seq 1, ack 1, win 274, options [nop,nop,TS val 855551371
ecr 198253037], length 0
08:28:20.860748 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.49427 > office.lan.53: [udp sum ok] 0+ A? google.com. (28)
08:28:20.860857 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP
(17), length 56)
192.168.0.115.49427 > office.lan.53: [udp sum ok] 0+ AAAA? google.com.
(28)
08:28:20.861401 IP (tos 0x0, ttl 64, id 9095, offset 0, flags [DF], proto
UDP (17), length 72)
office.lan.53 > 192.168.0.115.49427: [bad udp cksum 0x820a -> 0x87ed!]
0 q: A? google.com. 1/0/0 google.com. [3m33s] A 142.250.80.110 (44)
08:28:20.861738 IP (tos 0x0, ttl 64, id 9096, offset 0, flags [DF], proto
UDP (17), length 84)
office.lan.53 > 192.168.0.115.49427: [bad udp cksum 0x8216 -> 0xe0e3!]
0 q: AAAA? google.com. 1/0/0 google.com. [1s] AAAA 2607:f8b0:4006:820::200e
(56)
08:28:20.862682 IP (tos 0xc0, ttl 64, id 59726, offset 0, flags [none],
proto ICMP (1), length 112)
192.168.0.115 > office.lan: ICMP 192.168.0.115 udp port 49427
unreachable, length 92
IP (tos 0x0, ttl 64, id 9096, offset 0, flags [DF], proto UDP (17),
length 84)
office.lan.53 > 192.168.0.115.49427: [udp sum ok] 0 q: AAAA? google.com.
1/0/0 google.com. [1s] AAAA 2607:f8b0:4006:820::200e (56)
08:28:21.985759 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
192.168.0.115 tell office.lan, length 28
08:28:22.133507 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.0.115
is-at 20:68:9d:0f:33:44 (oui Unknown), length 46
^C
19 packets captured
19 packets received by filter
0 packets dropped by kernel
On Thu, Feb 17, 2022 at 8:24 AM Rich Felker <dalias@aerifal.cx> wrote:
> On Thu, Feb 17, 2022 at 08:17:36AM -0500, Satadru Pramanik wrote:
> > Looks like reverting that commit works, but interestingly, only
> > stochastically.
> >
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > getaddrinfo: Try again
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > getaddrinfo: Try again
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > getaddrinfo: Try again
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > getaddrinfo: Try again
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > getaddrinfo: Try again
> > chronos@localhost
> > /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> > ../musl_getaddrinfo_test google.com
> > AF_INET6: 2607:f8b0:4006:81c::200e
> > AF_INET: 142.250.80.46
>
> Can you tcpdump these again and see if there's network traffic when it
> fails? This sounds more like the nameserver being unreliable.
>
[-- Attachment #2: Type: text/html, Size: 11501 bytes --]
next prev parent reply other threads:[~2022-02-17 13:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFrh3J9CK67S=Jn531zTK04QeR8yiZwro_ZThQD=3aUx5XghCA@mail.gmail.com>
2022-02-06 21:30 ` Rich Felker
2022-02-06 23:25 ` Satadru Pramanik
2022-02-06 23:44 ` Rich Felker
2022-02-07 1:29 ` Satadru Pramanik
2022-02-07 2:40 ` Rich Felker
2022-02-07 19:19 ` Satadru Pramanik
2022-02-07 21:02 ` Rich Felker
2022-02-14 17:24 ` Satadru Pramanik
2022-02-14 18:29 ` Rich Felker
2022-02-14 19:00 ` Satadru Pramanik
2022-02-14 22:00 ` Rich Felker
2022-02-15 16:59 ` Satadru Pramanik
2022-02-15 17:44 ` Rich Felker
2022-02-15 22:56 ` Satadru Pramanik
2022-02-16 1:41 ` Rich Felker
2022-02-16 18:37 ` Satadru Pramanik
2022-02-16 18:44 ` Satadru Pramanik
2022-02-16 21:33 ` Rich Felker
2022-02-16 21:53 ` Satadru Pramanik
2022-02-17 1:44 ` Satadru Pramanik
2022-02-17 4:14 ` Satadru Pramanik
2022-02-17 13:17 ` Satadru Pramanik
2022-02-17 13:24 ` Rich Felker
2022-02-17 13:30 ` Satadru Pramanik [this message]
2022-02-17 13:46 ` Rich Felker
2022-02-17 14:49 ` Satadru Pramanik
2022-02-17 15:53 ` Rich Felker
2022-02-17 16:05 ` Rich Felker
2022-02-17 16:36 ` Satadru Pramanik
2022-02-17 18:17 ` Rich Felker
2022-02-17 21:39 ` Satadru Pramanik
2022-02-17 21:42 ` Satadru Pramanik
[not found] ` <CAFrh3J9CBGagzmnn9E7W0H15iiOzZEtg4YKfJ1qRwCtrjnw6tA@mail.gmail.com>
2022-02-17 21:43 ` Fwd: " Satadru Pramanik
2022-02-17 22:48 ` Rich Felker
2022-02-18 1:25 ` Satadru Pramanik
2022-02-17 16:17 ` Satadru Pramanik
2022-02-07 5:35 ` Markus Wichmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFrh3J9Z2s-4iMm97n6qNLs3LO_SSybjCz4yE9XqS9iJsQn=KA@mail.gmail.com' \
--to=satadru@gmail.com \
--cc=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).