You are not logged in.
Hi all,
I have my arch box running fine, but on occasions my router freezes up and the only way I can fix it is by restarting the router. Now when I restart the router, the arch machine doesn't get itself a new IP address. All my Windows machines on the other hand manage to get a new IP. I am using networkmanager for networking and the machine has an ethernet connection. Does anyone know whats going wrong here?
Thanks,
Luke
Offline
Tried restarting the network / dhcpcd?
Offline
Sorry, I didn't mention that its a headless box so the only access I have to it is over ssh really. Surely the system should get a new IP itself? It gets a new IP if I unplug the ethernet cable, the plug it back in.
Offline
Nobody know what this could be?
Offline
Nobody know what this could be?
Without any logs, dmesg output or tests that you may have performed to try and figure it out? I guess no one will be able to help you without that.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
There are a few things you could do, but you are correct that if dhcp is running correctly it should automatically renew its IP.
You mentioned, however, that the only way to fix the issue is to restart the router because your Arch box is headless. Do other computers on your network lose their IP as well? If so, it might actually be an issue with your router and home LAN as opposed to DHCP.
If you need some documentation on setting up DHCPd on your server, you might want to check out http://wiki.archlinux.org/index.php/Con … or_DHCP_IP
I hope this helps, if not it might be a good idea to post the information requested by r00kie...
Information Security Professional
Offline
Have you tried launching dhcpcd with the -E flag?
-E , -lastlease
If cannot obtain a lease, then try to use the last lease acquired for the interface. If the -p, -persistent option is not given then the lease is used if it hasn't expired.
Don't know if this applies to the current operation, or if it will be smart enough to try to use its previous elase next time a problem is detected. Might be worth a shot, though.
Option B: Set dhcpcd to run on a cron every few minutes or every few hours, so it can hopefully recover next time this happens. You could probably write a small script that tries to ping some server (google), and if the ping fails, restart your interface and try to get a new lease.
Option C: Buy a new router? ![]()
Last edited by Fox2k (2010-08-03 01:59:52)
Offline