Guide: Flash Linksys EA6300v1, EA6400, EA6500v2, EA6700, EA6900v1.0/1.1 with Tomato

Discussion in 'Tomato Firmware' started by monoton, Nov 15, 2017.

  1. monoton

    monoton Serious Server Member

    How to flash Linksys EA6300v1, EA6400, EA6500v2, EA6700, EA6900v1.0/1.1 with Tomato.
    The EA6300v1 uses the same firmware as EA6400 since the routers are exactly the same.

    WARNING:
    If anything goes wrong this can brick your router and I will not be held responsible if that happens. You're doing this at your own risk.


    For these router a different CFE needs to be flashed otherwise only 32k of NVRAM can be used and that is not enough but for the most basic setup.

    This means that you will not be able to revert back to Linksys stock firmware after the CFE flash. Other 3rd party firmwares can however be flashed.

    Since the CFE has to be changed for this router there are some Pros and cons when this is done.

    Pros:
    Can install 3rd party firmwares (without the 32k NVRAM limit)
    Can enter recovery mode (Hold the red "reset" button on the back of the router and power up the router, release it after about 15-20 seconds)
    Navigate to 192.168.1.1 and the ”recovery web interface” should come up.

    Cons:
    Can no longer flash back to Linksys stock firmware (not really sure if this is a con since the stock Linksys firmware is nearly useless)

    Download for EA6300v1 & EA6400: https://my.pcloud.com/publink/show?code=kZNb807Z04GYcuqwyxY10A7Ypsd8YHj35b57/
    The archive contains:
    linksys_ea6400_ddwrt.bin
    linksys_ea6400_cfe.bin
    WinSCP-5.9.6-Portable
    CFEEdit.exe
    putty.exe
    Tftp2.exe

    Download for EA6500v2: https://my.pcloud.com/publink/show?code=kZUbB87Zm3YFpS5jm17pxlLl49R2b5lXvYQV
    The archive contains:
    linksys_ea6500_ddwrt.bin
    linksys_ea6500_cfe.bin
    WinSCP-5.9.6-Portable
    CFEEdit.exe
    putty.exe
    Tftp2.exe

    Download for EA6700: https://my.pcloud.com/publink/show?code=kZ8beL7Zh4Wmg5YsaGfhw7Lb5Qn2kuR4sA87/
    The archive contains:
    linksys_ea6700_ddwrt.bin
    linksys_ea6700_cfe.bin
    WinSCP-5.9.6-Portable
    CFEEdit.exe
    putty.exe
    Tftp2.exe

    Download for EA6900v1.0 & EA6900v1.1: https://my.pcloud.com/publink/show?code=kZ5Erm7ZffTAthNzl1Hnv31K35kW7uw3aK4V
    The archive contains:
    linksys_ea6900_ddwrt.bin
    linksys_ea6900_cfe.bin
    WinSCP-5.9.6-Portable
    CFEEdit.exe
    putty.exe
    Tftp2.exe

    Also remember to download Tomato firmware of your choice.

    1.
    Reset the router (press and hold the red reset button until the power indicator flashes)

    2.
    Connect the PC to LAN port1 on the router.

    Give the PC a static IP:
    IP address: 192.168.1.20
    Subnet mask: 255.255.255.0
    Default gateway: 192.168.1.1
    DNS: 192.168.1.1

    Reconnect to make the settings take effect.

    Ping the router "ping -t 192.168.1.1" (ttl=64 usually means that the router is ready)

    3.
    Open a web browser and navigate to 192.168.1.1.

    Skip the basic setup (check the "skip" box) and proceed to log in using "admin" as password.

    Navigate to Connectivity → Basic and flash "linksys_ea6xxx_ddwrt.bin".

    If there’s an error saying the file is invalid this means the stock Linksys firmware is too new and can only flash firmwares signed by Linksys.

    In this case do the following: Go to Troubleshooting → Diagnostics and click on "restore previous firmware", if it asks for a file then flash "linksys_ea6xxx_ddwrt.bin".

    If it doesn’t ask for a file the flash will have to be done with tftp:

    (For Windows)
    Disconnect router
    Run tftp2.exe
    Server: 192.168.1.1
    Password: blank (nothing)
    File: browse to the dd-wrt file
    Retry: 99 times
    Connect the router
    Immediately when ttl=100 appears in the ping window, press Upgrade to upload the firmware. This has to be excecuted quite fast so that the firmware have time to be uploaded to the router before ttl=64 appears.

    If ping times out or host unreachable before firmware is flashed, ttl=100 doesn't show up, only ttl=64 or something else, just reconnect power to the router and let tftp keep trying. Also try a few resets once in a while.

    Whatever you do, do not reconnect power or reset the router if the firmware has started uploading.

    Most times it works on the first go, but this can take a bunch of retries (It appears the number of ttl=100 responses is not the same on every powercycle and sometimes there are no ttl=100 response at all, very strange)

    Give the router a few minutes untill ttl=64 appears in the Ping window.

    If ttl=64 does not appear, make sure that atleast five minutes has passed since the upload and reconnect the power to the router

    Go to 192.168.1.1 again and DD-WRT should be there.
    If not:
    Navigate to Troubleshooting → Diagnostics and restore previous firmware.

    DD-WRT should now boot.

    (For the Linuxes)
    The procedure is the same as for Windows but instead of the tftp2 application, command line is used.

    Install tftp from the distro repo if not already installed.

    Run tftp from the folder where "linksys_ea6xxx_ddwrt.bin" is located.

    $ tftp
    tftp> connect
    (to) 192.168.1.1
    tftp> binary
    tftp> rexmt 1
    tftp> timeout 180
    Reconnect the power to the router.

    When ttl=100 appears in the ping window:
    tftp> put linksys_ea6xxx_ddwrt.bin

    Sent 22765568 bytes in 76.5 seconds
    tftp> quit

    4.
    Once the flash has completed (this takes a couple of minutes) navigate to 192.168.1.1.

    Set username/password to admin/admin.

    Navigate to the services tab and enable SSHd. Click Save at the bottom, then Apply Settings.

    5.
    Open "linksys_ea6xxx_cfe.bin" with "CFEEdit.exe" and fill in:
    MAC Address (found on the bottom of the router)
    WPS Password (found on the bottom of the router)

    Go over to the Advanced Mode tab and change 0:macaddr and 1:macaddr to the following:
    0:macaddr (same as MAC Address +2)
    1:macaddr (same as MAC Address +4)

    The HEX sequence from 00H to FFH:
    00,01,02,03,04,05,06,07,08,09,0A,0B,0C,0D,0E,0F
    10,11,12,13,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F
    20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F
    30,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,3F
    40,41,42,43,44,45,46,47,48,49,4A,4B,4C,4D,4E,4F
    50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5D,5E,5F
    60,61,62,63,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F
    70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F
    80,81,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F
    90,91,92,93,94,95,96,97,98,99,9A,9B,9C,9D,9E,9F
    A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,AA,AB,AC,AD,AE,AF
    B0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF
    C0,C1,C2,C3,C4,C5,C6,C7,C8,C9,CA,CB,CC,CD,CE,CF
    D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF
    E0,E1,E2,E3,E4,E5,E6,E7,E8,E9,EA,EB,EC,ED,EE,EF
    F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,FA,FB,FC,FD,FE,FF


    So if the MAC Address (found on the bottom of the router) is:
    3B:00:8F:39:F9:56
    then 0:macaddr (same as MAC Address +2) would be:
    3B:00:8F:39:F9:58

    If the MAC Address (found on the bottom of the router) is:
    3B:00:8F:39:F9:CF
    then 0:macaddr (same as MAC Address +2) would be:
    3B:00:8F:39:F9.D1

    For EA6300v1 and EA6400 also change clkfreq to:
    clkfreq=800,533

    Save as "new6xxxcfe.bin"

    6.
    Run WinSCP.exe
    File protocol: SFTP
    Host name: 192.168.1.1
    Port number: 22
    Username/Password: root/admin
    and Login

    Upload the newly created CFE file "new6xxxcfe.bin" to the router.
    This is done by dragging the file from the left side to the right (make sure the right side is in the /tmp/root directory)

    Close WinSCP

    7.
    Run Putty.exe
    Host name: 192.168.1.1
    Port: 22
    Connection type: SSH
    and Open
    login as: root
    password: admin

    To flash the CFE use the following commands:
    mtd unlock /dev/mtd0
    mtd write –f /tmp/root/new6xxxcfe.bin /dev/mtd0

    If that doesn't work try:
    mtd unlock /dev/mtd0
    mtd –f write /tmp/root/new6xxxcfe.bin /dev/mtd0
    Close Putty

    8.
    Now that the new CFE is flashed the "recovery web interface" can be used to flash new firmwares.
    Hold the red "reset" button on the back of the router and power up the router, release it after about 15-20 seconds.

    Navigate to 192.168.1.1 and the "recovery web interface" should come up.
    Flash Tomato Firmware (this can take up to five minutes, check the ping for ttl=64 to see if it’s done.)

    When the flash is done it's time to reset NVRAM (hold the WPS button while powering on the router, hold it until the Linksys logo starts to flash or 15-20 seconds)

    Go to 192.168.1.1 and do a reset from within Tomato. Administration → Configuration → Erase all data in NVRAM memory (thorough).

    Reboot router.
     
    Last edited: May 21, 2018
  2. boooya

    boooya Network Newbie Member

    Thank you very much monoton, this worked great!

    I guess there is some kind of checksum calculated when using "CFEEdit.exe" to save "new6400cfe.bin" otherwise it would have been nice not having to fire up a Windows VM :)

    Firefox (57.0.1, 64-bit) failed to upload the tomato firmware on the ”recovery web interface”, so I had to redo the process (reset to the DD-WRT-step), luckily the second try with Safari worked.
     
  3. monoton

    monoton Serious Server Member

    I used the windows tools in WINE under Linux.
    I thought about writing the guide for Terminal use for the Linuxes at first but ended up doing it this way instead since Windows have about 90% of the desktop market.
     
  4. iv7777

    iv7777 Reformed Router Member

    Thanks for the nice guide. Look like there can be one tiny optimation added to the process if someone likes a faster bootup:

    At step 6, before saving as "new6400cfe.bin", go to Advanced Mode and change

    clkfreq=800,333

    to:

    clkfreq=800,533

    Save as "new6400cfe.bin" and follow the rest steps.

    By doing this, the RAM clock will be set to 533MHz instead of 333MHZ at CFE boot and the boot up time can be cut from 90 down to 60 seconds. For some reason, the CFE doesn't like value 333 at the first boot and reboot again with 533 set as the new value. Setting the value 533 will make it boot only once, thus saving some time. This can be verified by hooking up with a serial cable.

    Hope this will help
     
  5. monoton

    monoton Serious Server Member

    Thanks.
    Didn't know about that one, added it to the guide.
     
  6. lepa71

    lepa71 Networkin' Nut Member

    Do we have to have modified CFE if linksys fw is too old(before it was required a signed fw from linksys)?
     
  7. CHuckNasty

    CHuckNasty New Member Member

    Im Noob, so please forgive me question but on step 3 statement: "If there’s an error saying the file is invalid this means the stock Linksys firmware is too new and can only flash firmwares signed by Linksys."

    Would I need to contact Linksys or am I SOL?


    Router: Linksys EA6900
    Firmware: Ver. 1.1.42 (Build 174772)
     
  8. monoton

    monoton Serious Server Member

    To get around the 32k NVRAM issue the modified CFE is needed, doesn't matter if the firmware is old or new.
     
  9. monoton

    monoton Serious Server Member

    In that case you have to flash by using TFTP wich is also described in step 3.
     
  10. CHuckNasty

    CHuckNasty New Member Member

    oh ok. I will try that out and see what happens.
    Thanks for the response.
     
  11. CHuckNasty

    CHuckNasty New Member Member

    @monoton Also another question, I have had this router for about 3 years, its a EA6900 either way, it currently is running version W_EA6900_1.1.42.174776_prod.img would i need to roll it back to an older verison using the TFTP also?
     
  12. monoton

    monoton Serious Server Member

    No, there's no need to roll back to an earlier version when TFTP is the method to be used.

    imo the TFTP way is actually the easiest.
    ping the router
    $ tftp
    tftp> connect
    (to) 192.168.1.1
    tftp> binary

    Reconnect the power to the router.

    When ttl=100 appears in the ping window:
    tftp> put linksys_ea6xxx_ddwrt.bin

    Sent 22765568 bytes in 76.5 seconds
    tftp> quit

    No need to log into stock firmware.

    If Linksys stock firmware is too recent i.e if there’s an error saying the file is invalid when trying to flash from stock, then the TFTP method is the only way.
     
    CHuckNasty likes this.
  13. CHuckNasty

    CHuckNasty New Member Member

    Hey @monoton I have restarted setup the router directly to my pc via my lan port, Gave the PC a static IP:
    IP address: 192.168.1.20, Subnet mask: 255.255.255.0, Default gateway: 192.168.1.1, DNS: 192.168.1.1 and set everything as followed, and it still says unable to get response form the server when using TFTP? Any suggestions?
     
  14. monoton

    monoton Serious Server Member

    If you can ping the router there shouldn't be any problem.

    Did you open TFTP from the folder where linksys_ea6900_ddwrt.bin is.
    and
    Did you do tftp> put linksys_ea6900_ddwrt.bin immediately when ttl=100 appears in the ping window (this has to be excecuted fast otherwise the firmware do not have time to be uploaded before ttl=64 appears in the ping window.
     
    CHuckNasty likes this.
  15. CHuckNasty

    CHuckNasty New Member Member

    The funny thing is i usually get about 20 ttl=100 pings before the it starts to work then, then it gets to about 65% and then show server cant be reached. I try to do it quickly as soon as i see the ttl=100 but it cant be reached until about 20 pings of the ttl=100, but never has time to finish. can i do something to slow the pings down maybe?
     
  16. monoton

    monoton Serious Server Member

    I've now tried three different routers EA6400, EA6700 and EA6900.

    EA6400 worked fine, several ttl=100 responses and flashed the firmware.

    EA6700 and EA6900 both only had a few ttl=100 responses and TFTP would time out.

    I don't know if this is the same issue you have, but in the end I was able to flash both of them with the following procedure:

    $ tftp
    tftp> connect
    (to) 192.168.1.1
    tftp> binary
    tftp> rexmt 1
    tftp> timeout 180
    tftp> put linksys_ea6900_ddwrt.bin

    This will make TFTP try to upload every second for three minutes.

    Then I had to reconnect the power, reset and "tftp> put linksys_ea6900_ddwrt.bin" in no particular order for several times until the firmware finally uploaded with several ttl=100 responses.

    I probably had to reconnect power/reset 15 times before it worked, but it is definitely doable.

    It's very strange, some of the routers flash the first time, others not so much.
     
    CHuckNasty likes this.
  17. CHuckNasty

    CHuckNasty New Member Member

    Ok. this is my procedure and let me know if i am doing it incorrectly. so when I open the cmd prompt:

    I have the file stored on my downloads forlder(tftp.exe and linksys_ea6900_ddwrt.bin) in the same folder.



    1. Hold the red "reset" button on the back of the router for 30 seconds, and power up the router, release it after about 15-20 seconds.
    2. already have ping on 192.168.1.1 in one cmd prompt window
    3. second cmd prompt window, have tftp ready to go=C:\Users\CEWJR9842\Downloads\Linksys\Tools (not sure if i need to telnet) because this command just opens the small tftp window below:
    upload_2018-5-7_7-51-30.png

    4. enter admin password and upgrade. and fail!(sometimes the blue line starts after about 20 ttl=100 have gone by but then fails mid way.) It does not give the the option to run it via cmd window, unless i'm supposed to telnet to it, am i doing something incorrectly.

    I am not getting to a point when I can run the tftp.exe via cmd prompt, is this a telnet procedure or do I need to also enable tftp in windows 10, if so then i can see why i'm not at least able to do this below:

    $ tftp
    tftp> connect
    (to) 192.168.1.1
    tftp> binary
    tftp> rexmt 1
    tftp> timeout 180
    tftp> put linksys_ea6900_ddwrt.bin


    Again thanks for all your help, it is surely appreciated.
     
  18. monoton

    monoton Serious Server Member

    I just booted up a Windows machine to test and it turns out TFTP on windows doesn't work the same way as in Linux.

    Here's what i did:
    1. Download tftp2.exe http://www.3iii.dk/linux/dd-wrt/tftp2.exe
    2. Disconnect all routers
    3. ping -t 192.168.1.1
    4. Run tftp2.exe
    Server: 192.168.1.1
    Password: blank (nothing)
    File: browse to the dd-wrt file
    Retry: 99 times
    Press Upgrade and let it keep trying.
    5. Connect the router
    Check the ping window and tftp2. If ping times out or host unreachable before firmware is flashed, ttl=100 doesn't show up, only ttl=64 or something else, just reconnect power to the router and let tftp keep trying. Also try a few resets once in a while.
    I had success when tftp2 was on retry 24.

    Whatever you do, do not reconnect power or reset the router if the firmware has started uploading.
     
    CHuckNasty likes this.
  19. CHuckNasty

    CHuckNasty New Member Member

    Cool. I will try this as soon as I get home from work and update you.
     
  20. OskySal

    OskySal New Member Member

    Hey @CHuckNasty, if you use the linksys upgrade tool, leave password blank (at point 4 in your procedure). That's why it fails.
     
  21. CHuckNasty

    CHuckNasty New Member Member


    My bad, I should have been more specific, I enter the password as 'admin', but was using the screen shot to show monoton what comes up since i was using windows 10 and not linux to run the tftp.exe.
     
  22. CHuckNasty

    CHuckNasty New Member Member


    SO @monoton i tried the method for like 4 hours last night, and still it would not finish, it would start the upgrade, but then when i noticed the linksys light it would double flash at some point likes after it showed 'flashing upgrade' and the blue line would start and then I would see the double flash on the linksys light on the front of the router, light it was resetting it self because it was blocking it from allowing the firmware to be upgraded. I should have videoed the lights, it was very strange. I mean literally every time the blue line went across, the router would double blink like it reset it self on purpose before the firmware could be finished flashing, I was thinking this was some measure linksys put in to disallow custom firmware flashes. I tried the 99 retries for over four hours. Maybe i'm just SOL with this router. Does this router do management mode?
     
  23. monoton

    monoton Serious Server Member

    Damn, sorry but I'm out of ideas here.
     
    CHuckNasty likes this.
  24. CHuckNasty

    CHuckNasty New Member Member

    @monoton hey no problem, you win some you lose some! I just want to thanks for the help you did provide!
     
  25. JCORNWELL23

    JCORNWELL23 New Member Member

    what is +2??

    Mac addresses confuse me
     
  26. pomidor1

    pomidor1 Networkin' Nut Member

    MAC is number in the hexadecimal code, you must use, for example, a converter and add a digit to +2
     
  27. monoton

    monoton Serious Server Member

    Not sure I can explain it any better than the guide.

    The guide have the HEX sequence from 00H to FFH and two examples.

    If your MAC Address ends in 17, then +1 will be 18, +2 will be 19, +3 will be 1A, +4 will be 1B.
     
  28. JCORNWELL23

    JCORNWELL23 New Member Member


    I got it man. I apologize for not telling you sooner. I actually thought I did not send this message. Of course I attempted to figure it out again and maybe see if there was something else i could do while waiting whch was when I saw your chart. Thank you very much. Now I am trying to get tomato onto it
     
  29. JCORNWELL23

    JCORNWELL23 New Member Member

    @monoton I am successful with my upgrade to the tomato firmware. I keep having the issue where I set up the channels (2.4 & 5). It does not have a change password option in this area. I configure the settings which i am mostly concerned about security for now. I save, it refreshes, then I cannot get back in unless i connect via ethernet or I reset it. Is there a default password besides admin?
     
  30. lepa71

    lepa71 Networkin' Nut Member

    Which tomato would you recommend to run on EA6400? Thanks
     
  31. monoton

    monoton Serious Server Member

    Shouldn't be any issues with this. I assume this is under Basic -> Network.

    Security: WPA2 Personal
    Encryption: AES
    Shared Key: Password for this SSID

    or do you mean you can connect to the wireless SSID with the shared key, but not login to the router at 192.168.1.1 with admin password

    or is this some other issue and I have misunderstood completely
     
  32. monoton

    monoton Serious Server Member

  33. kartel

    kartel New Member Member

    Thanks. I ran this on my EA6700 today and it worked great. it holds Fresh Tomato's setting fine now.
     
  34. JCORNWELL23

    JCORNWELL23 New Member Member

    @monoton my apologies for my lack of response. i later flashed merlin in hopes that it would be less involved or easier for me. It has worked for me so far, but I would not have understood most of it had I not done all the research that I had done with tomato and ddwrt. So, when I get bored of merlin, I will try tomato again. Even better if I somehow stumble upon another router to tinker with. Thank you for all the information that you have available.
     
  35. Aftershock90

    Aftershock90 New Member Member

    So I'm having trouble with the 8th step.
    When I try to upload the FreshTomato firmware to the recovery web interface, it seems to work for a couple minutes but then the address changes to 192.168.1.1/f2.htm and it says connection timed out. Router seems toast then so I just reflash DD-WRT, nothing unrecoverable so far thankfully.
    Reading the 1st reply by boooya thought it was a browser issue (running FFox 61.0.1 x64) but tried with latest Chromium and had the same result.
    Any Idea as to what's happening? All the previous steps worked fine.

    Trying on the EA6400
     
    Last edited: Jul 26, 2018
  36. lepa71

    lepa71 Networkin' Nut Member

  37. monoton

    monoton Serious Server Member

    Don't know, I've never had this happen to me.
    Maybe try to upload the firmware with TFTP after booting to recovery mode.
     
  38. forall forall2

    forall forall2 New Member Member

    hi
    i have bricked ea6300v1 which i already successed to flash dd-wrt in past and i tried to revert to stock and from there whatever i'm trying , (and i followed this guide too) nothing helps to bring the httpinterface of the router back

    the only thing i success to do is tftp flash as i see ping replies from 192 168 1 1 and it flashes the fiirmware but after that , nothing, i see the green led blinking and then stay constantly but no httpinterface interface,
    tried to flash the FW_EA6300_1_1.40_176337_prod which is the very oldest firmware available in linksys website for the ea6300v1

    flashed also the ddwrt with cfe and without cfe according to this guide.

    tried to flash edited cfe according to the guide via tftp, it flashes successfully but nothing, no dhcp no httpinterface (i set static ip address in my nic ofcourse)

    router is connected on port 1

    the only thing i can do is tftp to the modem on power and see the pings


    any ideas?
     
  39. Anmage

    Anmage New Member Member

    Hi!

    What about the Linksys EA6900v2?
    I have one of this device, and I would like to use tomato firmware...
     
  40. Yaron Keren

    Yaron Keren New Member Member

    EA6300v1, guide worked perfectly until step 8, could not get the FreshTomato firmware to install neither through web UI nor through CFE. Firmware reverted to the DD-WRT installed in the guide.
    Did get latest DD-WRT installed using web UI.
    Thanks!
     
  41. monoton

    monoton Serious Server Member

    Did you reset NVRAM (hold the WPS button while powering on the router, hold it until the Linksys logo starts to flash or 15-20 seconds) when flash was done? if so I have no idea why dd-wrt comes back.
     
  42. monoton

    monoton Serious Server Member

    I don't know about EA6900v2, couldn't find any info if it was different from 1.0 and 1.1
     
  43. Yaron Keren

    Yaron Keren New Member Member

    I followed the steps carefully so guess I did, can't really recall now.
    Thanks again for making this great guide available!
     
  44. Adriel

    Adriel Network Newbie Member

    Is there a way to verify that the 32k NVRAM limit is gone after doing this?
    I've done it and didn't have any errors, but not sure if it worked or not.
     
  45. audit13

    audit13 New Member Member

    Created an account to say "Thank you!" for the excellent guide.

    I decided to take a chance and flash DD-WRT on a used ea6400 I purchased on Thursday. I wasn't too concerned about bricking the router since I didn't pay much for it. After a few tries, I got the latest Brain Slayer beta DD-WRT installed with PIA as a VPN client.
     
  46. monoton

    monoton Serious Server Member

    If you can access the "recovery web interface" the CFE was successfully flashed, it's not available with the stock CFE.
    If the 32k NVRAM limit were still there you probably would have noticed it by now, missing wireless band or setttings resetting itself.
    The most basic setup would perhaps be below 32k and you would not have noticed.
     
    Adriel likes this.
  47. Canopus

    Canopus New Member Member

    It looks like Linksys EA6400 5GHz radio does not work properly (at least two recent versions of FreshTomato). I did not test 2GHz.
    Router drops connection pretty often - character time 10 min.
    I went back to DD-WRT (version of 13 May 2018) and problems have gone.
    Anybody else has such problem?
     
  48. txnative

    txnative Networkin' Nut Member

    You should've posted some of your wifi settings to the Freshtomato-arm forum instead of here, someone could've assisted you.
     
  49. gustavo

    gustavo New Member Member

    thank you !! for this tutorial , it works perfect on ea6700 , once i have the first firmware in , in case i want to load other firmware , can i do that from the firmware upgrade option ( for ex from ddwrt firmware upgrade) , or should i perform a reset and then upload using the minicab interface ? ,
     
  50. monoton

    monoton Serious Server Member

    I have four EA6400 up and running with freshtomato 2018.3, and have no problems with either of the bands.
    Have you flashed the CFE and if so did you set:
    0:macaddr (same as MAC Address +2)
    1:macaddr (same as MAC Address +4)
     
  51. monoton

    monoton Serious Server Member

    Going from one firmware to another (dd-wrt to tomato, koolshare to tomato etc.) you can try from within the firmware and a full reset. If it doesn't work just use the "recovery web interface" and do a full reset.
    If going from lets say freshtomato2018.3 to freshtomato2018.4 just flash from within tomato. A reset might still be needed depending on the changes between the two versions.
     
  52. gustavo

    gustavo New Member Member

    @monoton , ok thank you !, i have now DDWRT v24-sp2 , dated 02/2014 , on other older router i have 3.0 installed , how can i found if this fw (v 24) is the latest version for my device link sys Ea6700 ?, i looked hundred of pages with no luck , any help appreciated .
    im trying to stick with ddwrt, as it seams ( just by researching ) that it may be recommend for wifi bridges over tomato , thanks
     
  53. monoton

    monoton Serious Server Member

    Latest FreshTomato here
    Latest DD-WRT here (DD-WRT only do beta realeases nowadays)
    Latest KoolShare forks here
     
  54. audit13

    audit13 New Member Member

    If you are running DD-WRT, look under Status --> Space Usage NVRAM. I believed it shows the used nvram/total available nvram.
     

    Attached Files:

  55. Adriel

    Adriel Network Newbie Member

    I'm with freshtomato, but they also show the NVRAM usage, but it doesn't seem to change much from
    "Total / Free NVRAM 64.00 KB / 29.97 KB (46.83%)"

    Which is pretty similar to what it was before.
    Either way, I haven't noticed any issues, so guess it worked :)
     
  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