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

Is the ping time to my router high?

Discussion in 'Tomato Firmware' started by Sunspark, Jun 29, 2008.

  1. Sunspark

    Sunspark LI Guru Member

    Hi guys, this is over a wireless connection.

    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.983 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.042 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.210 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=2.077 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.070 ms

    Shouldn't it be below 1 ms? It is after all, the first hop from the laptop..

    Using OS X.
     
  2. ifican

    ifican Network Guru Member

    Nope your fine, I would'nt be to concerned with .5ms or so. Ping time is all going to be based on packet size. Different apps use different sizes and thats why some times appears vastly different. Looks like OSX uses 56 bytes, windows uses 32, some flavors of linux or unix use 64. If you change your packet size you will see your times change up or down as you increase or decrease the size.
     
  3. LLigetfa

    LLigetfa LI Guru Member

    I think it's high. Probably due to interference if pinging over wireless. Could be CPU load as well.

    In a clean environment I don't see pings over 1 ms to any of my dozen APs. I know because I tested all of them to prove a point.

    We had someone setup an industrial wireless network on our process network and when they ran into problems, they flew in a couple of hotshots. Of course, my wireless network was blamed for their problems so I tagged along with them to prove my innocence. They were seeing double digit ping times and they figured it was normal. On my hotspot network with a dozen APs strung out along 2 KM of fibre, I could not find a single ping over 1 ms. When I presented my results, they were speechless.
     
  4. ifican

    ifican Network Guru Member

    It's nothing to be concerned about, 1ms vs an average of just under 2 is nothing to worry about. Sitting literally right next to the AP i currently use, at 64bytes i run just over 1ms. Any number of factors can cause latency over wireless, but again 1 ms is nothing to be concerned with.
     
  5. Sunspark

    Sunspark LI Guru Member

    I was twiddling about earlier.. at first I though it was the packet size as mentioned because it was lower.. but then it reverted back to the way it was.. I played around with different wireless channels.. no real change.. decided screw it..

    But now..

    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.042 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.145 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.058 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.239 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=1.262 ms
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.230 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.266 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.200 ms
    64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=1.216 ms

    Changes since attempts earlier with the channels:

    1- Changed router MTU to 1448 (and wireless MTU to 1448 also). Why? Because apparently 1448 is very tiny bit more optimal than 1492 for DSL, something to do with ATM cells. I seem to have a smidgen of a speed bump (smidgen).

    2- Rebooted the router.

    So my ping times are down now, but I don't know why.. too many variables changed.. channel, MTUs and a reboot.. I'll see how it is next week.. router was up 8 days before I rebooted it.
     

Share This Page