Date: Thu, 06 Jul 2017 11:31:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 176671] [epair] MAC address for epair device not unique Message-ID: <bug-176671-2472-VmaDYsy9Gc@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-176671-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-176671-2472@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 --- Comment #6 from Olivier Cochard <olivier@freebsd.org> --- 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<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metri= c 0 mtu 1500 options=3D8<VLAN_MTU> ether 02:ff:70:00:0f:0b hwaddr 02:ff:70:00:0f:0b [root@jail2]~# ifconfig epair1b ether epair1b: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metri= c 0 mtu 1500 options=3D8<VLAN_MTU> 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-176671-2472-VmaDYsy9Gc>