1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

timeouts when pinging the WRT54G

Discussion in 'Cisco/Linksys Wireless Routers' started by Anonymous, Dec 31, 2005.

  1. Anonymous

    Anonymous Guest

    I'm having issues with my WRT54G, let me first give a basic explanation of the setup

    Verizon (SoCal) DSL -> Westell Modem -> WRT54G v4 -> PC

    Now the router is brand new, it still has the original linksys firmware that came with it, although once everything is working properly I'd like to re-flash it with one of the updates.

    before I put the router into the mix, everything seemed to work fine. When I first installed the router i needed to do an ipconfig /release after which the the config looks like this

    IP Address:
    Subnet Mask:
    Default Gateway:
    DHCP Server:
    DNS Servers:,
    WINS Server:

    (I'm not even sure what a WINS server is, but the IP address, mask gateway, mask and dhcp server is as I expected).

    Now I can connect to the net, however under load I get a lot of timeouts and it starts to break, this is especially obvious when I'm running something network heavy like a P2P application. However even under lighter loads it seems to break.

    I'm not very network savvy, but using ping I've noticed that even when pinging the router (ping I'm getting timeouts when just viewing some webpages.

    Now this seems particularly odd to me, after all even if I was disconnected from the net then I'm still connected to the router, so it should have no problem pinging the router.

    One of the first things I did was to replace the network cable between the router and the PC.. but this made no difference.

    I realise this isn't much to go on, if anyone has any suggestions about programs I could run to gather more information, then I'd be glad to do so and post the results.

    Thanks in advance :)

  2. Anonymous

    Anonymous Guest

    Ok I have some more information I should have mentioned, when setting up the router I needed to connect to the westell modem to set it to "Bridged Ethernet" mode.

    I thought about removing the linksys router from the configuration (temporarily until this is solved), so I plugged the modem back directly into the PC, however this didn't work.

    I then tried to connect to what I thought the modems ip would be ( so that I could turn off "bridged ethernet" but didn't find the modem at any of those IP's.

    Unfortunately I've fogotten what IP I used to make the original changes :( but those seem like they'd be likely... is there any other reason I wouldn't be able to connect ?

  3. mazilo

    mazilo Network Guru Member

    Why don't you turn off everything for two minutes? Then, turn them back on to see if that will solve your problem between the modem and your computer.
  4. Anonymous

    Anonymous Guest

    thanks for your comment Mazi, I tried powering down the modem and computer and then restarting... but it didn't seem to make any difference. I'm not really worried about the modem though, I only mentioned it because I wanted to remove the router for the moment to get full net access back while i figure out what's wrong with the router.

    So my question is, what could make the router timeout on the ping ? The PC is connected directly to the router... so it seems odd to me.

  5. Anonymous

    Anonymous Guest

    Ok I've done some searching and found that it's probably because the linksys firmware keeps open connections for 5 days and that BitTorrent opens a lot of connections, which causes the router to run out of ram and reboot. This would explain why I have trouble pinging the router.

    I could confirm this if I could get 'uptime' info out of the router, but I dont think there's any way to do this with the standard firmware.

    anyhow the only solution seems to be upgrading the firmware, I upgraded to the latest linksys firmware and it hasn't re-booted on me yet (although I havn't pushed it as hard).

    I dont have any qualms about upgrading the firmware, I just wanted to get it reliably first so that if I did have issues I wouldn't blame it on the firmware.


Share This Page