> We migrated from separate files in /etc/networking/interfaces.d to just > declaring > everything in the single /etc/networking/interfaces file. This overcomes a > lot of > issues with regards to bringing interfaces up in the proper order and "ifup > -a" > now works perfectly again
great. > (a) to have bonds come up correctly you absolutely have to define slaves > before the > bond master and the primary slave before secondary slaves in the > configuration file, > and (b) to have a vlan come up correctly define its raw device before the > vlan device. yep, I'm pretty sure this is how ifupdown has always behaved. However, please do feel free to open a bug, as it should work better and not require specific ordering like this (I just can't promise it will get fixed soon). Also, if it ever worked in the past that you know of, it's more likely to be fixed, so do note that if you open a new bug. > bringing bonds up correctly at boot does not it should - can you please downgrade to the vlan version 1.9-3.2ubuntu1.16.04.1 (assuming you're on Xenial), and if it still fails there, please open a new bug. If it doesn't fail there, then let me know in this bug, as it's a regression from my changes. You can download the older vlan package from here: https://launchpad.net/ubuntu/+source/vlan/1.9-3.2ubuntu1.16.04.1 click on the arch you're using under 'Builds' to get to the arch-specific page with binary deb links, e.g. for amd64: http://launchpadlibrarian.net/289303685/vlan_1.9-3.2ubuntu1.16.04.1_amd64.deb < There is a problem when running a bond on top of vlans also please test this with above-mentioned vlan package version, and open a new bug if it fails there as well, or post here if it works with that older vlan version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: Fix Released Status in vlan package in Debian: New Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 <begin content of /etc/network/interfaces> auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 <end content of /etc/network/interfaces> The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
