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

Strange problem with access to my router

Discussion in 'Tomato Firmware' started by ceckin, Nov 12, 2010.

  1. ceckin

    ceckin LI Guru Member

    Guys, i have a WRT54GL and after trying a lot of firmwares i found that the 1.28 SpeedMod works the best for me, but with all firmware i have a problem. After some amount of ping packets, i get this:

    Reply from 192.168.1.10: Destination host unreachable.

    The problem is that this ip is the end address of the routers range. Its not used by anyone or any device. So how come the router times out?
     
  2. TexasFlood

    TexasFlood Network Guru Member

    I typically only see "Destination host unreachable" when I'm disconnected from my network. I'm not clear what you mean by "The problem is that this ip is the end address of the routers range. Its not used by anyone or any device." 192.168.1.10 is that end of a range? What range. Don't follow.
     
  3. ceckin

    ceckin LI Guru Member

    You set an ip range from which the router gives addresses. Mine is from 192.168.1.2 to 192.168.1.10 (the last one, and the one from i get "Destination unreachable").
     
  4. TexasFlood

    TexasFlood Network Guru Member

    So you're saying 192.168.1.10 is the last IP on the router defined DHCP range, correct? And you're trying to ping 192.168.1.10 and getting "Destination host unreachable"? You also state "It's (presumably meaning 192.168.1.10) not used by anyone or any device." If 192.168.1.10 is indeed not used by any device then that's why it times out, because there is no device there to respond to a ping. If I have misunderstood then please correct me, again, hah.
     
  5. ceckin

    ceckin LI Guru Member

    Probably i didn't explain it good. So here it goes:

    Im pinging my router (192.168.1.1) to detect if there are any losses or router stop responding. While latency is normally <1 ms, sometimes few packages gets:

    192.168.1.10 Destination host unreachable.

    And thats why its strange im not pinging 1.10, but the router and few packages gets lost somehow. And also dnsmasq sometimes timeouts on request, which is strange cause i have wired connection plus <1ms latency.
     
  6. TexasFlood

    TexasFlood Network Guru Member

    OK. I -may- have seen that before, although I can't recall the exact details. I was trying to ping a device and lost contact with my router for whatever reason, after which is starting listing the IP of my local interface basically stating that my local interface could not reach the destination being pinged. If the computer you are pinging from has the IP of 192.168.1.10 then the same thing is happening to you. The next step is to troubleshoot why you've lost connectivity.
     
  7. ceckin

    ceckin LI Guru Member

    For some reason i dont think you understand me, this is why i mean:

    Code:
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.1.10: Destination host unreachable.
    Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
    I'm pinging my router, this .x.10 address is never used by any device, also the router was reseted and nvram cleaned, before inserting the new settings (ISP connection settings). As you can see i don't ping x.10, but i get reply from the router that there is no device on that address. So whats wrong?
     
  8. TexasFlood

    TexasFlood Network Guru Member

    Strange. If you're really sure 192.168.1.10 is not being used then it's not the same thing I saw. If you haven't, maybe run "ipconfig" just to be 110% sure. After that maybe run "netstat -r" just to double check your routing tables.
     
  9. ceckin

    ceckin LI Guru Member

    Its a little embaracing to admit it, but it seems like there were a few old route paths in the Windows route table. Thanks for the help, really apreciate it.
     

Share This Page