Date: Wed, 15 Jun 2016 15:01:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 207701] vlan interface over failover lagg has empty/00:00:00:00:00:00 mac/ether address Message-ID: <bug-207701-6-a5Y4TafQDj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207701-6@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207701 Matthew Seaman <matthew@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthew@FreeBSD.org --- Comment #8 from Matthew Seaman <matthew@FreeBSD.org> --- Hi, We're seeing exactly this on upgrading from 10.2-RELEASE to 10.3-RELEASE-p5 -- only one machine out of about 10 that have been upgraded. Workaround is to set the ether address via rc.conf by adding: ``` ifconfig_vlan110="ether 90:b1:1c:41:93:50 up" ``` Config settings: ``` ifconfig_bge0="up" ifconfig_bge1="up" ifconfig_lagg0="laggproto lacp laggport bge0 laggport bge1 up" cloned_interfaces="lagg0 vlan110" vlans_lagg0="vlan110" create_args_vlan110="vlandev lagg0 vlan 110" ifconfig_vlan110="ether 90:b1:1c:41:93:50 up" ipv4_addrs_vlan110="10.2.1.9/24" defaultrouter="10.2.1.1" ``` Machine is a Dell R420 -- we're seeing the same effect with both the on-board bge(4) NICs and with an add-on igb(4) card. This setup has been working flawlessly for us on numerous machines since around 9.0-RELEASE -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207701-6-a5Y4TafQDj>