Tomato for Netgear Nighthawk R7000

64 posts / 0 new
Last post
Jennifer Melfi
Jennifer Melfi's picture
Thanks for your reply,

Thanks for your reply, kamaaina.

The problem was traffic was either "Unclassified" or "p2p" (default). On Genie, I have for example QoS Highest for SIP ATA using MAC address. I couldn't get this to work or by IP address with Tomato on R7000. The built-in rules should have given priority to SIP/RTP even without my custom rule, but didn't appear to. I had a lot of Jitter Buffer underruns on my SIP ATA then when running stock, which is why I switched back.

My understanding is that only outbound traffic is given a classification, which means it was just classifying all outbound traffic as the default classification.

If I'm the only one experiencing QoS issues on v119 on R7000 I may give it another try this weekend.

Kong
Kong's picture
kamaaina said: IMHO,

kamaaina said: IMHO, traditionally Tomato is the firmware with the best reputation for QoS because it's the easiest to setup and has the best options. DD-WRT and others I found confusing, and the stock firmware usually does not provide much options. Tomato has QoS options for SIP, Skype, SkypeOut, etc. Have you looked at the links provided in the about page: http://www.linksysinfo.org/index.php?threads/using-qos-tutorial-and-discussio... This thread by Toastman is great because he is the one who built the QoS component within Tomato. Here is another one as well: http://www.wi-fiplanet.com/tutorials/article.php/3800416/How-to-Manage-Traffi... Hope this helps.

FYI, tomato definitely always had the better working qos if we are talking about old units, because dd-wrt and tomato used the same old kernels, but their rules were much more advanced and they have a nice interface for it. 

But things have changed, dd-wrt is now using the latest 3.x kernel series and thus is able to use the latest qos algorithms e.g. codel, fq_codel etc., see:

http://www.bufferbloat.net/

Besides that dd-wrt qos has been completely overhauled and therefore works much better than 2 or 3 years ago.

rockman412
rockman412's picture
Jennifer Melfi said:  If I'm

Jennifer Melfi said:  If I'm the only one experiencing QoS issues on v119 on R7000 I may give it another try this weekend.

Not the only one.  Late pages in this thread http://www.linksysinfo.org/index.php?threads/tomato-for-arm-routers.69719/ indicate lack of bandwidth monitoring, lack of QoS, wireless dropping and a spontaneous high-ping bug.  There's also another flavor out besides shibby's, but it still has most these issues.

 

shibby 120 is suppose to correct the high-ping bug though Laughing

kamaaina
kamaaina's picture
@ Kong: Thanks for the update

@ Kong: Thanks for the update. I have to say, when I had DD-WRT on the R7000 I looked shortly at the QoS settings and thought that it provided many more options now and seemed improved. You are confirming the impression now, so it might be worth taking another look if a lot of things have changed under the hood as well. The last time I touched it in DD-WRT before was easily a couple of years back. The interface is a different beast though, I guess I am just used to the Tomato look. It is so easy to mess things up with the rules though. Definitely great once you have it working well and a case of never change a running system.

I have to say, even the stock firmware, in some cases, is heading in promising directions. You see Asus and Netgear now at least offering some QoS settings and even a few custom rules, nowhere to be found a few years back.

With 119 on the R7000, I guess we have to realize this is only the second release for the R7000, not everything might be perfect yet. It is actually surprisingly stable so far. No crashes, the wireless is stable, internet throughput great, OpenVPN keeps on running. Everything I use works so far and no household members have complained about anything.

The R7000 overall really seems to be a remarkable machine. I hope for the price tag it can match longevity expectations as well, then we'll have a true contender for a great device with all the firmware options and the horse power and the wireless range, what's not to like (from a user perspective).

Kong
Kong's picture
It is really funny, that OEMs

It is really funny, that OEMs start integrating QOS at a time where lots of people don't need the traditional qos anymore, if you are a SOHO user with 100MBit you actually don't need qos and a lot of people have such connections now.

Basic qos is good, e.g. to limit things like uploads that hog your line, but more is usually not needed for the majority.

Nowadays you have different problems, e.g. 2 y ago you had one or two wireless device in your house, now you have 5-10 or more and wireless needs to cope with that.

DD-WRT has changed a lot in the last 18 month, I added a handful of new features and BrainSlayer redesigned a lot of things in the background. We are seeing more diversity now, different wireless chips, cpu arches.

In the last 6 months dd-wrt has improved a lot, especially on newer models and with the cleanup that is happening now dd-wrt is really getting in shape now.

TomatoUser
TomatoUser's picture
I really want to like DD-WRT,

I really want to like DD-WRT, and have given it a shot many times in the past. I recently installed the Kong builds on my R7000, and the UI is just so painful to use (I must've been spoiled by Tomato). Even simple things like adding new static DHCP addresses has some crazy usability bug that is acknowledged in the official wiki: http://www.dd-wrt.com/wiki/index.php/Static_DHCP#Configuration (bold part).

For some people, UI isn't a big deal, and for them, DD-WRT is probably a good fit. After all, I'm absolutely certain its underlying capabilities work perfectly well. Still, at the end of the day, given that I not-too-infrequently log into my router to do stuff, the UI being difficult to use is a big minus *to me*. Still, I want to thank you (Kong) for your hard work on supporting R7000. One of the reasons I decided to buy the R7000 very recently was that I saw that custom firmwares were supported, with DD-WRT leading that charge. With custom firmwares around, I know that my router will continue to be supported even after NETGEAR decides to move on. And custom firmwares are almost always better than stock too :)

----------

NETGEAR Genie is painful to use in its own right (it's frickin' slow interface kills me, for one). Nevertheless, I think I'm going to stick to stock for a bit until Tomato stabilizes on the R7000. That said, thanks to shibby and all the other Tomato maintainers for their work on Tomato too! Have shibby's firmwares installed on my RT-N66 and RT-N10P, and they're rock-solid.

DougRoberson
DougRoberson's picture
That's odd, I have exactly

That's odd, I have exactly the opposite opinion. I tried Tomato and just didn't "get it," and quickly switched back to DD-WRT. It was much simpler for me to find and execute the functions that matter to me in DD-WRT.

koenBerg
koenBerg's picture
I thought I bricked r7000 too

I thought I bricked R7000 too using tomato (did the correct steps and went first back to Netgear). Got it alive again using this advise
and changing ip address on local computer:

IP address: 192.168.1.2

Subnet mask: 255.255.255.0

Default gateway: 192.168.1.1

Click OK button

http://forum1.netgear.com/showthread.php?t=88562

jd2014
jd2014's picture
I can't get past the login

I can't get past the login either. What a joke. I've had it with this lame router and the lame 3rd party firmwares that fix nothing as it is.

I really wish someone would bring a lawsuit against Netgear for a product that is bug ridden.

kamaaina
kamaaina's picture
You might want to look at
DougRoberson
DougRoberson's picture
jd2014 said: I can't get past

jd2014 said: I can't get past the login either. What a joke. I've had it with this lame router and the lame 3rd party firmwares that fix nothing as it is. I really wish someone would bring a lawsuit against Netgear for a product that is bug ridden.

Russian proverb say, if can't stand heat, stay out of kitchen.

djdawson
djdawson's picture
Girlpopup - I recently

Girlpopup - I recently thought I had bricked my R7000 (no ping response, no apparent response to any form of reset, etc.), but after seeing a post about repeated resets sometimes working I decided to give that try and it worked.

The longer story is that I tried to fallback to the stock firmware after playing with the latest dd-wrt kong build and the router never came back. I was about to order a serial cable when I found the post above (I forget where I found it) while looking for a description on how to open the R7000 (it's not obvious, or wasn't to me). I set up my laptop with a continuous ping to the router and then just started doing 10-second resets (not 30/30/30), and after three or four iterations of that my pings started working. I tried to re-flash the factory code via tftp, but they all timed out, so I just tried the web GUI and that worked. So, it apparently wasn't as completely bricked as I thought it was.

So, don't give up too quickly on an apparently bricked R7000.

HTH - Good luck!

Chun
Chun's picture
Guys, I need serious help.

Guys, I need serious help.

I have no idea what Im doing and Im running off of a Mac computer.

I had DD-WRT firmware and tried going over to Tomato without going to original Netgear R7000 firmware because a website said that if I change the extension to .bin it would work. Now nothing works. I cant get into the router because the user and password doesnt work, the 25 second reset button doesnt let me get in when I terminal 'telnet 192.168.1.1 233' - and i get 'RT- login: ' but I cant do anything.

I tried 30-30-30 and then a 5 second reset and that didnt work either.

Have I completely destroyed my router?

Kong
Kong's picture
 

 

Girlpopup said: Djdawson - I've recovered my R700 thanks to Shibby and Simol just a few days after bricked. Truth must be told, Tomato is really great but I came back to DDWRT because of my LAN needs. By the way, I've a brand new linksys ac 1900 waiting for an open firmware ;-)

 

I hope you didn't buy the 1900AC:-) OpenSource support for that unit is not coming in short. I haven't seen any commit on the OpenWRT mailinglist for that unit.

I looked at the unit and the available sources, but for me alone this is way too much work if I do it in my spare time. Since the EX6200 exactly meets my requirements at work, the broadcom dual arms will get the most attention now, since it is going to be used at work. Which means, I have lots of time for these units, not just spare time.

Even if the 1900AC gets support, it will take long and take even more time to be stable.

Still waiting for updated broadcom drivers. Units have been out there for more than 6 months now and the wireless drivers still have a few problems.

Thus I doubt the WRT 1900AC will be a replacement for the good old WRT54G within the next 12 month. With all those new features Beamforming/TurboQuam, DFS ... the driver complexity raises and thus it takes longer to fix all those tiny bugs, that are anoying if you want to have some real uptimes, e.g. I have RT-N16 or WNR3500L running with uptimes >6 month and they work like they have just been rebooted.

kamaaina
kamaaina's picture
 

 

Chun said: Guys, I need serious help. I have no idea what Im doing and Im running off of a Mac computer. I had DD-WRT firmware and tried going over to Tomato without going to original Netgear R7000 firmware because a website said that if I change the extension to .bin it would work. Now nothing works. I cant get into the router because the user and password doesnt work, the 25 second reset button doesnt let me get in when I terminal 'telnet 192.168.1.1 233' - and i get 'RT- login: ' but I cant do anything. I tried 30-30-30 and then a 5 second reset and that didnt work either. Have I completely destroyed my router?

 

You can find help here:

http://www.myopenrouter.com/forum/thread/56510/R7000-bricked-Flashed-DD-WRT-to-Tomato-cannot-login-user-pw-denied/ or otherwise will need a serial cable.

tonijj
tonijj's picture
Ive ran Kongs built in the

Ive ran Kongs built in the past, but had performance issues with the speed, so I switched to Tomato.

One thing that Im struggling with is DDNS. in DD WRT, when you choose Custom URL, you have the opportunity to type in your login credentials, username and PW. But in Tomato, you dont get that option, what the? :(

Furthermore, in DD-WRT, when choosing custom url, when adding the url, ie
http://dyn.encirca.com/auth/dynamic.html?host=ddns.johansson.pro

The request to the server actually gives the following, note the double domain name that the DD WRT does:

http://dyn.encirca.com/auth/dynamic.html?host=ddns.johansson.projohansso...

Any ideas? any had this issue as well?

drivel2787
drivel2787's picture
So for those of you running

So for those of you running tomato how is the stability? VPN speed is fast I assume? I am still on the stock firmware. I have never been TOO big on DD-WRT, I ran it on my WRT320N and I like it but I found a lot of slow down on internet connection speed, etc... I ran Tomato on the same router and LOVED it. I use to hate tomatoes until this came along :)

I've been waiting and debating flashing my R7000 to DD-WRT, but now that tomato is available pretty sure I want to flash this. So from those of you that have tested what are the pros and cons of going to tomato?

Also, I'm on stock firmware, so which do I use to install? The initial and then the final firmware?

kamaaina
kamaaina's picture
You can install with initial

You can install with initial and then the latest (currently 121). It's been very stable for me. Running the VPN client since version 118 and been going through 119,120, etc. Bandwidth monitoring not working, and QoS was not working, now (121) is partially, but not the same. I know after 4 releases of Tomato it's still "beta" at best but I am happy, it does most of what I want and is stable.

For the VPN client, I get about ~30-35 Mbit/s download on average, I would say, with PIA as the provider. It fluctuates quite a bit depending on day and time of day, can be anything between 25-48 Mbit/s. I do have the router OC to 1400 Mhz though. Checking as I type I get 28 down.

Looks like 200+ people have it running now and participate sharing their stats:
http://tomato.groov.pl/tomatoanon.php?model=Netgear+R7000

BaseBoy
BaseBoy's picture
Have it now 2 months running

Have it now 2 months running on my R7000 Must say its nice and stable. VPN works great with VyprVPN

Regards,

Base

Bob2014
Bob2014's picture
I have everything up and

I have everything up and running on my R7000, but I cannot get the AC mode working. Everything is n speed only. What settings do I need to change to make this work?

umesh
umesh's picture
Hi there guys I need help

Hi there guys I need help bought a brand new R7000 and flashed it from genie to tomato as per shibby video. The router even stated that the initial and the final install was sucessful and tomato was up and running after the flash. Then I decided to reboot the router so that i can enter the vpn credentilals. Once the router booted i just cannot connect to it any more. I have tried pingin it, telnet and even putty the lights are on and fine and i am using an thernet cable but i cannot connect all i keep getting is unable to connect message. Somebody please help

BaseBoy
BaseBoy's picture
Hey Umesh,

Hey Umesh,

Try to put your IP adres in by hand on your PC. The range is 192.168.1.1 > 192.168.1.254 and subnet 255.255.255.0 Then try connect to 192.168.1.1 Then it worked by me ;)

Regards Base

umesh
umesh's picture
BaseBoy said: Hey Umesh, Try

BaseBoy said: Hey Umesh, Try to put your IP adres in by hand on your PC. The range is 192.168.1.1 > 192.168.1.254 and subnet 255.255.255.0 Then try connect to 192.168.1.1 Then it worked by me ;) Regards Base

Sorry base boy thanks for your help but I am a newbie at this and any help would be appreciated as I don't know how to do this 

BaseBoy
BaseBoy's picture
Here you can see how you do

Here you can see how you do that ;) http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-i...

Ip adress you put 192.168.1.2
Subnet mask 255.255.255.0
gateway 192.168.1.1

when you done that press oke and in your browser you go to 192.168.1.1

umesh
umesh's picture
BaseBoy said: Here you can

BaseBoy said: Here you can see how you do that ;) http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-... Ip adress you put 192.168.1.2 Subnet mask 255.255.255.0 gateway 192.168.1.1 when you done that press oke and in your browser you go to 192.168.1.1

Her there base boy thanks for the reply it worked and I am up and running I thought I had bricked the router. Just moved from a Asus n66u to R7000 and was hoping to get past 20mbps thinking it was a CPU bottleneck buy still stuck on 20mbps anyone out there getting past this speed with IP vanish VPN 

BaseBoy
BaseBoy's picture
Hey,

Hey,

Have also VPN running but my speed is reaching more, so think its a other problem ;)

umesh
umesh's picture
Hi there guys I need help

Hi there guys I need help bought a brand new R7000 and flashed it from genie to tomato as per shibby video. The router even stated that the initial and the final install was sucessful and tomato was up and running after the flash. Then I decided to reboot the router so that i can enter the vpn credentilals. Once the router booted i just cannot connect to it any more. I have tried pingin it, telnet and even putty the lights are on and fine and i am using an thernet cable but i cannot connect all i keep getting is unable to connect message. Somebody please help

BaseBoy
BaseBoy's picture
Hey Umesh,

Hey Umesh,

Try to put your IP adres in by hand on your PC. The range is 192.168.1.1 > 192.168.1.254 and subnet 255.255.255.0 Then try connect to 192.168.1.1 Then it worked by me ;)

Regards Base

umesh
umesh's picture
BaseBoy said: Hey Umesh, Try

BaseBoy said: Hey Umesh, Try to put your IP adres in by hand on your PC. The range is 192.168.1.1 > 192.168.1.254 and subnet 255.255.255.0 Then try connect to 192.168.1.1 Then it worked by me ;) Regards Base

Sorry base boy thanks for your help but I am a newbie at this and any help would be appreciated as I don't know how to do this 

BaseBoy
BaseBoy's picture
Here you can see how you do

Here you can see how you do that ;) http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-i...

Ip adress you put 192.168.1.2
Subnet mask 255.255.255.0
gateway 192.168.1.1

when you done that press oke and in your browser you go to 192.168.1.1

Pages