[Bug 207701] vlan interface over failover lagg has empty/00:00:00:00:00:00 mac/ether address
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Mar 4 13:04:00 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207701
Bug ID: 207701
Summary: vlan interface over failover lagg has
empty/00:00:00:00:00:00 mac/ether address
Product: Base System
Version: 10.3-BETA2
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: freebsd-bugs at virtualtec.ch
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
Created attachment 167713
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167713&action=edit
comparison between 10.2-release and 10.3-prerelease dmesg
We configure some servers with two interfaces as follows:
- failover lagg0 on em0 and em1
- several vlans on lagg0
after upgrading our systems due to the openssl bug, they came up without
networking. The reason was the vlan interfaces on the lagg got configured
with empty mac addresses:
vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1496
ether 00:00:00:00:00:00
inet 10.0.1.11 netmask 0xffffff00 broadcast 10.0.1.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 10 parent interface: lagg0
where as with RELEASE-10.2, this looked as follows:
vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1496
ether 00:30:48:7f:29:74
inet 10.0.1.11 netmask 0xffffff00 broadcast 10.0.1.255
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 10 parent interface: lagg0
The lagg0 looks the same in both releases:
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:30:48:7f:29:74
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
laggproto failover lagghash l2,l3,l4
laggport: em0 flags=5<MASTER,ACTIVE>
laggport: em1 flags=0<>
We're normally using a stripped own kernel config, but for this purpose
I deliberately booted with 10.2-RELEASE and created a 10.3-PRERELEASE at r296382
GENERIC kernel to have a verifiable configuration.
Our rc.conf snippet to configure the interfaces looks as follows (there
are more vlans configured than this):
cloned_interfaces="vlan10 lagg0"
ifconfig_em0="vlanhwtag up"
ifconfig_em1="vlanhwtag up"
ifconfig_lagg0="laggproto failover laggport em0 laggport em1 up"
ifconfig_vlan10="inet 10.0.1.11/24 vlan 10 vlandev lagg0 up"
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list