Hi Andrew, my understanding from back when you introduced that support into ifupdown was that you intended for people to use ifupdown directly for bridge and vlan management rather than through the hooks provided by bridge-utils and vlan.
Since Ubuntu is doing a bit of weird magic here (compared to how things are in Debian) and the actual bridge and vlan creation is sometimes triggered from udev entirely independently of ifupdown, it seemed to me like there wouldn't be a real way of changing ifupdown to cope with this and that rather than having two piece of software try to do the same thing, turning the whole vlan and bridge support of in ifupdown seemed the right way forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295304 Title: ifdown -a fails with vlans on bonded interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1295304/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
