Posted: Mon Apr 23, 2018 5:45 Post subject: WRT320N to E2000
Hi
I have successfully flashed my WRT320N router to DD-WRT. It is ' DD-WRT v24-sp2 mini (c) 2010 NewMedia-NET GmbH Release: 08/12/10 (SVN revision: 14929)'. I want to move it to an E2000 using the latest release that is working. I have been reading the Wiki and I have different best approaches.
I see that k3 is mentioned and I would like to use it if it is not goping to brick my unit. What is the best strategy for me to move forward.
Robert
Posted: Mon Apr 23, 2018 7:20 Post subject: Re: WRT320N to E2000
robertdaleweir wrote:
Hi
I have successfully flashed my WRT320N router to DD-WRT. It is ' DD-WRT v24-sp2 mini (c) 2010 NewMedia-NET GmbH Release: 08/12/10 (SVN revision: 14929)'. I want to move it to an E2000 using the latest release that is working. I have been reading the Wiki and I have different best approaches.
I see that k3 is mentioned and I would like to use it if it is not goping to brick my unit. What is the best strategy for me to move forward.
Robert
Thank you. I do see that there are several successful upgrades on the Forum using entirely different Binaries. What I was attempting to establish is "I see that k3 is mentioned and I would like to use it if it is not going to brick my unit." I was wondering if there is anyone who has successfully used any of the k3 binaries and successfully Flashed to my unit. Appreciate your response.
Posted: Mon Apr 23, 2018 22:06 Post subject: Re: WRT320N to E2000
robertdaleweir wrote:
I do see that there are several successful upgrades on the Forum using entirely different Binaries. What I was attempting to establish is "I see that k3 is mentioned and I would like to use it if it is not going to brick my unit." I was wondering if there is anyone who has successfully used any of the k3 binaries
There are lots of reports of E2000 users; just search the new build threads. From the wiki, this is the important part for you:
E2000 wiki wrote:
For newer builds, you must flash a trailed mini build first, then use nv60k.bin files thereafter
If you're not aware, trailed means the E2000 named files; and there aren't nv60k k3x builds, so you must used trailed builds for them.
There are surely a thousand threads about it, but based on the wiki, from your current 14929, flash k2.6 21061 mini E2000 first, then use whatever k3x trailed (E2000.bin) you find from your research. Reset and manually set up. I'd suggest 34311 or 35531; newer build have wireless issues. And both threads mention running the E2000, like this. _________________ #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
Thank you very much jwh7. Exactly what I was looking for. I will follow your advice and get back here and post my results. Right now I am having a problem transferring a modified cfe.bin to the /tmp directory on the unit. I have tried 'winSCP' from my Win7 machine and Filezilla from my Linux unit and I get the same error " Error: The first key-exchange algorithm supported by the server is diffie-hellman-group1-sha1, which is no longer secure. Aborting connection.
Error: Could not connect to server ". I realize that it is a 'key-exchange' issue as the router keys are outdated (for security reasons). What can I do to copy my revised cfe.bin file onto the Router. I don't know how to use 'ftp' to get it over but this denial for a 'keys' problem has me stumped.
Many thanks again...
Right now I am having a problem transferring a modified cfe.bin to the /tmp directory on the unit. I have tried 'winSCP' from my Win7 machine and Filezilla from my Linux unit and I get the same error
You need to enable SSH in DD-WRT to use WinSCP. _________________ #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
I actually had SSH running on the router, sorry I should have mentioned it. I think the issue must be the age of the SSH keys which renders the transfer un-doable. I am not sure how best to get Filezilla to give up its rigid, but safer, requirement to use newer keys (sha256 or whatever) or how to get newer keys on the WRT320N. The "diffie-hellman-group1-sha1" reference is what I believe the issue is. Thanks...
