From owner-freebsd-net@freebsd.org Thu Jul 6 11:31:26 2017 Return-Path: Delivered-To: freebsd-net@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 B081BDAB104 for ; Thu, 6 Jul 2017 11:31:26 +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 93FE767221 for ; Thu, 6 Jul 2017 11:31:26 +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 v66BVQoV066450 for ; Thu, 6 Jul 2017 11:31:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 176671] [epair] MAC address for epair device not unique Date: Thu, 06 Jul 2017 11:31:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: olivier@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 11:31:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 --- Comment #6 from Olivier Cochard --- I've reach to reproduce a setup when this localy-unique epair create confli= ct on a LAN: +----------------+ +---------------+ | ServerA | | serverB | | bridge0 - em0 |- LAN -| em0 - bridge0 | | | | | | | | epair1a | | epair1a | | epair1b | | epair1b | | | | | | | | vnetjail1 | | vnetjail2 | +----------------+ +---------------+ MAC addresses of epair1 are the same on both jail, then they can't communic= ate each others: [root@jail1]~# ifconfig epair1b ether epair1b: flags=3D8943 metri= c 0 mtu 1500 options=3D8 ether 02:ff:70:00:0f:0b hwaddr 02:ff:70:00:0f:0b [root@jail2]~# ifconfig epair1b ether epair1b: flags=3D8943 metri= c 0 mtu 1500 options=3D8 ether 02:ff:70:00:0f:0b hwaddr 02:ff:70:00:0f:0b We could perhaps generate a MAC field "eaddr[1]" (in if_epair.c) from the hostid for mitigate this conflict (like the net/if_bridge.c code) ? But if we take code from if_bridge, we should create a common function for being available to if_bridge and if_epair. --=20 You are receiving this mail because: You are the assignee for the bug.=