Added by Chris Buechler about 14 years ago. Updated over 13 years ago.
100%
Description
When moving a VLAN from a physical interface to lagg (amongst other possible scenarios), you end up with duplicate VLANs configured - one on the previous physical interface and one on the lagg.
Updated by Ermal Luçi about 14 years ago
Applied in changeset df2a0f1861be7a4b751bc4cb6e5fe7025b8f0f9c.
Updated by Chris Buechler almost 14 years ago
Still leaves behind the old VLAN.
em1_vlan5: flags=8003<UP,BROADCAST,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
inet6 fe80::290:bff:fe12:166%em1_vlan5 prefixlen 64 scopeid 0xf
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
vlan: 0 parent interface: <none>
Updated by Ermal Luçi almost 14 years ago
Committed the fix even on vlan config page.
Please test!
Updated by Chris Buechler almost 14 years ago
no change. When changing a VLAN from a physical interface to lagg or vice versa, it leaves the old VLAN interface as well as adding the new.
Updated by Ermal Luçi almost 14 years ago
Committed the other fix because the previous relied on interface being assigned.
Updated by Andreas Bochem over 13 years ago
Bug still exists in 2.0-RC1 (amd64) build on Mon May 9 04:17:17 EDT 2011.
Tested:
Updated by Andreas Bochem over 13 years ago
still in 2.0-RC2 built on Tue May 31 12:13:03 EDT 2011
Updated by Ermal Luçi over 13 years ago
I just pushed some fixes.
Please gitsync and verify they work correctly now.
Updated by Ermal Luçi over 13 years ago
Applied in changeset 6b421a0fb42a50d1e87ac63c64a5b8b8d2157577.
Updated by Andreas Bochem over 13 years ago
confirm fixed in 2.0-RC3 (amd64) built on Tue Jun 21 23:37:22 EDT 2011