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

Will Netgear R7000 be supported by tomato?

Discussion in 'Tomato Firmware' started by MrDoh, Nov 4, 2013.

  1. MrDoh

    MrDoh Networkin' Nut Member

    Just wondering if support will be added to my favorite third-party firmware for the Netgear R7000? I know that DD-WRT has this support already, but I'd rather use tomato.

    That would be wonderful!

    Thanks very much.
     
  2. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    If Victek is able to successfully port to ARM, then maybe.
     
  3. MrDoh

    MrDoh Networkin' Nut Member

    Good to hear, there's hope then.

    Thanks much.
     
  4. lightsword

    lightsword Serious Server Member

    Tomato for Broadcom-ARM will almost certainly going to be based off of AsusWRT sources, I'm going to make an attempt to get the R7000 added under AsusWRT-merlin for the time being then I may try and port tomato. The whole build environment will need to be re-based since it is an entirely new platform so it may take some times.
     
  5. Toastman

    Toastman Super Moderator Staff Member Member

    This is the way to go. I wish you every success with the port of Tomato.
     
  6. Toastman

    Toastman Super Moderator Staff Member Member

    I'm sure a few photos would be of interest.
    |
    netgear_7000_asus_rtac68u_opening.jpg
    |
    20131105_131612.jpg
    |
    |
    20131105_131835B.jpg
    |
    |
    20131105_131950.jpg
    |
    |
    20131105_131956.jpg
    |
    |
     
  7. Toastman

    Toastman Super Moderator Staff Member Member

    R7000 has:

    BCM4709A dual-core 1GHz processor inc LAN switch + 128MB flash memory and 256MB RAM.

    Broadcom BCM4360 + Skyworks SE2623L 2.4 GHz Power Amp (x3) of which spec is:
    • +23 dBm, EVM = 1.8 %, MCS8 (200mW)
    • +26 dBm, EVM = 3 %, 802.11g, OFDM 54 Mbps (400mW)
    • +26 dBm, ACPR < –32 dBc, 802.11b (0.4W)
    • up to 600Mbps at 2.4GHz
    Broadcom BCM4360 + Skyworks SE5003L1 5 GHz Power Amp (x3) of which spec is:
    • +19dbM (80mW)
    • up to 1300Mbps at the 5GHz band

    3 external presumed dual-band antennas (there are no internal antennas)
    2 USB ports - USB2 (rear) USB3 (front)
    12v 3.5A PSU
    default IP is 192.168.1.1
    login: admin / password: password


    Power Conversion: http://www.rapidtables.com/convert/power/dBm_to_Watt.htm
     
  8. Victek

    Victek Network Guru Member

    curious .. low power a 5GHz ... about CPU and periphericals it's RT-AC68U with an additional USB2.0 port. If price is lower then go for R7000 ... ;) and.. no heatsink ...so good for Tropical countries... U153 ... RTC socket?
     
  9. szpunk

    szpunk Networkin' Nut Member

    I buy what you buy, haha~
     
  10. RMerlin

    RMerlin Network Guru Member

    RT-AC68U has a BCM4708, versus a BCM4709 for the R7000. Main difference is the CPU clock and the supported DDR clocks.

    Netgear released the GPL for their firmware. It's not as extensive as Asus's (a lot of stuff is provided pre-compiled), but you get at least the source code to the kernel (I saw very little differences to Asus's kernel).
     
  11. kyrios

    kyrios Serious Server Member

    Then I'll receive what you dump :p
     
  12. lightsword

    lightsword Serious Server Member

    Simply put the netgear is better hardware, but is still very close the RT-AC68U, I'll be attempting to modify asuswrt-merlin for compatibility with the R7000 by merging any hardware related differences between the RT-AC68U codebase. From there the tomato userland code can start getting merged in.
     
  13. Toastman

    Toastman Super Moderator Staff Member Member

    Vic, in fact, there are thermal pads between some of the chips and the screening can, and more thermal pads between the screen which press against a thin metal heatsink screwed into the router case. I removed them to take the photos.
     
  14. Victek

    Victek Network Guru Member

    Ah, so you have it! ... I thought pictures was from Internet ... another router to tomato?
     
  15. shibby20

    shibby20 Network Guru Member

    well victek has ac56. i have ac68 and toastman has R7000 :) now we have to make tomato for those routers... should be "easy" :D
     
  16. lightsword

    lightsword Serious Server Member

    I'm forking off of asuswrt-merlin since its a completely new architecture and pretty much straight from asus sources https://github.com/RMerl/asuswrt-merlin it would be good to have one place for everyone to submit changes to the core base. I'm starting with the R7000 but I'm still fixing up a bunch of compile errors.
     
  17. Victek

    Victek Network Guru Member

    shibby... I like your "joke" ... lightsword if you plan to use asuswrt sources then maybe RMerlin can allow a fork in his git, I don't know if he's planning to extend asuswrt to another non asus models.
     
  18. lightsword

    lightsword Serious Server Member

    I've already forked it here https://github.com/Lightsword1942/asuswrt-merlin and have submitted some pull requests to fix up a few things. Github makes this type of thing easier as anyone can fork a project. If RMerlin wants to keep asuswrt only for asus devices other devices can always be added on a separate fork.
     
  19. RMerlin

    RMerlin Network Guru Member

    I have no intention of supporting other routers personally - Asus's routers are already a lot of work to support. And Asus having gone out of their way in supporting me so far, it would be a lack of respect on my part to start supporting their competitors while getting free development devices and occasional pre-release code to play with.

    Don't forget to remove anything that is licensed specifically for Asus however. That means you will have to remove Asuswebstorage, support for Asus DDNS (which requires an Asus MAC anyway), AiCloud, their ufsd driver, and probably somre more. Otherwise, you might run into legal issues.

    I didn't see from where you forked, but it would probably best to fork from the 374.34_2 code. Current head is very much a work-in-progress, especially regarding OpenVPN.
     
  20. lancethepants

    lancethepants Network Guru Member

    I think quite the opposite. The more diversity people have with firmware, the more people are willing to buy that router. I don't think Asus cares so much what firmware you're running, so long as you're purchasing their hardware. If such a stance were true, then I would suggest that Asuswrt is also a competition to them really. Any choice apart from the stock firmware is some sort of competition. Rather, any force promoting their hardware is one I think they should even more support. I know my thoughts wouldn't have turned to Asus for routers, hadn't tomato existed. Now I know I will only purchase Tomato/Open Source supported routers, be it Asus, or any other manufacturer that will be sufficiently friendly with the open source community. That's my thought, and in no means intend to offend.

    So far, much has been borrowed from you anyway, you help already with the right dosage tomato needs.
     
    Last edited: Nov 6, 2013
  21. RMerlin

    RMerlin Network Guru Member

    I was talking from a hardware point of view, not from a firmware point of view. Taking Asus's code and making it run on non Asus-hardware would just be wrong on my part seeing the support Asus has given me.

    And to be honest, I don't care much for Netgear products in general. Never had any positive experience with their products, either myself or with my customers.
     
    lancethepants likes this.
  22. lancethepants

    lancethepants Network Guru Member

    Ah, understood, and agree. Should have caught you were speaking about netgear products.
     
  23. lightsword

    lightsword Serious Server Member

    Understandable, I won't do any pull requests for supporting other hardware to your repo in that case. I think I forked right off of head but I can always fetch the upstream change for OpenVPN once it is fixed up, so as long as its not breaking compiles I won't worry too much about it yet. I may do a few test builds without modifying any of the Asus specific components but I don't intend to leave them in long term. The ufsd driver is licensed by Netgear as well so I don't think there should be any issues using that, although it could probably be pulled in from the Netgear sources if needed directly.
     
  24. RMerlin

    RMerlin Network Guru Member

    What you should probably start doing is stripping off the bits you don't need, like those proprietary bits. After that, you can start merging in the Tomato-specific bits, component by component.

    For ufsd, you could replace Asus binary blob with Netgear's own. Those blobs have actual "signatures" in them stating for which router they were compiled by Paragon. You will have to make sure your kernel options are as close as possible to Netgear, as otherwise the module might fail to properly load.

    For OpenVPN, a large portion of it is at the webui level, so it's something you should worry too much about at this point, as you will have to totally scrap the webui to merge Tomato's UI in place. I might do a few minor tweaks to rc/openvpn.c and other rc-level stuff specific to OpenVPN, but shouldn't be anything major at this point.
     
  25. lightsword

    lightsword Serious Server Member

    I mainly want to make sure I have something buildable before I start pulling off some of the ASUS components and dealing with the webui, do you know if the ufsd signatures are kernel specific or if it actually does some kind of hardware detection? I suppose I can just test that to find which version works better. Hopefully the broadcom kernel from ASUS sources is universal enough I don't really have to change much in relation to the kernel config. I'm thinking the best way to work everything is to have staging levels. So basically it would flow something like asuswrt(tarball)>asuswrt-merlin>asuswrt-merlin(with other OEM hardware configs)>basetomato>tomato-mods. That would appear the easiest method for staging any upstream changes that come from asus/broadcom and distributing them down to all additional mods, it would also probably make debugging changes from upstream easier since we would be able to see when they actually break and if it is a hardware config issue vs userland/gui issue.
     
  26. RMerlin

    RMerlin Network Guru Member

    By signature, I mean this:

    Code:
    admin@Stargate3:/tmp/home/root# strings /lib/modules/2.6.36.4brcmarm/kernel/fs/ufsd.ko | grep Build
    Build_for__Asus_RT-AC56U_k2.6.36_2013-01-18_U86_r195788_b2
    
    Asus had to pay Paragon to get a license that is specific to their routers. If you take that licensed module and use it on a different router, you might be in legal trouble, and face the risk that either Asus or Paragon ask you to take the file out, or shut down the whole project. And as you can see, a single string command can determine from where your binary blob is coming from.

    And there is also the fact that this module is compiled for specific kernel options. For instance, Asus has both an smp and a up build of it in the tarball, the up was probably intended either for testing or for a future ARM-based router that might be single core.
     
  27. lightsword

    lightsword Serious Server Member

    Ill try and make it work with the netgear one if possible, its probably not that big an issue since netgear has licensed the module as well. Removing it(if any issues come up) would pretty much just amount to a config change since everything is going to be based off of the same build system. This doesn't really seem all that different from how broadcom and other drivers routinely get cross ported between devices that have licensed the software in some form already.
     
  28. lightsword

    lightsword Serious Server Member

    I've started to commit changes from Netgear sources, these will need to be vetted and may need to be config flag sensitive. Currently these are just quick comments on the merges, I've tried to alert if they may break things. https://github.com/Lightsword1942/asuswrt-merlin/commits/R7000 If anyone wants to start going through and weed some stuff out that would be helpful. Ill then merge the patches that don't break things into a seperate tree. For reference I am basing off of the Netgear sources here https://github.com/Lightsword1942/R7000
     
  29. jerrm

    jerrm Network Guru Member

    The difference is Broadcom has basically accepted the practice - it only helps sell chips. Paragon may be a little more picky, there is little benefit for them to allow it.

    ASUS/Netgear may both license the driver, but hopefully this will be the base for other platforms that will not have the license. Obviously not a day one issue, but there will need to be a "no-paragon" and model-specific config options. Understand it's one step at a time.
     
  30. lightsword

    lightsword Serious Server Member

    Model specific configs can already be customized, unless the driver has actual copy protection it would probably be a single config flip switch to enable/disable it.
     
  31. RMerlin

    RMerlin Network Guru Member

    Paragon has different versions and different licenses. For instance, Asus has a license for NTFS support on their N16/N66/AC66U router, but an NTFS + HFS+ license on their AC68U. That's why they might not look favorably to different licensed builds being moved around.
     
  32. lightsword

    lightsword Serious Server Member

    I've been merging device specific changes to a new branch here https://github.com/Lightsword1942/asuswrt-merlin/commits/downstream . These should hopefully be ones that don't break other devices. Let me know if you think there is anything will cause an issue or if there's something missing. I've left a lot of changes out since they seem to not be hardware related.
     
  33. lightsword

    lightsword Serious Server Member

    I've made some merges on the board config, can someone check my conditional if's are correctly isolating the R7000 definitions, there were quite a few to deal with. https://github.com/Lightsword1942/asuswrt-merlin/commits/downstream I have most of the configs merged so it should be fairly close once I get these board definitions dealt with since the layout is pretty different. If using native board configs ends up being an issue I'll probably just scrap the individualized configs and make generics. I'm not sure if using generic partition layouts will have an affect on flashing between stock and tomato firmware though.
     
  34. juggie

    juggie Addicted to LI Member

    Any news to report on this project?
     
  35. lightsword

    lightsword Serious Server Member

    Not much yet, I've been busy the last few weeks, should have some time soon though. I've worked up a few things in regards to workflow but need to finish bug hunting for a special high performance development Virtual Machine that I want to be able to use, It should make it easy for anyone to get set up for compiling/development quickly without many of the performance hurdles that normally exist for VM's. Compiling for these ARM boards just takes forever and significantly slows down development otherwise, and I have a very fast desktop even. The board configs are what I'm worried about, I'm going to probably need testers and there are almost certainly going to be soft bricks, meaning serial console at a minimum for any testing. There are just a lot of differences in the configurations and in all likelihood I'm going to be taking DD-WRT's universal board config and attempting to adapt tomato to use that, anything else will probably not be maintainable and I kind of think the DD-WRT guys know what they are doing when it comes to this part at least(they port way more new broadcom devices than anyone else).
     
  36. JAC70

    JAC70 Networkin' Nut Member

    Hi lightsword, and thanks for your work thus far. I'm not asking for a timeline, but are you able to confirm that there will be a fully functional Tomato version for the R7000 at some point? I ask only because I have a 30-day return window on this router, and the Netgear firmware is something of a joke compared to Tomato.

    Cheers.
     
  37. Cheval

    Cheval Network Guru Member

    Any update on this at all? Would really like to get Tomato working on my R7000. :)
     
  38. MrDoh

    MrDoh Networkin' Nut Member

    Really curious about what's going on with tomato for the R7000 as well. I've heard so far that Toastman is working on it, and there are references to it in the thread that Victek is responding to. Just wondering if anyone is making progress with this, since I've heard that there is beta test going for the Victek's work, and that's apparently being developed and tested on an Asus RT-AC56U?

    Would appreciate any information about this, really would like to see tomato running on the R7000! I'm a pretty patient person *smile*, but hearing about Victek's progress is prompting me to ask.

    Thanks much.
     
    mito likes this.
  39. mito

    mito LI Guru Member

    Hey Vic, the voice is running fast! Hope you really are on a Beta for R7000 the most powerful router in the market and with Raf will be a tsunami!
    salu2;)
     
  40. lilstone87

    lilstone87 Serious Server Member

    This really has me interested as well, seeing just recently what shibby is doing with the ASUS AC68U. Would be nice to have a update regarding the R7000, if there is anything regarding a tomato build.
     
  41. shibby20

    shibby20 Network Guru Member

    I`m making tomato for AC68 because i have this router in my hand. But i`m really working on support ARM to Tomato. When i will be done, then should be very easy add support other ARM routers like R7000, AC56U or Trendnet TEW-812DRU (i own the last one).
     
    mito likes this.
  42. lilstone87

    lilstone87 Serious Server Member

    i appreciate you taking the time to reply, and appreciate ur work shibby. just recently i started using the R7000, as i was using a N66U. In which i was very happy when you made speeds better with a ntfs drive. I am ready to use tomato on this R7000, as i perferr the QoS within tomato :).
     
  43. shibby20

    shibby20 Network Guru Member

    can you tell me your speed from USB?
     
  44. szpunk

    szpunk Networkin' Nut Member

    Is TEW-812DRU ARM based? I saw this on smallnetbuilder that say it's 4706:

    http://www.smallnetbuilder.com/wire...dru-ac1750-dual-band-wireless-router-reviewed

    and TEW-811DRU is 4708:

    http://www.smallnetbuilder.com/wire...dru-ac1200-dual-band-wireless-router-reviewed
     
  45. shibby20

    shibby20 Network Guru Member

  46. lilstone87

    lilstone87 Serious Server Member

    I was getting like 17MB's copying to the drive, which was around same as merlin's builds. if i remember correctly copying from drive speed's were about the same. i know before you made the change right around 3MB's was max sadly.

    Edit: Also I have used DD WRT recently on the same drive, but with the R7000, and I was getting between 24-26MB's writing to the drive via NTFS, and copying from the drive was around 20MB's. I dunno what kind of NTFS driver being used within DD WRT for the R7000. Also if I remember correctly, with the netgear firmware for the R7000. I was able to get like 44-46MB's writing to the drive, and around 40MB's copying from the drive.

    Btw the edited part of this post, the drive(2TB Seagate USB3) was connected to the R7000 via USB3 port.
     
    Last edited: Feb 21, 2014
  47. mito

    mito LI Guru Member

    Great shibby to hear from you about you are close to get support for R7000:D
    It is an impressive router with poor OEM firmware, but great possibilities with third part firm.
     
    Last edited: Feb 22, 2014
  48. mito

    mito LI Guru Member

    Hey Vic what about you, any posibilities on ARM firm for R7000?
    Are you on it?
    Salu2
     
  49. Victek

    Victek Network Guru Member

    Yes, once ARM kernel and drivers will run it's only a job to identify IRQ and interface in the device to be ported (I said between brackets..)
    The fact now is the huge amount of IF we are inserting in tomato code to share common files for both platform (ARM and MIPS). It makes tomato tricky with the clean tree we had before.
    We (shibby and me) have some discussions in the way to go, creating one branch only for ARM (shibby's proposal) or creating a common branch for all platform (not only restricted to ARM since RALINK can be included too)....
    In resume.. yes, it's posible to include other models (EA6900, R7000, DIR-812...).

    Cheers!
     
    Elfew, desiromeo and mito like this.
  50. mito

    mito LI Guru Member

    Hi Vic, thx for your time to reply.
    Yes I get what is going on with the development of the Tomato tree.
    Since you both are working on that, obviuosly you have to decide in which way to go, from a general point of view I would go first to the branch that would have more units to flash including also the router's market tendency.
    Salu2
     
  51. Victek

    Victek Network Guru Member

    One example of the actual status... ;) ... we are in the right way but still many issues to solve. The main problem is to implement all tomato features and maintain the specifications. The decision is not critical, my way represents a lot of work but then all platforms will be in one tree. It's a development decision and doesn't affect to the end user.

    Screenshot from 2014-02-26 18:33:06.png
     

    Attached Files:

    Last edited: Feb 26, 2014
    mito likes this.
  52. mito

    mito LI Guru Member

    Vic, yes i get your way, all platforms in one tree.
    Thx a lot for your work, saw your attachm.
    This is a nice surprise and a great update:)
    We hope you have another update soon;)
    Abrazo.
    Regards
     
  53. MrDoh

    MrDoh Networkin' Nut Member

    Good to see that the R7000 is being planned. Love to see a beta to try out at some point *smile*.

    I know, don't put the cart before the horse, trying to keep my enthusiasm in check, not easy *smile*.

    Thanks.
     
  54. lightsword

    lightsword Serious Server Member

    I've been busy lately but I've been working with a source management system that might be helpful for this, it is similar to the repo system google uses for android's source code but also allows mercurial alongside git. Hopefully I get some time to try using it with tomato.
     
  55. sandspike

    sandspike LI Guru Member

    Any thoughts on how soon the R7000 could be supported? I need a new router and it's between this and the RT-AC68U. Big thing is I need it to support 300Mb/s-1Gb/s internet. The R7000 seems to be the best hardware, But with shibby and merlin supporting the ac68u, that is powerful.

    Sent from my SM-N900V using Tapatalk
     
  56. jsmiddleton4

    jsmiddleton4 Network Guru Member

    See thread on Tomato ARM support.
     
  57. shibby20

    shibby20 Network Guru Member

    I should have R7000 in next week. Please be patience

    Wysłane z mojego S-line przy użyciu Tapatalka
     
  58. JameZUK

    JameZUK Reformed Router Member

    Shibby, thats great news! :)
     
  59. TyShawn

    TyShawn Reformed Router Member

    That is great news to hear as I have my router coming next week too.
     
  60. sandspike

    sandspike LI Guru Member

    Very cool, thanks brother, I will be looking for a deal on the R7000.

    Sent from my SM-N900V using Tapatalk
     
  61. MrDoh

    MrDoh Networkin' Nut Member

    So glad to hear that. Please be sure to come back here and mention it when it's ready for testing, or do you use another thread? Currently using dd-wrt with the R7000, but would be happy to be able to use tomato!
     
  62. mito

    mito LI Guru Member

    Last edited: Apr 23, 2014

Share This Page