it appears that the suggested edit to /lib/udev/rules.d/40-bridge- network-interface.rules fixed the problem i was seeing (don't have the vlan-related file on the system). thank you! the interfaces.fail and interfaces.nospc files both now work as expected, as does our standard interfaces configuration (the attached files were simplified versions of this).
the whitespace/indentation question isn't a big deal, but it is a source of confusion. without your fix, the only version of the file that i could get to work was the interfaces.utf8 (comment #4). but it isn't strictly related to indentation: both interfaces.fail (using ascii whitespace indentation) and interfaces.nospc (no indentation) failed. for whatever reason, the apparent indentation using the non-printing characters in interfaces.utf8 worked. thanks again... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1003656 Title: bond entries in /etc/network/interfaces fail without indent (when adding a bond the bridge fails to acquire a dhcp address) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1003656/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
