From owner-freebsd-amd64@freebsd.org Mon Aug 15 16:54:29 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C63A6BBBBA0 for ; Mon, 15 Aug 2016 16:54:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B5D24170C for ; Mon, 15 Aug 2016 16:54:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u7FGsT9E071477 for ; Mon, 15 Aug 2016 16:54:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 211872] IPv6 UDP traffic sometimes sent using wrong mac address Date: Mon, 15 Aug 2016 16:54:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mandrews@bit0.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 15 Aug 2016 17:27:53 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Aug 2016 16:54:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211872 Bug ID: 211872 Summary: IPv6 UDP traffic sometimes sent using wrong mac address Product: Base System Version: 11.0-RC1 Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: mandrews@bit0.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Outbound IPv6 UDP traffic sometimes appears to put packets on the wire with= the destination MAC address of a completely different system. "ndp -a" shows correct MAC addresses. Example: Two nameservers, trying to query each other, on IPv6 private addresses (fc00::/10) fdfa::fafa:d53a, mac 00:25:90:57:21:b3 fdfa::fafa:d53b, mac 00:25:90:38:6f:fa These are lagg0 interfaces aggregating two Intel em nics. On each machine, run: tcpdump -e -n net fdfa::/16 and port 53 On machine 2, run "host -t a www.fark.com fdfa::fafa:d53a" and it will time= out, with its own tcpdump showing: 12:46:22.835604 00:25:90:38:6f:fa > 00:25:90:57:21:b3, ethertype IPv6 (0x86= dd), length 92: fdfa::fafa:d53b.15484 > fdfa::fafa:d53a.53: 47157+ A? www.fark.c= om. (30) 12:46:27.836716 00:25:90:38:6f:fa > 00:25:90:57:21:b3, ethertype IPv6 (0x86= dd), length 92: fdfa::fafa:d53b.39323 > fdfa::fafa:d53a.53: 47157+ A? www.fark.c= om. (30) and machine 1's tcpdump showing a wrong MAC address used in the replies: 12:46:22.835118 00:25:90:38:6f:fa > 00:25:90:57:21:b3, ethertype IPv6 (0x86= dd), length 92: fdfa::fafa:d53b.15484 > fdfa::fafa:d53a.53: 47157+ A? www.fark.c= om. (30) 12:46:22.835272 00:25:90:57:21:b3 > 00:25:90:23:be:bc, ethertype IPv6 (0x86= dd), 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 (0x86= dd), length 92: fdfa::fafa:d53b.39323 > fdfa::fafa:d53a.53: 47157+ A? www.fark.c= om. (30) 12:46:27.836340 00:25:90:57:21:b3 > 00:25:90:23:be:bc, ethertype IPv6 (0x86= dd), 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 be= en 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 a= ny. Another weird and possibly related issue: "ndp -c" fails on machine 1 -- it deletes one or two entries and then stops with "ndp: writing to routing soc= ket: Operation not permitted". On machine 2, "ndp -c" completes with no problem= s. I haven't yet tried dropping the lagg interface and using the em interfaces directly. --=20 You are receiving this mail because: You are on the CC list for the bug.=