https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
--- Comment #5 from Andrey V. Elsukov <a...@freebsd.org> --- (In reply to Mike Andrews from comment #0) > 12:46:22.835272 00:25:90:57:21:b3 > 00:25:90:23:be:bc, ethertype IPv6 > (0x86dd), length 232: fdfa::fafa:d53a.53 > fdfa::fafa:d53b.15484: 47157* > 1/2/4 A 64.191.171.200 (170) > 12:46:27.836186 00:25:90:38:6f:fa > 00:25:90:57:21:b3, ethertype IPv6 > (0x86dd), length 92: fdfa::fafa:d53b.39323 > fdfa::fafa:d53a.53: 47157+ A? > www.fark.com. (30) > 12:46:27.836340 00:25:90:57:21:b3 > 00:25:90:23:be:bc, ethertype IPv6 > (0x86dd), length 232: fdfa::fafa:d53a.53 > fdfa::fafa:d53b.39323: 47157* > 1/2/4 A 64.191.171.200 (170) > > 00:50:90:23:be:bc is a totally different 3rd machine. That's.... weird. :) > > Add the -T flag to the "host" command to force TCP, and it works. > > Flip the queries around so that machine 1 queries machine 2, and it works. > > I'm seeing similar issues with other similar machines (and similar hardware, > all Supermicro machines with Intel em nics of varying vintage) that have > been updated to 11.0-RC1. All ware fine on 10.3-RELEASE. The only > em-specific tweak I've got is "-tso", but turning tso back on doesn't change > behavior any. Can you check `ndp -an` on the problematic machine at the time when you see wrong addresses? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
