I have no idea why this is. I know that dhclient3 is killed when the computer goes to sleep. But I don't understand what wakes it up, nor why it won't work "normally" as soon as the interface is up. Please note that it doesn't just take extra time - it will never connect.
If you want me to run more tests, all you have to do is ask!
Hiya,
I am not sure this is gonna help.
However, I found that ifdown/ifup doesn't actually do the trick.
What you _actually_ need to do is this:
#!/bin/bash
#echo Killing the DHCP client... dhclient. eth1.pid
killall dhclient3
rm /var/run/
#echo Restarting the DHCP client... dhclient. eth1.pid -lf /var/lib/ dhcp3/dhclient. eth1.leases eth1
dhclient3 -pf /var/run/
This actually does the trick quite nicely.
I have no idea why this is. I know that dhclient3 is killed when the computer goes to sleep. But I don't understand what wakes it up, nor why it won't work "normally" as soon as the interface is up. Please note that it doesn't just take extra time - it will never connect.
If you want me to run more tests, all you have to do is ask!
Bye,
Merc.