Posted: Sun May 03, 2020 16:40 Post subject: Question about using dd-wrt on EA6500v2
Hello guys,
I am new to this forum, I have wanted to start playing with router´s os for a while, but never had to, because always solve things with a Mikrotik Router that have inside of my network and Linksys as border router.
Today I read that is possible to run some linux command and really love to know my real time bandwidth usage, and that really call my attention. I have a EA6500 v2 but started testing (today) with an old E900 and everything work perfect.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sun May 03, 2020 18:19 Post subject:
It is so awesome to find out about arbitrary executive decision wiki edits. The linked article in the OP is the original EA6500v2 install guide. And we have not answered the questions that the OP had yet. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I already read the first link, and the second is related with EA6700, and I do have EA6500 the one I saw that has some problems with the NVRAM with DD-wrt, and regarding a comment on the post quoted, Advanced Tomato appears to do not have that issue.
Sorry for asking probably silly questions, but i am afraid of briking my main gateway router cause i already saw some weird responses on the E900 where i start testing.
Joined: 18 Mar 2014 Posts: 12838 Location: Netherlands
Posted: Wed May 06, 2020 19:07 Post subject:
The EA6700 and EA6500v2 are identical.
It has nothing to do with EA series linksys.
The EA6500, EA6700 and EA6900 all suffer from the 32k nvram problem.
I cannot comment on Tomato but I doubt they solved this.
The way to mitigate that is described in the instructions.
The only real way is using an alternate CFE like I have done for my EA6900, see my signature at the bottom of this page but necessary it is not.
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Wed May 06, 2020 19:17 Post subject:
You can always also check FreshTomato, which now has advanced themes that are pretty sharp. Wondering if the EA6500 can stand using the XWRT-Vortex CFE without issue, I don't recall of the top of my head if that is one of the ones that doesn't play nice with DD-WRT if you use the custom CFE.
It is so awesome to find out about arbitrary executive decision wiki edits.
I presume that is referring to me. Ya, after my cleanup of the R6400v1, R6400v2 / R6700v3 wiki pages a couple weeks ago, I starting cleaning up the EA6xx0 stuff but it became a huge headache. Then work got busy, and then house/yard spring stuff also started...then I forgot about it. :-/
Anyway, I've spent the past couple hours sorting it all out. The 'EA6300V1' points to the EA6400 (since it is one), and the EA6300 wiki now covers the true 'EA6300' single-core variant and all the other BCM47081A0 models that use EA6350 firmware. EA6{5,7}00 stuff is in a table now, to show the links and forum threads. \o/
I still plan to update some of the generic thread links to post-specific ones, but I think this is a big improvement. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Wed May 06, 2020 22:28 Post subject:
I may ping you after I clean up that EA6350 mess since I don't know if the link will transfer. The V1 and V2 are all jumbled into one mess of a thread. But anyway, thanks for the follow-up _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
The EA6500, EA6700 and EA6900 all suffer from the 32k nvram problem.
I cannot comment on Tomato but I doubt they solved this.
The way to mitigate that is described in the instructions.
The only real way is using an alternate CFE like I have done for my EA6900, see my signature at the bottom of this page but necessary it is not.
The instructions seems pretty straightforward.
But I do not have this router so I can only point you to the instructions.
Oh man, i am sorry about my ignorance, did not know that both models was also the same. I took a look into the post, and they refers that stock version shuould be 1.40, and like him is running 1.41 on mine, should i download 1.40 for 6700 with out any issue? (for 6500v2 the only option for downloading is 1.41)
I am really not encoraged on using advanced tomato cause as far as i saw NVRAM needs to be written, and that cause a non reverse point to standart. And saw that dd has more features.
Thanks guys, if you happen to have any other tip, please let me know. I am just experirnced with devices with direct access to bios and save my potatoes if its necessary.
The EA6500, EA6700 and EA6900 all suffer from the 32k nvram problem.
I cannot comment on Tomato but I doubt they solved this.
The way to mitigate that is described in the instructions.
The only real way is using an alternate CFE like I have done for my EA6900, see my signature at the bottom of this page but necessary it is not.
The instructions seems pretty straightforward.
But I do not have this router so I can only point you to the instructions.
Hi EGC,
Thanks for your initial Light up. I kindly believe that tomato has solved the NVRAM problem, because one of the common steps on the tomato flashing installation is to replace the NVRAM and they warn that there are no way back to custom.
I installed Tomato Shibby into the EA6500v2 and everything is working fine (started with dd-wrt and then changed), I was about to move it to production but saw that the CPU values are rounding 87ºC. are those normal values? Sorry if my question is very silly, but i did not have the chance to test it with factory, and saw that happen often on some installations.
I am thinking on getting an external small USB fan (in deed: Ac Infinity Multifan S1) to glue it into the bottom to force the heat out and take energy from another device.
Joined: 19 May 2017 Posts: 20 Location: TN<>MI, US
Posted: Mon Jul 11, 2022 12:45 Post subject:
Forum activity on this model has really dropped off; this is the latest thread I find!
For any bewildered who stumble upon this, the fix procedure remains the same; do the new CFE (my posts here and following go a little more in depth, that original support thread now locked) and upgrade.
Gave this router to my FIL, who used it for a year then changed ISPs. Just retrieved it from a drawer in his basement, updated to latest BS build (sad to read kong no longer active), and now works better than new. Fixin' to give back to FIL for return to original ISP. Router is rock solid.
In retrospect, I would initialize in the CFE the rc_startup variable with the key command
Code:
for line in $(nvram show | grep =$ ); do var=${line%*=}; nvram unset $var; done
since the router won't ever run (or even flash) current builds reliably without it.
What's old is new. _________________ My old self (phonetics-R-fun)
The .rc_startup script is the startup script that is stored in nvram, not the CFE bootloader. Administration -> Commands -> Save Startup. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
The .rc_startup script is the startup script that is stored in nvram, not the CFE bootloader
I think he intended to have it stored in the CFE. So when an a nvram reset occurs the CFE will populate nvram (and set "rc_startup=" where it will eventually get transferred to the file .rc_startup).
I have not looked thru the code to see if the dd-wrt will do something to the nvram variable "rc_startup=". Ie, set to NUL/Null/empty string or basically otherwise overwrite the CFE reset values.