I did some more debugging on the problem: - It also occurs when upgrading to Quantal Quetzal 12.10 (as of September 5, 2012). - The sub-interfaces seem to be not the problem. I have configured my VirtalBox machine to have a separate interface for each network, but bridging into the same network. That is, there are eth0 and eth1 instead. - The problem seems to be caused by the "gateway" setting on more than one interface. Leaving "gateway" only for eth0 lets the machine boot without the delay, at least in most of the cases. I am currently not sure whether it "solves" the problem.
However, having a second default route should be no real problem. That is, when eth0 is shut down, the default route via eth1 should ensure that Internet connectivity is still working, and vice versa. Therefore, ifupdown should have no problems with this configuration, and there must be a bug somewhere in the scripts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043244 Title: "Waiting up to 60 more seconds for network configuration" when using interface aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1043244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
