Tomato for ARM routers

Discussion in 'Tomato Firmware' started by kthaddock, Feb 28, 2014.

  1. wit100

    wit100 Networkin' Nut Member

    I always wondered about this - I have set up a rather large LAN network for someone's small business and they have over 100 computers on the network (almost all wired). They are currently using RT-AC66U. The R7000 obviously has a faster CPU than RT-AC66U. If you switch it to R7000 instead of the current RT-AC66U, will you see a performance increase? I know most of the PCs on the network do access Internet all the time.
  2. James Good

    James Good Serious Server Member

    MrDoh, FYI, I am running an AC68U, on Shibby's 118 (haven't gone onto 119 yet, 118 is nice and stable), and have a Verizon Network Extended too. I haven't seen any problems with it, nor have I ever set any VPN passthrough options (not sure if that's even something that exists in Tomato?). Glad yours is working though!

  3. MrDoh

    MrDoh Addicted to LI Member

    Yes, I've had to go back to dd-wrt because my Verizon Network Extender won't stay up with Victek's tomato firmware, haven't tried Shibby's yet. I'm really sorry about that, since the IPv6 worked so well, as well as everything else other than the Network Extender. Unfortunately I can't use cell phones here without it, so I'm stuck.

    If I reconfigure Victek from factory defaults, and don't do anything else, the Network Extender has the best chance of coming up. But it didn't make it through the whole first night (offline this morning). This morning I reconfigured from factory defaults, and somewhere along the line the Network Extender decided that it didn't like what it saw, and went offline again. Right now, it's working fine, of course, it always works with dd-wrt and pretty much any other firmware I've tried.

    I sure wish that there was something other than lights that I could look at with this stupid Network Extender to see why it's going offline. All I get as an indicator is that the power and WAN lights are solid blue, and the GPS and system lights are solid red. Not something I've seen before, so I'm guessing that it can't get in touch with its home base, which it uses a VPN to do.
  4. jsmiddleton4

    jsmiddleton4 Network Guru Member

    We're getting closer and closer with each improvement. Looking forward to installing a Tomato variant and being done with the transition and then just moving forward with Tomato.

    So much easier to configure and a great value. If folks have not done a donation I encourage them to do so.
    Iceman_jkh and TyShawn like this.
  5. wit100

    wit100 Networkin' Nut Member

    To give a bit more info to my question above (quoted), I asked them to send me the CPU load just now. They said it is usually in the 0.02 to 0.2 range for all 1 / 5 / 15 mins. So, would they benefit from a router with a faster CPU like R7000?
  6. jerrm

    jerrm Network Guru Member

    How fast is the connection? Are you using QOS?
  7. wit100

    wit100 Networkin' Nut Member

    Connection 100mbps down / 20mbps up.

    No QoS currently in use, but that may change in the future.

    Over 100 PCs on the network.

    CPU load typically shows 0.02 to 0.2 for all 1 / 5 / 15 mins.
  8. jerrm

    jerrm Network Guru Member

    You're not going to see any real boost from a faster processor on a 100mbps line without QOS. With QOS and a reasonable ruleset, you will see some load on the CPU, but probably still have enough headroom that a faster processor won't gain you much (if anything).

    If the router is doing something besides routing, that could change the equation.
  9. wit100

    wit100 Networkin' Nut Member

    Thanks. I suspected that's the case but wasn't really sure. Appreciate the insight and input.
  10. vex-box

    vex-box Networkin' Nut Member

    Does anyone know what version of ARM Shibby & Victek are coding for here?

    The reason I ask is DLink DSR-250N is only one of two EIGHT port Gigabit routers out there.

    It utilises ARMv6 @300MHz but DLink does provide the source code so was wondering if this is an option.
    Tomato with this form factor (incl DLink lifetime hardware warranty) would be fantastic.

    I can donate a router if its deemed possible.

    Thanks Vex
  11. kallsop

    kallsop LI Guru Member

    Also noticed the varying ping times and long boot time, looking forward to shibby v120. Didn't get to try OpenVPN Client yet to see if it drops PIA, and if I can exclude an IP with 'route <excluded_IP> net_gateway'.
  12. wit100

    wit100 Networkin' Nut Member

    Are you referring to R7000?
  13. kallsop

    kallsop LI Guru Member

    Yes, a Netgear R7000. I tried dd-wrt Kong build 24045M, now trying Tomato shibby v119. Whichever works first for what I need, I'll probably stick with it. A new Kong build was just released, 24170M, didn't try that one yet.
  14. sandspike

    sandspike LI Guru Member

    Things have cooled in here, how is everything working for everybody.
    What version are you running, any issues, praise,etc.

    Shibby - How is 120 progress?
    Victek - Any progress on the next version?

    I am running Shibby 118, wireless is still running very well, ping times are still an issue from time to time. 300Mb U/D internet, running well with CTF enabled. Using access restriction, static DHCP, OpenVPN, SSHD, and Routing rules. All working.
  15. wit100

    wit100 Networkin' Nut Member

    Dude, where are you at? 300Mb is FAST! Can I ask how much that is per month? So envious. I don't think that is even available for residential houses in my area...
  16. shibby20

    shibby20 Network Guru Member

    v120 is out.
    TyShawn, Iceman_jkh, MrDoh and 3 others like this.
  17. sandspike

    sandspike LI Guru Member

    Austin, TX - AT&T Gigapower Uverse - Getting upgraded to 1Gb soon. $70 a month.
  18. sandspike

    sandspike LI Guru Member

    Cool, changelog only shows minor changes, were you able to resolve the ping issue?

    [RELEASE] 120
    All version:
    - openssl update to 1.0.1h
    - grow up 6rd-prefix range
    - transmission update to 2.83
    - dnscrypt: add user selectable/manual proxy input – thx lancethepants
    - fix advanced dns/dhcp page
    - dnscrypt-proxy update to 1.4.0
    - dnsmasq update to 2.71

    K26ARM only
    - openssl – add options: version, speed and s_client
    - add DNSSEC to VPN and AIO builds
  19. MrDoh

    MrDoh Addicted to LI Member

    Looks good, also wondering if Shibby has gone back to the older, more stable wireless drivers? Or moved forward to more stable drivers?

    Thanks very much for the new version!
  20. lilstone87

    lilstone87 Serious Server Member

    This is a good question, as I found the wireless drivers in both Shibby's, and Vic's to be unstable. Being one who runs Kong's DD WRT currently, his OLDER driver build's are the best, as the newer drivers suck atm.
  21. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Which ever driver it is my wireless clients connected stronger and more stable with 120 than when I tried 119.
  22. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Thanks again for all the hard work. Curious about this seeing in in another thread. Is this going to be added at some point to the FW or will, due to the nature of the thing, always have to decide for ourselves and manually enter this information via telnet, etc.?

    OC R7000 to 1400
    nvram set clkfreq="1400,800"
    nvram commit
    read CPU temp:
    cat /proc/dmu/temperature
  23. Victek

    Victek Network Guru Member

    Never used the new driver ... ;) test versions before posting uncertain information. I don't consider good practice to overclock CPU in this model, it's not an overclocking forum. Kong is not using OLD drivers, dd-wrt have their customized drivers adapted to kernel version they use.
  24. lilstone87

    lilstone87 Serious Server Member

    Well if you knew me, you would know I don't post stuff without testing myself first. First night I used your latest build on my R7000, someone in the house tried to stream video over the 5GHz band, it was unstable, and dropping like crazy.

    So I am back to using Kong's DD WRT atm, as I expected issue's with such early build's of tomato for the R7000. Main issue's that kept me from running tomato currently was the ping issue, wireless drivers, and poor NTFS USB3 performance(Shibby's build).
  25. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Pings still a little higher then with Netgear's default FW. But they are not all over the place now. Consistently a little higher. Not big swing back and forth.
  26. wit100

    wit100 Networkin' Nut Member

    As for long ping time... Are you guys talking about wired client ping time or wireless client ping time? Ping time seems to be fine on mine with v119 and v120 (< 1ms) - though I am only playing with wired ones right now.
  27. MrDoh

    MrDoh Addicted to LI Member

    Trying Shibby's new 120. All good so far. Wireless strength/coverage is good, ping times are good, IPv6 is working, and whaddya know, the Verizon Network Extender is even working! Be sure to change your wireless locale setting to US, if you're in the US *smile*.

    Hopefully the router will stay nice and stable as it is. If so I'm pretty happy about it, we'll see *smile*.

    Oh yeah, I should mention, before trying IPv6, I put the command mentioned above for Victek in the firewall script. That may be why it's working for me, and it is working just fine.
    Last edited: Jun 11, 2014
  28. sandspike

    sandspike LI Guru Member

    Save configuration working?

    Sent from my SM-N900V using Tapatalk
  29. desiromeo

    desiromeo Addicted to LI Member

    I too did notice issues with the drivers you use victek. There is only one device in my house that doesn't work well and that is my brothers new MacBook pro retina. My older non retina MacBook and many other devices have no issues what so ever. Also after 6days of running fine the 2.4 ghz wireless totally died and the router rebooted. Has been fine since and I tell my brother to suck it up because I like drivers victek uses over what shibby and merlin use. Kongs firmware with old drivers I think were the most stable with no issues, but for some reason I can't seem to set up my openvpn server properly on ddwrt. It's so simple on tomato.

    I'm hoping Broadcom can finally manage to make a decent wireless driver but I don't have much faith in them.

    Sent from my Nexus 4 using Tapatalk
  30. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Wired ping time.
  31. MrDoh

    MrDoh Addicted to LI Member

    Didn't work on Victek, hope that it works with this one!
  32. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I'm a little confused as to why we're not supposed to discuss the basics of OC settings for our R7000's in this thread.

    I did not want to push it too much so I settled at 1200,800.
  33. Flamez

    Flamez Network Newbie Member

    This is great news! Thanks Shibby!

    Does this work on this version where a URL visted History List? Where it shows which site a user on your network is visting and gives user's ip and the site ip and description times when they went there?
  34. juggie

    juggie Addicted to LI Member

    Shibby, did you ever make any progress with the R6250 you received?
  35. Diverge

    Diverge Networkin' Nut Member

    Probably because most people are more concerned about stable and working firmware. IMO there's many more cons than pros as well.

    Sent from my Nexus 5 using Tapatalk
  36. lilstone87

    lilstone87 Serious Server Member

    Well I still find it a little odd, even with Vic's or Shibby's latest build's on my R7000. After flashing the firmware and such, I have to do another reboot or two to get pings back to normal. This is pinging the router wired btw.
  37. Victek

    Victek Network Guru Member

    Don't know what version/firmware was used previously... but nvram erase and reboot after flashing will help to isolate/define this subject not observed in any of my versions by myself.
  38. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "IMO there's many more cons than pros as well."

    That's fine. Don't do it. Discussing it is not telling anyone to do it. If discussing settings for the R7000 and the Tomato firmware does not belong in this thread then where does it belong?

    We discuss the pros and cons of even installing the Tomato FW as well. Discussing it isn't telling anyone to install it and take the risk doing so contains.

    Discussing it is relevant to this thread.
  39. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I do not understand the ping issue and how one firmware impacts pings as we've seen. So I certainly have no explanation for this. But wanted to report it anyway.

    After I set the overclock speed to 1200,800 my pings went way down. Went from being in the high 100's to being teens and low 20's with the longest being 23.

    Glad. Everything does present itself a little snappier. That is so objective it is hard to qualify/quantify. But it is the case.
  40. wit100

    wit100 Networkin' Nut Member

    I am still not seeing long ping time. Almost all my pings are < 1ms. The highest I got (just 2 out of some 20000 pings were 2ms). Seems perfectly reasonable to me. Note that my R7000 only has a laptop (wired) connected to it and nothing else.
  41. lilstone87

    lilstone87 Serious Server Member

    Well I have two comment's so far with Shibby's latest 120 build. After a couple reboots pings have settled down, and also NTFS transfer speeds to my USB3 drive are around 30MB's. I know on his 118 build I struggled to get around 13MB's transferring to my drive. As of now, I just need to test the wireless drivers, and if they seem pretty stable, I can run tomato on my main router for now.
  42. MrDoh

    MrDoh Addicted to LI Member

    So just got up this morning, and everything except the Verizon Network Extender is working. Same thing as Victek, with 2 solid red lights (system and gps), and 2 solid blue lights. What an interesting piece of technology, no way to tell what it isn't liking about what it sees.

    Anyways, unless I can get it back up without totally reconfiguring the firmware, back to some other firmware. Too bad. Maybe next time.

    Edit: Was just able to get the Network Extender back up by moving it from a static IP to DHCP. Don't know why, it works fine on a static IP with any other firmware I've used, including dd-wrt. And worked fine with a static IP last night. It's nice to have it on a static address,since I can give it a name, and easily see it in the device list, but even better to have it running *smile*. Anyways, looks like a reprieve *smile*.
    Last edited: Jun 11, 2014
  43. Bruce Kelley

    Bruce Kelley Network Newbie Member

    My long pings (wired, they were randomly fluctuating between 30 and 150 or so) finally settled down to consistent <1ms after a couple of days with 119. I wonder if there was some state in my net switch that needed to time out. If it happens again, I'll restart the switch.
  44. jsmiddleton4

    jsmiddleton4 Network Guru Member

    The pings are hard to understand in terms of cause.....
  45. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Cox's DNS servers have been known to have issues so this is another one of those things that I can't exactly explain because I'm not 100% sure about what the variables are.

    I had been accessing the web without issue. Seemed fast enough but sometimes a bit of a lag connecting to various web sites.

    I used 2 of OpenDNS's DNS server IP's and the third entry Googles.

    Really sped connecting to web sites up.

    Again not sure if that's a Cox thing, my ISP, or if there is something about the FW that makes manually entered DNS IP's faster to resolve web sites.

    I think this is it though. Was hoping 119 was the "Transition to Tomato and don't look back" FW. It wasn't. Had to go back to Netgear's. 120 however, I think this just maybe the one that allows a full transition to Tomato and then just move on through new releases as they come out.

    Thanks again Shibby and Victek. Was able to send something to Shibby. Still need to do so for Victek.
  46. RMerlin

    RMerlin Network Guru Member

    Dunno if either of you two are using the ipt_webmon module, but I fixed it so it now works under Kernel 2.6.36.
    Toastman likes this.
  47. MrDoh

    MrDoh Addicted to LI Member

    Just a quick one, I looked at my logs and saw that they were full of thousands of the infamous Comcast IPv6 "Neighbour Table Overflow" messages, similar to what I got with the Asus RT-N66U with IPv6. So I put this script into the init script:

    echo 512 > /proc/sys/net/ipv6/neigh/default/gc_thresh1
    echo 1024 > /proc/sys/net/ipv6/neigh/default/gc_thresh2
    echo 2048 > /proc/sys/net/ipv6/neigh/default/gc_thresh3

    and no more of those pesky messages. It is a workaround, trading some memory use for the messages.

    There was also an ip6tables command workaround that worked with the Asus RT-N66U, and didn't cost memory, but I haven't got it working, yet. The interfaces that it references are different on the R7000, so it needs to be adapted.

    Anyways, hope that this quick workaround helps someone else *smile*.
  48. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Back to Netgear's last night. 120 FW was great for about 18 hours. Started having disconnects, pages not loading, etc. Manually added DNS server IP and that seemed to fix "it", whatever it is. But did not. Clients complaining of stuff not loading, slow, lags, etc.

    Back to Netgear's last night and everyone happy.

    I really want to draw a line in the sand and establish Tomato FW and then move on from there. I'll keep trying. I'm sure we'll get there at some point.
  49. jsmiddleton4

    jsmiddleton4 Network Guru Member

    And the dang ping thing. Ping's with Netgear's back to single digit and low teens. 120 pings stayed in the 20's to 30's and some times up to the 80's and 90's.
  50. wit100

    wit100 Networkin' Nut Member

    Can you explain a bit more on your config? For example, is IPv6 enabled? Wireless connectivity vs wired stability?
  51. jsmiddleton4

    jsmiddleton4 Network Guru Member

    No IPv6.

    Both wired and wireless ended up with same symptom of log jams, pages not found, etc.

    I've tried 119 and 120. Same experience with both. 120 just took a little longer. Start out great, fast, connectivity good for both wired and wireless. Over time slowly degrades, pages don't load, etc.

    I'm not a programmer but have seen this in the past be pinned at the "memory leak" issue.

    Reboot helps for awhile but eventually the router slips back into the same stalls, etc.

    When connecting to the router when this is happening, it takes a long time to finally log into the router too.

    I said before with 119 it is as if the router is busy doing something else and is occupied with whatever that is.
  52. sandspike

    sandspike LI Guru Member

    So I guess pings and router lag is not fixed....I'm really not seeing the issue on 118, should I push for 120, that is the question.....

    Attached Files:

    • ping.JPG
      File size:
      148.3 KB
  53. Mercjoe

    Mercjoe Network Guru Member

    I have a question on all these fluctuations in ping time.

    Just what is the baseline and expectations here?

    I have a 3500l v1 running Toastman 7505.2 and pinged and I got a fairly constant 32ms with a high fluctuation of 72ms

    I swapped the r7000 to the network main and got 23ms ping average and a high fluctuation of 69ms.

    If I ping either router I get <1ms for as long as I let it run.

    I am on a DSL connection and I have fairly constant internet use from wired and wireless devices while I was running these tests
  54. wit100

    wit100 Networkin' Nut Member

    On a wired client, you should almost always get <1ms if you are pinging the router itself. Once you go outside of your own LAN, there are too many factors.
  55. sandspike

    sandspike LI Guru Member

    My ping times are wired, albeit through a connected switch.
  56. jsmiddleton4

    jsmiddleton4 Network Guru Member

    " Once you go outside of your own LAN, there are too many factors."

    I'd say we all know that. The issue is with the same "many factors" and changing just the FW ping times are very different between OEM FW and the Tomato variants. Some how the FW is involved and not just the "many factors".
  57. Mercjoe

    Mercjoe Network Guru Member

    But again, I ask what is the baseline of acceptable ping time and what are our expectations??

    We are getting functionality that is far and away more complex and involved than that of the OEM firmware. Is it not fair to presume that there is going to be a difference ping times and such?

    As an experiment. I just tested my OLD WRT54g v2.1. I had different ping times from Toastman's Tomato 7635 and the stock Linksys firmware (actually less ping time with Tomato BTW). Does this mean that there is a problem with the firmware? No, because it is not remotely the same software.

    At what point does it become a issue that needs to be addressed?

    Personally, I would like to see the basic operations of the routers completed. By this I mean all the basic functionality that we have all become accustomed to in the tomato firmware. Once that is attained THEN we start worrying about optimizations.

    The ARMdev team is doing an awesome job at adapting a MIPS based software to these newer platforms. Lets not cloud the issue by complaining about things that probably do not matter when looked at objectively.

    Lets get the basics done FIRST.
  58. MrDoh

    MrDoh Addicted to LI Member

    Did a little playing around here. Re-flashed and configured Victek on the R7000. When configuration was done, everything was working, but ping times between my laptop and router (wired connection) were pretty random. So, wondering if this would be "fixed" by a reboot, I rebooted, no effect. Rebooted several times (4 times) to see what would happen, no effect.

    So, taking a cue from a previous posting here, turned on CTF, and rebooted. No effect. So I power-cycled the router, and when it came back from that, pings were <1ms. Just to see what would happen, I turned off CTF (no explicit reboot following that), and ping times were random again. Turned CTF back on (again, no explicit reboot) and ping times were <1ms every time.

    So, at least here, CTF seems to have a strong effect on normalizing ping times. Don't know what, but CTF is doing something here...Not conclusive by any means *smile*, but might point a finger at the cause for someone familiar with the source code.
  59. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "baseline of acceptable ping time and what are our expectations??"

    But it doesn't work like that. What we have is what establishes a baseline and the performance of that baseline. From that the other FW is contrasted. It is possible with the R7000 hardware to have very fast ping times "out there". Ping times on the LAN aren't an issue.

    The symptoms, lags, pages not found, etc., are consistent with the ping issue. All of those dots line up and connect.

    The FW that has connectivity issues "out there" also has higher and unstable pings as compared to the FW, Netgear's OEM, that has lower pings and does not have connectivity issues.

    There is not set number there is only comparing one to the other.
  60. MrDoh

    MrDoh Addicted to LI Member

    I've found that my "internet speedtest ping times", are comparable to those from Netgear firmware. As long as the ping time between my computer and the router is normal (<1ms wired, 1 or 2ms wireless). And I don't notice page loading lags or pages not found. But everyone has a different combination of wired and wireless hardware, and there are several different ISP's out there, so I understand if some people have issues and others don't.

    It would be nice, though, not to have to fiddle around to get the ping times normalized. Although I've been able to do that every time, with other firmware it doesn't take fiddling, it isn't an issue. On the other hand, I understand that development for tomato on ARM architecture for tomato is early on. Personally, I'm happy with how IPv6 just works, even though it's just a checkbox at the moment, not required. Having struggled with it for 8 months on Netgear stock firmware and dd-wrt, nice when something like that just works.
  61. Grimson

    Grimson Networkin' Nut Member

    Are the ping times erratic when you ping from the router console itself? If a reboot, without changing any settings, helps some of the time or causes it some of the time it could be that there are Ethernet negotiation problems between the WAN device and the router. That could also explain why some people are seeing it and others not, due to different WAN devices used.
  62. wit100

    wit100 Networkin' Nut Member

    For R7000, I can confirm erratic ping times for both:
    - within LAN (PC to router)
    - from PC to outside servers (

    I am comparing these ping times with v117 on RT-AC66U. The difference is extremely significant.

    See screenshots for comparisons of these two routers (attached)

    Note these erratic times are also reflected when loading websites.

    Attached Files:

    Last edited: Jun 12, 2014
  63. sandspike

    sandspike LI Guru Member

    That is the exact problem, I was posting about. My understanding was Shibby IDed the problem and would fix in 120. I completely understand if that wasn't possible to fix. Is shibby hunting the ghost in the machine or a problem that can be fixed.

    Oh and I would be remiss, if I didn't say Thank you to Shibby, Victek, Merlin, and others for making this project happen. Great work so far, looking forward to your next firmware releases. Never mistake our testing, documenting, and reporting as complaining. We are the testing group. We all willing volunteer our time to try things, help hunt bugs, and make this firmware better. Thanks to all!

    Sent from my SM-N900V using Tapatalk
    Last edited: Jun 13, 2014
    The Master likes this.
  64. shibby20

    shibby20 Network Guru Member

    little step forward - web monitor working on ARM

    julesism, zorkmta, Toastman and 5 others like this.
  65. sandspike

    sandspike LI Guru Member


    Sent from my SM-N900V using Tapatalk
  66. hawkmat

    hawkmat Addicted to LI Member

    Shibby! Great job getting Web Monitor working!!
  67. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "The difference is extremely significant."

    Yep. Its the difference that is revealing. Not the actual number as if the number in and of itself has meaning.
  68. lilstone87

    lilstone87 Serious Server Member

    Well I have been running Shibby's 120 build on my R7000 for over 3 days now, and it has run pretty well imo. Have had some streaming over the 5GHz band, using Samba via USB drive without any complains which is good. NTFS writing to USB3 drive speed is improved a good amount.

    Only problem I see, and others have reported about is the ping issue. It's something you can get rid of by enabling CTF, and rebooting the router a time or two after. Still enabling CTF shouldn't be required to get pings back to normal level.

    So getting the ongoing ping issue resolved, and getting some of the non-working ARM features working. The R7000 will be a great router running Tomato. I think I will probably go back to Kong's DD WRT for now as it is just more mature at this stage. But I will say Tomato in it's current stage is not bad on the R7000, and I plan to keep testing new releases. As I plan to run tomato on my R7000 in the future 24/7.
  69. Robert Riggin

    Robert Riggin Network Newbie Member

    With the hardware similarities of the r7000 and the ex6200 is there plans to support the ex6200?
  70. IcyTexx

    IcyTexx Networkin' Nut Member

    Does anyone have problems with 1300mbps 802.11ac on R7000 or any other router?

    I have a 2013 MacBook Pro Retina, and can't establish a connection faster than 600mbps. It never says 1300mbps.
    On the laptop it says transmit rate 200-300mbps. It said 800-900mbps two days ago.

    It seems like the router is working in 20MHz? Why can't I pick channels between 52 and 64?

    [​IMG][​IMG] [​IMG] [​IMG]
    Last edited: Jun 15, 2014
  71. MrDoh

    MrDoh Addicted to LI Member

    Decided to try Shibby v120 again, to see if I couldn't find a work-around for the Android phone WiFi problems I've been having. My theory is that if I use DHCP with the phone instead of a static IP that it won't struggle with WiFi as much. This time it took over an hour of turning CTF on and off and rebooting over and over before ping times settled down to where they should be, <1ms for a wired port.

    Boy, that was boring...Hoping that this can get better. Great to have tomato working, though.

    Edit: Working very well this morning. Everything connected, wireless is great, ping is still normal. So the time spent last night getting the ping to normalize seems to be well spent *smile*. Android phone battery usage problem is at least partially solved, can't tell if totally taken care of yet.

    Edit 2: Just noticed that I ended up with CTF off, and the ping times are still normal, so it's looking more random at the moment.
    Last edited: Jun 18, 2014
  72. MaX PL

    MaX PL Networkin' Nut Member

    the wifi card in that computer is limited to 800-something.
    i have the same computer and the best i've seen is 886 or something like that at 80mhz right next to the router.
  73. wit100

    wit100 Networkin' Nut Member

    I am eagerly awaiting a stable/solid version of v121 for R7000. Thank you, Shibby, and others for working on it.

    Now, while we wait for v121, can anyone explain the settings for R7000 (v120) so that it runs rock solid with no long ping time that appears after a while for several of us?
  74. IcyTexx

    IcyTexx Networkin' Nut Member

  75. MrDoh

    MrDoh Addicted to LI Member

    Something different about how static IP addresses are working with tomato than with dd-wrt and stock firmware. With both stock firmware and dd-wrt, I get better battery usage with a static IP on my Android phone and my Verizon Network Extender stays up with a static IP. When I've been trying tomato, seeing worse battery usage at idle on my Android phone with static IP, and Network Extender doesn't stay up using a static IP.

    Don't have my arms around this, but it was surprising enough that it took me some time before I thought to try these on DHCP, since they've worked well with static IP's on other firmware and routers. At this point, it could be something that I'm doing, of course, but I keep things pretty vanilla here, so I don't know what that would be *smile*. Just using routing and wireless core functionality, no USB, VPN, etc.

    I do change the wireless preamble length to "short" from the default of "long", but I've been doing that with firmware for some time now. So that shouldn't be an issue, but it might be on these early versions of tomato for ARM. Next time I go back to it, I'll leave it at "long", and see if that has any influence.

  76. Grimson

    Grimson Networkin' Nut Member

    I guess you mean static DHCP entries, static IP would mean that the IP is set on the client and not received via DHCP. In case of static DHCP entries it could be lease times or different DHCP options. With wireless it could be a different implementation of the APSD mode or other power-saving features in the driver.
  77. MrDoh

    MrDoh Addicted to LI Member

    Yes, I have a static IP set on my Android phone when I'm not using Tomato, and it's address is outside the router's DHCP pool, of course. Both the Android phone and Network Extender were set up initially in the static address section of tomato configuration, as I have done in the other firmware I've used (dd-wrt and stock). I have since had to move both to the regular DHCP pool, remove their static IP configurations from tomato, and remove the static IP configuration from my Android phone so that they would work properly on tomato.

    Currently back on Netgear stock firmware, a debug version that I was sent that has fully functional IPv6. I'll try tomato again when new versions come out.
  78. MaX PL

    MaX PL Networkin' Nut Member

  79. joecop67

    joecop67 Networkin' Nut Member

    I asked this in a separate thread but maybe I shoud have posted here. Sorry, I'm new to this forum. I have a netgear r6250, would love to see a flavor of tomato on it.
  80. IcyTexx

    IcyTexx Networkin' Nut Member

    From time to time it happens...

    [​IMG] [​IMG]
  81. zorkmta

    zorkmta Network Guru Member

    Shibby! Great job. Just bought R7000 and will arrived some days.

    Want to ask and don´t want made mistake

    To get tomato from original firmware
    1.- Flash from web-original firmware to initial v118?
    2.- From Tomato V.118 to V.120?
    3.- Erase nvram and do reset 30-30-30?

    Are correct?
  82. jsmiddleton4

    jsmiddleton4 Network Guru Member

    You want to do a reset to default before you update to make sure passwords are cleared out, etc.

    The 30-30-30 reset, I've done it as well, is no longer required. The option to clear NVRAM is NOW in the firmware when you flash.
    Last edited: Jun 23, 2014
  83. MrDoh

    MrDoh Addicted to LI Member

    If you follow the instructions that Shibby gives in his videos (see INSTRUCTIONS file with firmware downloads at Shibby's tomato ARM R7000 download site), they are quite informative. More information than you need, but very helpful. And I think that you should set the wireless locale to "US" for both 2.4 and 5GHz. bands if you're in the US *smile*.
  84. conquer22

    conquer22 Network Newbie Member

    Last edited: Jun 24, 2014
  85. Peldor

    Peldor Networkin' Nut Member

    Is Web Usage working in 120 or only in the upcoming 121(?) version? Thanks.
  86. kamaaina

    kamaaina Serious Server Member

    Web monitor would be for version 121 or later, not in yet in v120.

    Now, for the Netgear R6300v2, is it save to try the Shibby ARM version of the Asus RT-AC56U? Or another Tomato version?

    I recall they have the same broadcom CPU (or very close) but I forgot where I read if it's save to give that a shot or not. I guess I need to check SNB to see if that thing has serial pins in case I kill it but I'd rather not open it at all if possible.

    Is there an external way to clear NVRAM from the outside or enable recovery mode on the Netgear like on the Asus? I really like that feature, saved the box a few times already.
  87. marcus13

    marcus13 Networkin' Nut Member

    Hi Everyone,

    Can I just confirm if QoS is working on the ARM build for anyone. Me and a family member have tried 120 on RT-AC68U's and on both, from defaults, all manually configued, the same QoS rules that work on an AC66U don't work. Everything seems to get dumped into one or two buckets. Both setups are using PPPoE connections.

    Am I doing something wrong?

  88. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    You'll probably see an announcement in the changelog or in the forum. It will be much more than a minor bug fix....
  89. jmsqrd

    jmsqrd Network Newbie Member

    I have an R6250 and would like to know this as well. If the R7000 or AC56U versions are not safe to flash for whatever reason, is there a reason that builds for the R6250 and R6300v2 don't exist yet, despite all these routers being nearly identical from a core system perspective?
  90. sandspike

    sandspike LI Guru Member

    Hey jmsqrd, you are welcome to write the firmware. "Is there a reason they don't exist". Yes, because Victek, Shibby, and others haven't had time to code, QA, and test them. And more than likely don't have the hardware to test on. Let's not get demanding of the folks that generously donate their time to this project.
  91. jmsqrd

    jmsqrd Network Newbie Member

    Sorry, didn't mean to sound demanding. What I meant to ask was if there was a technical reason that the builds didn't exist considering the hardware similarity, especially since there are separate builds for the AC56U and AC68U. I'm actually more curious to know if flashing the R7000 build would result in anything more than an instant brick on a R6250. If I can get to the web interface at all after a flash I'd consider that good enough. Mine shows up tomorrow so I'll let you know what I find.
  92. shibby20

    shibby20 Network Guru Member

    I tried make tomato for R6300v2. Result: bricked and broked. I finally rewiwe router and it works on OFW but i am not able even upgrade netgear firmware without serial cable.

    R6250v2 i also have but i did touch it yet. For now i don`t have time for this.

    The most problematic things is *.chk file type for netgear`s firmwares. Tomato-ARM doesn`t support this header format. I know that R7000 works but as we can see R6300v2 wont and here is the problem. I really don`t want broke R6250 :/
  93. fbwalker

    fbwalker Network Newbie Member

    hey Shibby is the source for the R7000 available from the repo? and if so what branch is it on?
  94. shibby20

    shibby20 Network Guru Member

    No, ARM sources are not public yet.
  95. shibby20

    shibby20 Network Guru Member

    QOS on Tomato-ARM v121

    julesism, zorkmta, marcus13 and 8 others like this.
  96. lilstone87

    lilstone87 Serious Server Member

    Happy to see you got QoS working for the ARM build's, But still a bit worried as using QoS disables CTF. Which with using CTF on my R7000 running your build, with a couple reboots after, I still have ping issue's if not using CTF.
  97. MrDoh

    MrDoh Addicted to LI Member

    Shibby, that is really lovely, many thanks. However, last time I tried v120, I never did get the ping times stabilized after a couple of hours of fiddling, and had to give up. Right now I'm using Victek's tomato, since I was able to stabilize/normalize the ping times on it. Just waiting for a tomato release where I don't have to spend an hour or two trying to get the ping times to normalize...once that's done, everything's fine, and then the other features matter to me. I'm so paranoid about it at this point that I keep a DOS prompt window up to be able to check ping times a few times each day, since I've had ping times go back to random sequences after I thought that they were normalized.

    Anyways, that's the main feature that I'm looking for at the moment, personally, stable core functionality. The rest, like QoS, web traffic logging, and so on are great to have, but if the firmware isn't stable, then they don't really matter. This is just my opinion, of course, I'd be surprised if others wouldn't disagree *smile*. I really like tomato firmware, and would love it if it were just a little more stable on the R7000.
  98. shibby20

    shibby20 Network Guru Member

    ping issue propably fixed. I installed today v121 on my R7000 and now my ping is stable.

    kamatschka, MrDoh and kthaddock like this.
  99. lilstone87

    lilstone87 Serious Server Member

    Hopefully so, and thanks :). I know probably still early but any time frame in which we might see 121?
  100. sandspike

    sandspike LI Guru Member

    121 with steady pings.....drool. So QOS with CTF? I don't use the advanced features as much, but I do more and more every day.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice