Actions
Bug #3976
closedVLAN Interfaces on LAGG get orphaned on LAGG change
Start date:
11/03/2014
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1.5
Affected Architecture:
Description
Reproduce:
1. Create LAGG with e.g. em3 + em4, LACP and a nice description
2. Create a few vlans and assign them to your LAGG-device
3. Think about a nicer description and change the LAGG-device again. Now all your vlan interfaces on the lagg are orphaned and have no parent (device) anymore.
lagg1: 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 <DELETED>
inet6 <DELETED> prefixlen 64 scopeid 0xf
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em3 flags=18<COLLECTING,DISTRIBUTING>
laggport: em2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
lagg1_vlan15: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15 00
options=103<RXCSUM,TXCSUM,TSO4>
ether <DELETED>
inet6 <DELETED>%lagg1_vlan15 prefixlen 64 scopeid 0x11
inet 192.168.15.1 netmask 0xffffff00 broadcast 192.168.15.255
nd6 options=1<PERFORMNUD>
media: Ethernet autoselect
status: active
vlan: 15 vlanpcp: 0 parent interface: lagg1
Afterwards
lagg1: 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 <DELETED>
inet6 <DELETED>%lagg1 prefixlen 64 scopeid 0xf
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
media: Ethernet autoselect
status: active
laggproto lacp
laggport: em4 flags=0<>
laggport: em2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
lagg1_vlan15: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether <DELETED>
inet6 <DELETED>%lagg1_vlan15 prefixlen 64 scopeid 0x11
inet 192.168.15.1 netmask 0xffffff00 broadcast 192.168.15.255
nd6 options=1<PERFORMNUD>
vlan: 0 vlanpcp: 0 parent interface: <none>
See also https://forum.pfsense.org/index.php?topic=83605.0
First I thought it only happens on changing the LAGG members. But just changing the description is enough. If this bug (if you need a name - how about batman bug?) can't be fixed, I suggest a big fat warning on the LAGG configuration page.
Actions