The command in comment #8 *should* do this in a single exec resource: sudo ifdown --exclude=lo -a && sudo ifup --exclude=lo -a
However, I have found this does not actually work either for any significant config change (e.g. IP address change, gateway change). In fact, the command above frequently causes networking to stop working in such cases. The only way I've found that works is to reboot the server; NetworkManager is not an option when doing text-based network config. Other distros using upstart do not seem to have this problem. It's a shame that Canonical hasn't seen fit to address this, and its cost them my employer's (albeit meager) support budget. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301015 Title: Networking does not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
