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

Shibby's Tomato on R7000 - Unstable ping

Discussion in 'Tomato Firmware' started by thecodemonk, Jul 13, 2014.

  1. thecodemonk

    thecodemonk Connected Client Member

    I'm having an unstable ping issue once I flashed to Shibby's Tomato. I just got the R7000 yesterday and just verified wireless and wired connections were stable first. Then flashed to DD-wrt last night. No issues, everything was stable and fine. Since dd-wrt doesn't have very good ip6 support, I decided to try out tomato. So I flashed back to stock firmware, then flashed to 121 of Shibby's tomato. Since then, my ping to the router is all over the place.

    Reply from 192.168.5.1: bytes=32 time=184ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=44ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=30ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=18ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=15ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=31ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=51ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=31ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=15ms TTL=64
    Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=25ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=8ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=56ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=35ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=62ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=20ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=12ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=7ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=49ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=12ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=49ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=108ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=122ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=17ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=13ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=50ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=38ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=9ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=13ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=31ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=278ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=15ms TTL=64
    Reply from 192.168.5.1: bytes=32 time=82ms TTL=64

    I've looked through various options and I don't see anything that could be wrong. Anything I can check or reset? I've rebooted numerous times while setting up various options and it has never returned to a stable ping.
     
  2. thecodemonk

    thecodemonk Connected Client Member

    Some more information from trying to fix this tonight... I did a NVRam reset. Upon reboot, I had a <1ms ping constant. I started reconfiguring everything and when I was finished I did another ping test, it was very unstable again...

    So I reset nvram again and decided to leave a constant ping going as I changed things. After doing everything one by one and not seeing it deviate from <1ms ping, I decided to change the routers IP (I don't use 192.168.1.x at home). As soon as I changed it, I had to static IP my computer because the router didn't reboot, and it wouldn't get a new IP through DHCP. I was able to access the router on the new IP, but DHCP wasn't working, so I did a reboot. It rebooted and my ping times all over the place again. I tried quite a few things included changing the CTF and Jumbo frames both on, then individually off one at a time, no difference.

    With those off, I clicked on reboot from the tomato GUI and when it rebooted, my pings are now constant again at <1ms.

    I can't even guess as to what the problem is, but if there is anything I need to test or try, let me know. I'm not rebooting this thing unless I absolutely have to now. lol But if it just starts jumping all over again, I will post with results.
     
  3. thecodemonk

    thecodemonk Connected Client Member

    I was messing with ipv6 (had it enabled, but it's not working) and in the mix I had to reboot the router... Back to unstable pings and I cannot get it to resolve no matter how many times I've rebooted.

    I will be flashing back to dd-wrt in the morning unless someone knows of another tomato release that doesn't exhibit this problem.
     
  4. rs232

    rs232 Network Guru Member

    The ping issue is a well known bug for tomato ARM devices.
    Shibby 121 seems to be a bit better than previous versions but it still has the bug.
    When it happens the best solution is to reboot (few times) until the ping goes back to <1ms
    I had 4 days run of <1ms but then the bug reappeared. Please be patient until this is finally fixed.

    Forget about jumbo frames they are currently not working on ARM
    There are also few other bugs open and the they are tackled one by one

    Keep an eye on these two threads for updates:
    http://www.linksysinfo.org/index.php?threads/tomato-for-arm-routers.69719/page-7
    http://www.linksysinfo.org/index.php?threads/tomato-shibbys-releases.33858/page-35

    HTH
     
  5. thecodemonk

    thecodemonk Connected Client Member

    I just posted in another thread, but long story short, a reboot this morning got it back to <1ms. So I'm going to roll with it like this and hopefully not reboot it anymore. Since ipv6 is working now, I have no reason to change anything sans some firewall rules.
     

Share This Page