wrt54g and dhcp ip problems

[agibby5]

I have cat5e lines ran to every room in my house after last weekend 🙂. i have a wrt54g router w/ dd-wrt v23 firmware.

When i connect a new computer to the network via dhcp (such as my laptop when i come home from college) i get an unconventional ip address... the normal ip addresses are 192.168.1.xxx on 255.255.255.0. when i first plug in the laptop and turn it on, it takes forever to connect and when it finally does i get an ip address such as 169.254.12.8 on 255.255.0.0. why would this keep happening?

in order to get a working ip address, i have to go to the basement and unplug the router for a couple seconds. when i plug it back in and by the time i get back up to the second floor the computer is connected properly.

is there any settings that i havent seen? what can i do to remedy this problem???


Thanks in advance,

agibby

 

[volrath]

the 169 address comes from windows when it times out attempting a DHCP lease. Clearly the DHCP service on your router is failing, and rebooting fixes it. I don't know why this would happen other than faulty router software/hardware. If your workaround is not satisfactory, you can try manually specifying a static IP on the adapter and see if you can still get a connection.

Specify an IP such as 192.168.1.125 with subnet mask 255.255.255.0 and default gateway 192.168.1.1, with DNS server 192.168.1.1. Try not to use an IP which would already be in use. You may be able to get a connection this way, but if you connect back up to another network, you are going to want to change back to DHCP.

 

[InlineFive]

DD-WRT v23 has a problem with DHCP logs becoming corrupted and taking the server down. Mine has the same problem, although it's the most noticeable with wireless clients.

Your best solution is to set a Cron reboot every 12 hours. 🙂

And none of the DHCP servers in any 3rd party firmware for our router works properly. :shocked:

:sun:

 

[agibby5]

Originally posted by: volrath
the 169 address comes from windows when it times out attempting a DHCP lease. Clearly the DHCP service on your router is failing, and rebooting fixes it. I don't know why this would happen other than faulty router software/hardware. If your workaround is not satisfactory, you can try manually specifying a static IP on the adapter and see if you can still get a connection.

Specify an IP such as 192.168.1.125 with subnet mask 255.255.255.0 and default gateway 192.168.1.1, with DNS server 192.168.1.1. Try not to use an IP which would already be in use. You may be able to get a connection this way, but if you connect back up to another network, you are going to want to change back to DHCP.

the static setting works great. however, i'd rather not use it as i connect to many different networks throughout the week. thanks!

Originally posted by: InlineFive
DD-WRT v23 has a problem with DHCP logs becoming corrupted and taking the server down. Mine has the same problem, although it's the most noticeable with wireless clients.

Your best solution is to set a Cron reboot every 12 hours. 🙂

And none of the DHCP servers in any 3rd party firmware for our router works properly. :shocked:

:sun:

hmm, i have more luck connecting wirelessly to this network than with a wired connection. i like using the wired because of greater transfer speeds. what is a cron and how do i set it to do this? thanks!

thanks to you both for your replys.

 

[skyking]

go to the administration tab, and scroll down. near the bottom of that page, you can schedule a reboot.

 

[agibby5]

switched to tofu v12 and it seems to work much better.