[Bug 37515] Re: Doesn't restore interface state correctly on resume

2008-05-30 Thread Yann
A good fix for this is, for wired interface, is to check if a cable is connected/link is up at pre-up stage (mii ethernet transceiver knows). See this fix I commited as it can also cause a long resume from STR problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/236066 -- Doesn't resto

[Bug 37515] Re: Doesn't restore interface state correctly on resume

2007-04-28 Thread Brad Langhorst
it would be nice to try to do an "ifconfig vmnet1 up" if the ifup fails. When devices are not listed in /etc/network/interfaces this is a problem. to work around it, i've added a line iface vmnet1 inet manual to /etc/network/interfaces brad -- Doesn't restore interface state correctly on resu

[Bug 37515] Re: Doesn't restore interface state correctly on resume

2007-04-14 Thread Paul Sladen
There's still something slightly amiss with the logic---somebody reported this to me in-person a week ago on their laptop. Because of 'ifdown' and 'ifup' we loose the state of the interface if it was configured by a method that was not 'ifupdown' (network-manager or manual 'ifconfig'). -- Doesn'

[Bug 37515] Re: Doesn't restore interface state correctly on resume

2007-04-13 Thread scoopex
Same problem here - Kubuntu 6.10 restores all interfaces which are defined in /etc/network/interfaces. It seems that Ubuntu restores all network-interfaces after a resume or a suspend2disk - it doesn't matter if you commented out the "auto eth0" line. In this case i have two default routes after