Moving VLANs to lagg doesn't remove old VLANs
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.
Resolves #944. Actually bring down the vlan interface if it existed previously. This is a regression from the ppp dance/requests/whatever.
Ticket #944. Wehn changing the parent interface make sure to destroy the old vlan before creating the new one. Since vlans use the name of the parent the old interface referencing the old parent vlan will remain intact.
Ticket #944. Do not use the interface_bring_down fucntion here since it is meant for assigned interfaces. Directly destroy previous vlan interface if parent changes.
Ticket #944. Also destory the previous interface if the user changing the vlan tag of an existing vlan entry.
#2 Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to New
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>
#6 Updated by Andreas Bochem about 9 years ago
Bug still exists in 2.0-RC1 (amd64) build on Mon May 9 04:17:17 EDT 2011.Tested:
- create vlan 66 on em0 -> ifconfig shows em0_vlan66
- edit vlan 66 to be on lagg1 -> ifconfig shows both em0_vlan66 and lagg1_vlan66
- remove vlan 66 -> ifconfig shows lagg1_vlan66 removed, em0_vlan66 still present