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

Ping & Trace diagnostic stopped working on WRT54g

Discussion in 'Cisco/Linksys Wireless Routers' started by aputerguy, Sep 13, 2004.

  1. aputerguy

    aputerguy Network Guru Member

    I just upgraded the firmware on my WRT54G (ver 1) from 1.30.7 to 2.04.4.

    Everything works fine *except* that the ping and traceroute diagnostics now return:
    Network is unreachable
    This error message occurs even when I ping the router itself ( or

    Note that I have no problem pinging the router (or for that matter anything else on the LAN or Internet) from one of the client machines served by the WRT54G router.

    I have tried (multiple): hard resets, power-off, reload firmware -- but nothing sees to work.

    I tried loading firmware 2.02.7 but it has the same problems. When I downgrade again to 1.30.7, ping and traceroute work again.

    Any thoughts?
  2. cabo

    cabo Network Guru Member

    >Network is unreachable

    Have (had) you configured the WAN (internet) Interface with 2.04.4 ?
    Have you used your old config?
    You may need to load the factory default settings after the upgrade and then setup everything again.
  3. aputerguy

    aputerguy Network Guru Member

    I did a hard reset on the router and reconfigured everything from scratch.

    Again, the interesting thing is that the router itself works fine allowing both wired and wireless connections to connect properly both on my LAN and to the external Internet.

    Specifically, ping works fine when rund from any computer on my LAN -- i.e. I can ping other computers on my LAN, I can ping the Linksys WRT54G itself, and I can ping any computer on the Internet (WAN).

    The only problem is that the ping (and traceroute) commands on the WRT54G diagnostic screens themselves don't work -- i.e. I get network unreachable independent of whether I am pinging computers on my LAN (wired or wireless), computers on the Internet (WAN) or even the router itself ( or

    Not sure why this is happening though...

Share This Page