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

Tomato for ARM routers

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

  1. lancethepants

    lancethepants Network Guru Member

    I did as was recommended in this thread. I held the reset button for 20 seconds. This activates telnet on port 233. Then I just used telnet to get cli access. If using windows to telnet, it is 'telnet ipaddress port'. Just a space between the ipaddress and the port From there you can run 'nvram get http_passwd', and use that to get gui access into tomato.
     
  2. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Sorry going back to Netgear's. Was fine last night but today with multiple wireless clients everyone is dropping on both 5ghz and 24ghz channels. As noted above the wireless driver version seems to be flakey.
     
  3. hawkmat

    hawkmat Networkin' Nut Member

    Hi jsmiddleton4
    The save button is not working on Advanced/DHCP/DNS page. This appears to be a javascript error. I found a work around. Use Internet Explorer and put it in compatability mode. Hitting the save button now works. Setting are saved. Thanks!
     
  4. thedak

    thedak Connected Client Member

    Thanks, found that as well. Shibby posted elsewhere (thanks so much!!!) the follow procedure that works perfectly:

    1) run router and wait 2-3
    2) push and hold wifi on/off button for 25 secs - this will enable a "backdoor" access to the router.
    3) use putty and connect via telnet on port 233 and log in to router without password
    4) run command: nvram get http_passwd (login`s value: nvram get http_username)
    5) use result as password
    6) when you log in to tomato remember to erase nvram
    7) do other steps from INSTRUCTIONS file.

    and actually, you can do "nvram set http_passwd=value" (as well as for http_username) and use those clear text values to log into the gui.
     
    Last edited: May 25, 2014
  5. jsmiddleton4

    jsmiddleton4 Network Guru Member

    I can't go back to Netgear's. Getting this message:

    /tmp/flash3lDTtD: Bad trx header
     
  6. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "Hitting the save button now works."

    If I can't get back to Netgear's I'll have to try this.
     
  7. 0007Rraegten

    0007Rraegten Reformed Router Member

    You can use nvram set like this:
    nvram set dns_intcpt="1"
    nvram set dnsmasq_custom="cache-size=10000
    log-async=5
    strict-order"
     
  8. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Had to do reset again and then I was able to return to Netgear's. Will wait for Shibby's 120.....
     
  9. MaX PL

    MaX PL Networkin' Nut Member

    why not use the initial build? i've had it running fine for weeks now.
     
  10. sandspike

    sandspike LI Guru Member

    118 is working well here, was excited about 119, but it sounds like there are still issues there.

    Sent from my SM-N900V using Tapatalk
     
  11. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Go back to 118?

    Because the router is not used in a vacuum. The people who use the wireless need to be able to not have issues. Shibby will get a stable reliable version worked out. 119 just isn't it yet. Not in any hurry......
     
  12. Dioden

    Dioden Reformed Router Member

    Hi

    I have a R7000 with 1.28.0000 -118 K26ARM USB AIO-64K running on it.
    Everything is fine eksept from the PPTp VPN Server stops. It only works for some minutes after restart/save.


    Regards
    Dioden
     
  13. blackmack

    blackmack Addicted to LI Member

    Hi shibby. Will it be possible to speed up USB 3.0 transfer on AC68U in future (USB 3.0 2,4 ghz interference set to disable on stock firmware)?
     
  14. NoisyNinja

    NoisyNinja Reformed Router Member

    Hi does anyone know if the CPU in the netgear R6300 v1 is considered an ARM variant? I notice people reporting that the arm build works on v2 (dual core BCM4708) but I wasn't sure if it would work with v1 (single core BCM4706).

    Any insight would be appreciated!
     
  15. MrDoh

    MrDoh Networkin' Nut Member

    According to:

    http://www.broadcom.com/products/Wireless-LAN/802.11-Wireless-LAN-Solutions/BCM4706

    the CPU of this one is of the MIPS variety. The BCM4707/4708/4709 all include ARM CPU's, though.
     
    NoisyNinja likes this.
  16. NoisyNinja

    NoisyNinja Reformed Router Member

  17. Victek

    Victek Network Guru Member

    Tomato RAF ARM Platform version 1.3f ready. Changelog / Fixes:

    _ Wireless driver 6.37.14.73 (r448163). Mature and stable.
    _ Quagga replaced Zebra (not working in ARM platform).*
    _ Quagga RIP + GUI. (Advanced/Routing GUI).*
    _ Quagga OSPF + GUI. (Advanced/Routing GUI).*
    _ dnsmasq update to 2.71.
    _ DNSSEC + GUI (Basic Network GUI).**
    _ SQlite: Updated to version 3.8.4.3.
    _ OpenVPN 2.3.4. Update and Tomato customization.
    _ TCPDUMP + GUI (Tools).*
    _ UCARP + libpcap.*
    _ Dnscrypt updated to 1.4.0.
    _ miniupnpd 1.8 updated and revised to release May 23, 2014. Tomato customization.
    _ GMP updated to version 6.0.0a for DNSSEC.
    _ Dnscrypt resolvers and options combo list.**
    _ Netflow + GUI (Administration/Netflow).*
    _ Minidlna version 1.1.2. Update and customized for Tomato.
    _ Comcast DSCP IPv6 fix (in firewall GUI).
    _ Update libsodium to version 0.5.0.
    _ ipv6: don't install anycast address for /128 addresses on routers.
    _ dropbear: sftp correct path as in Tomato RAF.

    * Aaron Finley.
    ** Lance Fredrickson (lancethepants)

    Version for R7000, RT-AC56U and RT-AC68U.
    Note: All these updates are adapted from Tomato RAF MIPS platform.

    Download: victek.is-a-geek.com Downloads page.

    Procedure: Restore Factory Default configuration, Upgrade with Erase NVRAM option ticked, Access to GUI, Press Reboot and Configure from scratch.
     
    Last edited: May 27, 2014
    Iceman_jkh, MrDoh, Edrikk and 6 others like this.
  18. Connor McCaffrey

    Connor McCaffrey Serious Server Member

    are you using the paragon drivers for usb 2 and or usb 3? if not are they any versions of tomato arm that are?

    im curious the USB 2 performance of the R7000 vs RT-AC66U running Shibby 119

    also curious of USB 3 performance on R7000. since with stock firmware its 50-70MB/s
     
  19. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Going to Victek's web site now. Do we do the initial firmware thing first?
     
  20. Edrikk

    Edrikk Network Guru Member

    WOAH! Will try out the R7000 after work/kids are asleep..
    So excited to be on the Victek train! :)
     
  21. Victek

    Victek Network Guru Member

    If you use Netgear firmware then yes... if not just Upgrade but following the procedure.
     
  22. The Master

    The Master LI Guru Member

    Thanks Victek for your hard work (and Shibbys). But iam a bit Confused now.... what are the MAIN differenzes to Shibby Build?!

    @ MY N-16 iam a Victek FW User for a Long time but at the R7000 i dont know what i Need more ... and i dont really see a Differenz.

    It would be nice if Victek and Shibby could make a Chart for the differenzes and Main Funktions for the FW.

    And as ALWAYS I LOVE BOTH FW :D
     
  23. Victek

    Victek Network Guru Member

    ;) I expected this question and this is the reason why I don't release ARM version often, read the changelog wrote by shibby, read my changelog; I tried to be very precise, then you can conclude you are in front of two releases totally differents, like one lemon vs one banana... :) (yellow cover is similar... inside there is another approach).
     
    Edrikk likes this.
  24. Edrikk

    Edrikk Network Guru Member

    There are enough differences (if you even look at the GUIs carefully) that you'll notice they two are "similar but different".

    I personally use Victek's builds on my routers. I can't express how happy I am that Victek is releasing R7000 builds. As a former developer, I appreciate Victek's focus on quality. Not only because of the outcome, but also because (again as a former developer), I know that fixing bugs is not as 'fun' as putting in the new sexy functionality...

    I strongly urge you ARM folks to donate to Victek as well. We wouldn't have Tomato ARM if not for Vincente.
     
  25. jackyqxl

    jackyqxl Network Newbie Member

    this initial? tomato-R7000-RT-AC6x--118-initial-64K.chk
     
  26. jsmiddleton4

    jsmiddleton4 Network Guru Member

    And if we want to return to Netgear's Genie same return process as Shibby's? The return to netgear firmware file?
     
  27. The Master

    The Master LI Guru Member

    Its not only for the ARM Version ists for the MIPS Version the same....

    Its hard for a User to find the Differences in the FW for THERE (the Users) needs.
    And for you (the Devs) its hard to find the Problem in "one" FW.
    Example: User 1 writes about bad Wlan, User 2 writes about NO PROBLEM. Both same FW with only ONE difference "MODUL" in the FW thats causes the Problem.

    I know that this is for 1 FW with only 1 other Modul. Its better to have a "LOG" for both FW to Compare and LEARN from the other, so that the other FW does not have to go the HARD way to find out that THIS or THAT Module makes a HUGE Problem.....


    Sorry i am driffting away...


    Here is a Commperison...(quick and dirty)<- Too Dirty... one Moment..


    [​IMG]
     
    Last edited: May 27, 2014
    wmz0731, szpunk and MrDoh like this.
  28. MrDoh

    MrDoh Networkin' Nut Member

    Okay, haven't used Victek firmware before. I would be coming from dd-wrt, and would go back to dd-wrt if I needed to. It looks like I could just flash this new tomato firmware from dd-wrt. Then, to return to dd-wrt, just flash dd-wrt from there? Assuming that I erase nvram contents as recommended?

    Thanks!
     
    Last edited: May 27, 2014
  29. lilstone87

    lilstone87 Serious Server Member

    Well I just flashed Vic's R7000 build on my router, going from the netgear firmware using shibby's install steps. I will say, if your one of the one's having issue with pings being all over the place. This issue is indeed still a issue even with Vic's build. Shibby said he comfirmed this issue, so I suggest waiting on shibby's next build to get this ping issue corrected with the R7000.
     
  30. lilstone87

    lilstone87 Serious Server Member

    Also tested my USB3 drive connected to router using Vic's release, and here are the results I got compared to Shibby's build for the R7000. Shibby 13MB's writing to the USB3 drive using NTFS, and Vic's I got 22MB's writing to the drive. So almost a 10MB's jump between the two. Still noticed using either build, transfer speed's to the drive were up, and down, not as steady as I would like.

    Reading speed from the drive, transferring file back to pc. Shibby's was 32MB's using USB3 NTFS drive, and Vic's was 28MB's. So for me, the NTFS driver Vic is using is better for me. As I mention in post above, the R7000 PING issue is still a problem with Vic's build.
     
  31. Victek

    Victek Network Guru Member

    What's wrong with <1ms ping? :confused:
     
  32. Victek

    Victek Network Guru Member

    a) zlib to 1.2.8 was already updated in RAF since April 22, revision 1.3d. https://github.com/Victek/Tomato-RAF/commit/d11f89c1a7ba3b1c352e27e0caf7bed27e94eba7
    b) Web server is in RAF since ~ 11 months ago.
    c) Access restriction to web method is in RAF since ~ 9 months ago.

    The comparison is difficult .. one comma can provoke a bug... but it's a good guide for all.
     
    Last edited: May 27, 2014
  33. lilstone87

    lilstone87 Serious Server Member

    Vic,

    Right after flashing your build, I notice pings being all over the place like Shibby's build. As I ran a steady ping to the router while flashing tomato like shibby does in his video. I did however enable CTF, and ping's were still bouncing around. However I decided to reboot the router after enabling CTF, and pings have been staying in the 1-2ms range now.

    But I have seen this same thing with Shibby's build, and later on pings started jumping around again. So I am gonna monitor your build for a little while. Because if this ping issue returns, running this build will be a no go for me. Also the pings for me, when it is a issue, pings jump around from 1ms-200+ms.
     
  34. Victek

    Victek Network Guru Member

    OK, let's see your findings. My router is the gateway to my web site 24/7 .. you can compare too. ;)
     
  35. lilstone87

    lilstone87 Serious Server Member

    Vic,

    Again I appreciate both the work you, and Shibby are doing for the R7000. As I am a big fan of Tomato, and hope in the future QoS can be a working feature with ARM build's.

    Also regarding the NTFS driver, do you know what is different between your build, and Shibby's? I get better writing speed's to my NTFS drive on your's compared to Shibby's. But like I mentioned above, when writing to the drive transfer speeds seem to jump around a bit. More then I would consider normal, compared to using netgear's build, or Kong's DD WRT build.
     
  36. boghea

    boghea Reformed Router Member

    Hi Victek, are there plans to include transmission in your build?
     
  37. Victek

    Victek Network Guru Member

    It's really difficult for me to say what's different in shibby's builds or any other firmware and RAF version, any of us works to optimize the unit and as I mentioned before, one comma might sound different. It's also the difference between a 'copy and paste' and one developer (I consider myself with not enough skills to be a developer, but I like the hobby)...
     
  38. lilstone87

    lilstone87 Serious Server Member

    Vic,

    Also forgot to screenshot when pings were all over the place, after flashing your build. I am in no way just saying stuff to be saying it. As I want the best for us all, and I wonder what Shibby's findings were regarding the ping issue with his build. As he did say he comfirmed it as an issue. I thought about turning CTF back off with your build, but it's running steady atm, and don't want to see pings jumping all over the place again.
     
  39. Victek

    Victek Network Guru Member

    No, I have in my TODO an aria2 project, I consider it consumes less resources, but I have also a NAS at home for it. One router is not a NAS and you see the features added to RAF version are going to 'network' apps.. it's a router.
     
    The Master likes this.
  40. Victek

    Victek Network Guru Member

    mmmm... I fixed one issue in two builds ago.. look at miniupnpd debug ... if my release works stable then we know the reason and there is a difference in code between the way shibby or ASUS handle miniupnpd and RAF version. This fix avoids ping storm in the net...
     
  41. The Master

    The Master LI Guru Member

    THX Victek... for the explanation...

    I hope you understand me a little bit with the difficulty of the two FWs... and that my question maybe sounded like a attack -> SORRY.
    Thx for the great FW...and no back to THIS Topic (Great FW-Bugfinding)
     
  42. Victek

    Victek Network Guru Member

    I understand .. but the most important is that I listen, I go back to my bug finding position.. ;)
     
  43. jsmiddleton4

    jsmiddleton4 Network Guru Member

    " This fix avoids ping storm in the net..."

    Victek's version fixes the ping issue we've been seeing?
     
  44. sandspike

    sandspike LI Guru Member

    My pings have gotten ugly on Shibby 118 (R7000), time for a reboot, can anyone else confirm Victek's firmware pings are looking good?

    Still bad.
     

    Attached Files:

    Last edited: May 28, 2014
  45. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Looking at Victek's now.

    1. Overclocking options, do they work? The values don't seem right for the R7000.
    2. Pings longer than Netgear's stock FW.

    edit: However pages load very snappy and I see no evidence of high pings when surfing the Internet. I'm confused by the ping number seen doing a ping in a cmd window but no apparent impact surfing.

    Wireless clients are staying connected which was an issue with Shibby's and the newest Realtek driver. Victek's "older" more stable driver does not drop wireless clients.

    edit: Speedtest reports much lower pings than cmd ping command. Still not sure why nor what is going on with a FW that pings are impacted negatively. Speed is quite good however.
     

    Attached Files:

    Last edited: May 28, 2014
  46. boghea

    boghea Reformed Router Member

    I get your point of view, but this is the reason I got R7000 because it can do more (dual core, 128 flash and 256 memory). For me, not having Transmission is a deal braker (I don't like to have multiple devices plugged in when one can do the job perfectly well). The combination of transmission and DLNA is perfect. I believe it's a good thing to give people options (if you have transmission is not required to enable it) so the firmware can be used in more scenarios.
    Aria2 is something I am not familiar that's why I referred to Transmission.
     
  47. The Master

    The Master LI Guru Member

    Shibby Confirmed this Problem...will be fixed in 120 or later.. (119 new Version is out)
     
  48. Elfew

    Elfew Addicted to LI Member

    Aria2 is better then transmissions... you can control it remotely (over PC app, mobile app) etc. It is a complete solution. Nice GUI and better functionality. I hope it will be included in future :)
     
    wmz0731 and The Master like this.
  49. boghea

    boghea Reformed Router Member

    I have nothing against Aria2, the main idea was that I would like a download application on the router.
     
  50. shibby20

    shibby20 Network Guru Member

    @Elfew - transmission is a complete solution (client with build-in web gui). Aria2 has only command line interface (CLI) and haven`t build-in webGUI - similiar like rtorrent. If you want GUI then you have to install another package ie webui-aria (similiar like rutorrent for rtorrent). For transmission you can also use PC app, mobile app, it`s not a problem.
     
    Elfew and wmz0731 like this.
  51. boghea

    boghea Reformed Router Member

    I don't know when this would be possible but another feature worth introducing is temperature display for cpu and wireless; I am proposing this because when my R7000 came the heatsink was not connected to the cpu (it was missing the thermo conductor rubber) and the temperature displayed in dd-wrt was 80-81 Celsius; after reading on the forums I took apart the router and fixed this. My point is that temperature readings might explain performance issues for some users and also can be used to keep the device in healthy conditions.
    I would also love to have the led's working (including an option to turn them off depending on time) and the additional button.
    Thanks for making tomatousb available for R7000
     
  52. The Master

    The Master LI Guru Member

    Oh i think this temperature was normal ... so ist not ...outch not good have to check mine...

    if this is not mutch work then please yes add this Funktion...

    Thx
     
  53. sandspike

    sandspike LI Guru Member

    Unfortunately, wireless seems to have further issues in 119. So hopefully 120 will resolve both of these issues.
     
  54. The Master

    The Master LI Guru Member

    In 119 there is a new Version of the WL Driver, ist the Same as in DDWRT "NEW" Version from Kong and the same direct from Netgear. So all suffer from the same Problem.
    Shibby or Victek correct me if i am wrong.
     
  55. jsmiddleton4

    jsmiddleton4 Network Guru Member

    LED's working with Victek's.
     
  56. boghea

    boghea Reformed Router Member

    FYI
    After fixing this the temperature was between 50-58 Celsius under idle/load conditions, so preety good improvement.
     
  57. Edrikk

    Edrikk Network Guru Member

    Running @Victek build 1.3f on R7000, and initial impressions:
    • Only hours in, but in general seems solid as always
    • Issues:
      • Similar to Shibby's build, the clock speed is mis-stated (this has been previously stated, and RMerlin has code to fix as he pointed out here).
      • Similar to Shibby's build, setting the channel width to 80 MHz does not survive a reboot (US as country). After reboot the width is set to 20 Mhz.
    • Comments/Noticings:
      @Victek are these new changes not listed in the change log?
      • Changes in the QoS? I noticed that the Inbound rules are now percentage based (and I'm fairly sure in the previous versions there were floor and ceilings). I only noticed it because my iMacros (automated settings entry) macro failed on this page.
      • PPPoE overhead entry removed? Also noticed for the same reason as above

    General comment... Man, the R7000 takes a LOOOONG time to boot... This is compared to an E3000.... But then again, the WRT54GL boots in a fraction of the time it takes for E3000 to boot as well, soo.....
     
  58. jsmiddleton4

    jsmiddleton4 Network Guru Member

    "the clock speed is mis-stated"

    The Overclocking options are not correct either. Me thinks the parts of the code that deal with CPU speed were bypassed as being a lower priority issue. The current fw appears to grab its defaults from the cpu and moves on. Tweaking the CPU can come in later revisions.

    Just guessing there but I think that is close enough to be accurate.

    However the current Victek version has moved past the "try and and then go back to Netgear's" stage and I'm leaving Victek's installed and will update from here. The previous versions were interesting but not stable enough to draw a line in the sand.

    Victek's current version is stable enough to draw a line in the sand and move on from here.....

    Which is a good thing. From it we can move on to shibby's next version or Victeks, maybe even Toastman's.....

    :)
     
  59. Edrikk

    Edrikk Network Guru Member

    Agree with all the above. Except for "being close enough"... It's not... It's actually doubled (due to dual-core architecture. So it shows as 1998 or so when when it should be 1000).
     
  60. sandspike

    sandspike LI Guru Member

    I can't wait to try victek's build..shibby's build has been great so far....thrilled to have options.

    Sent from my SM-N900V using Tapatalk
     
  61. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Just checked, router and connections are stable, to see if anything new showed up. Mine is now saying
    CPU Clock1595 MHz
    .
     
  62. jsmiddleton4

    jsmiddleton4 Network Guru Member

    What is the actual impact of the wireless signal strength with these ARM based routers? Old school was don't set signal higher than 70 as you'd get noise and heat and little or no improvement. As I recall anyway.....

    What are we looking at now for these settings in terms of effective real world don't create a bunch of extra noise on the signal settings?
     
  63. MrDoh

    MrDoh Networkin' Nut Member

    I'm wondering what a good setting for transmit power is? The default seems to be 42, is that what people use for best results? Or "0" for default? I'll be playing with that some, but I'm just wondering where people are setting the transmit power for the best results?

    Thanks!
     
    Last edited: May 29, 2014
  64. Connor McCaffrey

    Connor McCaffrey Serious Server Member

    on RT-AC66U i set the transmit power to 100 for both radios
     
  65. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Didn't want to but ended up back at Netgear's FW. My CPU speed kept dropping and the router performance did as well.

    We're getting closer and closer but even Victek's is not quite ready for prime time. I'm not being inpatient by the way. Just reporting what my end user experience was.

    We'll get there. I'm glad to wait for stable well performing FW of a Tomato hybrid........
     
  66. sandspike

    sandspike LI Guru Member

    Anyone else seeing those same issues, I am happy with Shibby 118, most of the time, but I was about to switch over to Victek's. Edrikk?
     
  67. hawkmat

    hawkmat Networkin' Nut Member

    Hi jsmiddleton4!
    I have done a great deal of testing regarding the Tomato output power setting. I used a RT-N66U, RT-AC66U, RT-AC68U and a R7000. I used an two different notebooks. One with an Intel AC-7260 and One with a Killer N-1103. An iPhone 5s, iPad Air and several Android phones and tablets. 120 mega bit internet connection, LAN NAS server.
    Findings:
    The setting of 0 (Zero) is the maximum power output under Tomato. Advanced wireless settings at default.
    2.4 GHz/ Channel 6 = The country setting of US and 0 yields maximum output range.
    5 GHz/ Channel 153 = The country setting of Singapore and 0 yields maximum output range.
    These setting are not the best for throughput but signal range.
    I discovered this when I was doing speed tests with my iPhone 5s. I could never seem to get better than 65 to 70 mega bits per second on 5 GHz. I knew the phone could do better with my 120 mega bit internet connection.
    That began my journey to discover what was happening which involved a lot of trial and error.
    I discovered that a Transmit Power power of 50 and US country code on 5GHz gave me the greatest throughput. I'm now getting 85 to 100 mega bits per second. If i change the power setting back to 0 then my speed drops back to 65 to 70 mega bits. I have found this to be the same with all the Android devices too. File transfers from my NAS to the Notebooks are also faster at 50 Transmit Power setting. I left 2.4 GHz at 0 because I wanted max range and the 2.4 GHZ band has difficulty delivering above 70 mega bits anyway.
    What you can take from this is that if you have a internet connection below 70 mega bits then you can just run at maximum output power since the reduction of throughput wont be noticeable. If you have a higher speed connection then it might be worth experimenting with.
     
    Last edited: May 29, 2014
    Iceman_jkh and MrDoh like this.
  68. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Thanks for all the information. The settings have different impact than previous routers/FW. Nice to see how much research you've done.

    For now I'm waiting for another cycle of FW releases. Not only did my CPU speed seem to actually be dropping my wireless connection quality was as well. I was at the default values for the signal strength.

    It is as if the router was busy doing something.

    Edit: My pings were very high as well. Were running in the high 100's to high 200's. With Netgear's FW they run in the teens to low 20's.
     
    Last edited: May 29, 2014
  69. MrDoh

    MrDoh Networkin' Nut Member

    The core routing and wireless functionality of Victek's firmware was working very well for me, and I would have stayed with it, except for one thing. My Verizon Network Extender wasn't able to contact its home base for the first time. Figured that this was most likely because the VPN passthrough wasn't working for some reason, tried rebooting the Extender at least 3 times. The router was rebooted during configuration work, several times.

    Just went back to dd-wrt, and the Network Extender immediately started working properly without rebooting. It is now connected and working properly. Unfortunately, if I don't have the Extender working, phone batteries go down very quickly here, since we don't get enough cell signal without it. Will try again next release.

    Update: While this firmware seems sensitive relative to the Verizon Network Extender VPN passthrough, I've been able to configure the firmware and have it working when I'm done. However, a couple of times I've enabled CTF then rebooted, and VPN passthrough will stop working. Needed a full nvram erase and reconfigure to bring it back.
     
    Last edited: May 30, 2014
  70. Victek

    Victek Network Guru Member

    Thanks @Edrikk,

    My comments:

    ~ CPU clock speed display .. Really not a priority.. it's in TODO but I have bigger craps to solve.
    ~ Have to try changing region settings... didn't realize, thanks.
    ~ Yes, there are changes in QoS in a wip to fix it.
    ~ PPPoE ... I missed... sorry.

    Boot time. Yes, nearly 2 minutes ... every router is a different world... the most important is that is running solid, very solid as difference with the first release... and I did only three releases ;)

    The most important are the added features, OSPF is a hit for a domestic router ... DNSSEC is another step ahead. My POV for tomato is in the network side as one router must be. You have to pay thousands of dollars to get these features only available in a enterprise devices.
     
    MrDoh, Iceman_jkh and Elfew like this.
  71. Elfew

    Elfew Addicted to LI Member

    CPU clock - my devices are not stable after OC, so I dont use it. Reboots or lags. So I dont use it and no problem.

    QoS - I didnt notice changes because I dont use it - so you work on it?
    PPPoE - so no problem, it will be back in the next build

    And I agree with you - new features are a huge step ahead for Tomato - this fw has new opportunities and new group of users (or will have :))
     
  72. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Thanks for all your hard work.

    What's with the pings being so long?
     
  73. Iceman_jkh

    Iceman_jkh Reformed Router Member

    I'm not sure which R7000 fw I'll end up using (Victek, Shibby, Kong, Toastman) but without these guys doing the fantastic work they do (gratis), we'd have no alternatives to the stock (unimpressive) fw.

    I may even swap between their fws to best suit the features I need at any particular time and stability status of the fw.

    With that in mind, I'd like to donate to each of them (even if I only end up using 1 fw) to support their work and to recognise the sentiment that guys like that feel for the community!

    Thanks fellas!

    EDIT: Donated

    Sent from my GT-I9300 using Tapatalk
     
    Last edited: May 30, 2014
  74. rpress

    rpress Connected Client Member

    Wow Tomato for R7000! Thanks to the devs!

    I installed it and it's working great. With a 7260AC card in Linux 3.15 I'm getting 35 MB/s down, which is at least as good as with the stock FW. Pings are mostly around 1.5 ms to 3.7 ms.

    I struggled with Comcast IPv6 support, but I found the error. After setting usual DHCPv6 options simply add:
    Code:
    echo 0 > /proc/sys/net/ipv6/conf/`nvram get wan_iface`/forwarding
    to firewall script and IPv6 is working perfect.
     
  75. Victek

    Victek Network Guru Member

    What version do you use, shibby or mine?
     
  76. MrDoh

    MrDoh Networkin' Nut Member

    Also, can you please say what the filesystem path of the firewall script that you're referring to is?

    Thanks.
     
  77. rpress

    rpress Connected Client Member

    Sorry I forgot to say. I use yours, v1.3f.

    The firewall script is located in the web GUI under Administration->Scripts->Firewall.
     
    Victek and MrDoh like this.
  78. Victek

    Victek Network Guru Member

    Perfect, patch for next version when Comcast option in firewall will be enabled. Thanks!
     
  79. rpress

    rpress Connected Client Member

    Sure! Correct me if I'm wrong but I don't think this fix is specific for Comcast. As far as I can tell RA will not work with IPv6 forwarding turned on. So I think this option should be tied to the "Accept RA from WAN" check box in IPv6 Configuration.
     
  80. Victek

    Victek Network Guru Member

    Then I have a problem with Australia ISP's ... you're right, have to see how I can sort it...
     
  81. MrDoh

    MrDoh Networkin' Nut Member

    Wow, I'm impressed. Finally got Victek's firmware configured with my Verizon Network Extender working, and also Comcast IPv6 working, wireless-ac, etc.. Very nice, many thanks.

    Carefully saved settings files so that I can reproduce these settings if I need to for some reason. Like I do something stupid and break something.

    Does restoring saved settings work? I'm hoping so *smile*.

    Thanks so much!
     
    rpress likes this.
  82. Edrikk

    Edrikk Network Guru Member

    Only issue I have based on the functionality I use is the same in Shibby's: 80MHz channel doesn't keep after a reboot.

    Try it for yourself. What exactly do you have to lose?
     
  83. Edrikk

    Edrikk Network Guru Member

    Vic has given very clear directions earlier in this thread (in the 1.3f change log post)
     
  84. rpress

    rpress Connected Client Member

  85. jsmiddleton4

    jsmiddleton4 Network Guru Member

    Glad to see folks getting Victek's working. How are you pings?
     
  86. Victek

    Victek Network Guru Member

  87. rpress

    rpress Connected Client Member

    Great, I will try it. I have the R7000.
     
  88. Victek

    Victek Network Guru Member

    @R7000 and @rpress you have PM with the link for R7000 test version. Changelog:

    _ libzo.so.1 error fixed in Web Server.
    _ accept_ra=2 implemented, do at cli level and if it works then I'll include switch in IPv6 section.
     
    Elfew and dc361 like this.
  89. rpress

    rpress Connected Client Member

    Yes it works now without anything in firewall scripts. Somehow accept_ra is already 2, must be set by something else. So now Comcast IPv6 is working with 1.3f1 with no hacks. Thanks!
     
  90. vap23

    vap23 Network Newbie Member

    Can someone please point me to the proper procedure for upgrading to victek's tomato firmware from DD-WRT Kong firmware on the R7000. Thanks
     
  91. Imperial

    Imperial Reformed Router Member

    safe to upgrade to Viktek's R7000 build right from DDWRT?
     
    Last edited: May 30, 2014
  92. vap23

    vap23 Network Newbie Member

    Thank you Sir!
     
  93. Imperial

    Imperial Reformed Router Member

    LOL we posted the same subject at the same time! :)
     
  94. Imperial

    Imperial Reformed Router Member

    Hold on I was checking to see if those procedures would work- I dont know if they can be used from ddwrt
     
  95. vap23

    vap23 Network Newbie Member

    Thats funny. I'll wait for confirmation
     
  96. Victek

    Victek Network Guru Member

    Perfect, question, so shibby version was working with Comcast IPv6 without any hack?
     
  97. teh_g

    teh_g Networkin' Nut Member

    I was on shibbys version for a bit and IPv6 was not working for me with Comcast
     
  98. Victek

    Victek Network Guru Member

    Do you like to test the fix applied for IPv6 in your router? model? @rpress feedback is positive.
     
  99. jsmiddleton4

    jsmiddleton4 Network Guru Member

    One of the things the Netgear FW does better on the R7000 than either Shibby's or Victek's FW is releasing and renewing static IP addresses to clients. Let's say a client gets 192.168.1.200 given by DHCP. I still want to use DHCP but assign static dhcp, or reserved, IP addresses within a certain range. I'll assign that client 192.168.1.30. Netgear's refreshes that client IP from the .200 one to the newly assigned .30 one quickly. With the Tomato variants I often have to refresh the client to get it to grab the new static dhcp reserved IP, sometimes I have to reboot the router and refresh the client. Even then sometimes, not always, the old .200 IP address will still be displayed in the Device screen.

    Not in anyway a big deal. Just was making note of the different experience. Whatever Netgear is doing to manage IP's in this context is different than Tomato. As a result Netgear's is easier and quicker.

    Where as Tomato is easier to do the management and assignment of clients. Netgear's is quicker to redo the assigned IP.

    Still wanting to know about the ping deal. As I'm looking at my experience with both Shibby and Victek's I'm thinking the longer pings is part of the mix.
     
  100. MrDoh

    MrDoh Networkin' Nut Member

    Couple of things...woke up this morning (yeah! *smile*) and found the Verizon Network Extender offline again. Router was still working, but it looked like the VPN passthrough (or something else the Extender needs to see) had gone away over night.

    So I reset to factory defaults, and restored the settings file that I had saved with IPv6 and the firewall script setup and working. The Network Extender came back up fine after that, except no IPv6 or firewall script. So they apparently weren't saved when I saved my settings.

    So I set up IPv6, and all good now. I'll give it another shot because the IPv6 is working so well *smile*, but not a good sign for stability. And this is Comcast IPv6 that's working well, impressive. Better than the Netgear stock firmware. Kong's dd-wrt doesn't have IPv6 at all at this point, I've spent a lot of time working on that one, no consistent results. I can get it working on dd-wrt, but then reboot, and poof, gone.

    About pings, when I set it up yesterday evening, the pings to the router were all over the place. So I enabled CTF and rebooted and the pings were still all over the place. Went back to factory defaults, reconfigured, and got lucky. The pings to my router were "<1ms" without touching CTF. And still are this morning after restoring the settings file mentioned above. Pings on the internet speedtests are correspondingly low, comparable to dd-wrt firmware and the stock Netgear. Don't know why this works right sometimes and not others, same as with the Network Extender. But when it works, it works well and makes me happy.

    Hopefully the causes of the varied results here can be taken care of, and the firmware can be made to work consistently well. Thanks for all the work on this firmware to date, when it works right it works really well.

    Late-breaking news: While my 2.4GHz. wireless setup was restored when settings were restored, 5GHz. did not restore the SSID, channel number or Control Sideband. Also, none of my LAN settings (dhcp pool address range, static IP's) were restored. Looks like this one needs some work, sorry.
     
    Last edited: May 30, 2014

Share This Page