The problem is that network will still attempt to manage eth0 blantly ignoring that when taking down the primary interface, all the slaves like eth0:10 will go down too.
If you look at the backend code, you will see that network manager will register the interfaces in its list, but does not know how to manage them properly because to bring up eth0:10 you need to have eth0 up first. So they need a special ordering to be handled properly. Try this: ifconfig eth0 1.1.1.1 up ifconfig eth0:10 2.2.2.2 ifconfig eth0 down you will see that eth0:10 is down too. network manager does reset all the interfaces to initizialize but doesn't bring back eth0:10. this is hardly an ifupdown bug. This behavior is well known and n-m simply doesn't know how to cope with it. Fabio -- ifup fails to bring up alias interfaces like eth0:10 https://bugs.launchpad.net/bugs/95968 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
