Hi all, I've been running my 320n converted to e2000 for a number of years now. I've been running DD-WRT v24-sp2 mega Release 8/12/10 SVN revision: 14929. I never really upgraded to a higher version because everything works, and you know what they say - if it ain't broke, don't fix it!
Well now I'm looking for ipv6 support. Does anyone know a good, stable version that I can upgrade to that gives me ipv6 support? I've thought about going towards a Ubiquiti USG, a custom Untangle or PFSense box, but really this little thing works fine on my 50/5 mbps cable connection, and I'd like to see how long I can push it.
I am using k26 30825 mini have also used k3 30880 mega both are working stable. K26 is somewhat faster. I do not use ipv6 however
I found I can manually enable ipv6 using command line and conf files for radvd. However I'm still interested in upgrading.
Just to be sure I do it correct (since its been awhile)... I write my router settings down, do the 30-30-30 reset, flash it with something like dd-wrt.v24-30880_NEWD-2_K2.6_mega-nv60k.bin. Then when complete do 30-30-30 reset again, and then finally go through and configure all of my settings.
I don't need to do anything else to make the router still think its e2000.
Ok no matter what it kept saying firmware upgrade failed in the browser. I had to update to a specific build first, then after that was sucessful I was able to upgrade to mega-nv60k.
Process was as follows
Screenshot / copy paste any relevant settings I cared for into a word document. Also backup the traffic graphs.
30-30-30 reset
Log into router, set password, update to dd-wrt.v24-30880_NEWD-2_K2.6_mini-e2000.bin
After a few minutes, logged into router and did update to dd-wrt.v24-30880_NEWD-2_K2.6_mega-nv60k.bin
After a few minutes, though everything looked fine, for good measure I did another 30-30-30 reset.
After a few minutes I logged in, set password and went through each screen setting things up.
So far a great success. Speedtest is 49.81 down by 4.90 up (my cable package is 50/5 so thats within tolerance).
There's a whole new tab for ipv6 for me to play with now. Plus a whole slew of new features here and there including a new dark theme which I am really digging. I'm off to the races yet again with my 320n to e2000 conversion. It's been a few trouble free years on the old build. Lets keep this thing going until it croaks.
I just wanted to post an update for anyone using an old 320n with CFE conversion to e2000.
Now that its been a week, I can say that firmware dd-wrt.v24-30880_NEWD-2_K2.6_mega-nv60k.bin works just fine on this router.
I initially had issues with DNSMasq crashing when I first configured it with Hurricane Electric IPv6 tunnel. However I altered the DNSMasq.conf file and I haven't had a single issue. I have a thread here with my conf file if interested: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=310117&highlight= . My 50/5 mbps connection is delivered as expected. I've done numerous video streaming (1080p and 4k) from multiple sources. It's gone through its stress test and it survives.
I'm running SSH (SSH tunnel from remote to browse through my connection or RDP over SSH tunnel).
I use WOL, Hurricane Electric IPv6 tunnel, syslog to papertrailapp, QoS for SIP priority, no-ip ddns, dnsmasq (not radvd) for IPv6 dns/dhcp, and upnp.
Like I said in the previous post, even though I had an older 14xxx series mega firmware on, I still had to flash to the 30880 mini-e2000 first, then I could flash to the mega-nv60k.bin.
I chose build 30880 because there was another blog with someone recommending this build for the e4200. I figured e4200 is a just a little newer than the e2000, I suppose one difference is that it can do 2.4 and 5 GHz simultaneously. It's always a challenge to try the latest builds on these older pieces of hardware, but I'm glad that the performance did not suffer.
Ok now that I've had some time with this build, I can say its not perfectly stable. I'm not sure if its because I have ipv6 tunnel configured and dnsmasq doing dns/dhcp duties, but every so often I just lose connection and I cannot get an IP address, nor can I ping or log into the router if I statically assign one.
It takes about 15-20 minutes but then the problem resolves on its own. It happens about once a day, it self resolves if you let it alone. Papertrail app always shows these syslog events around the times this happens:
There are always a lot of dropbear events, various IP's trying to log into root from around the world (usually from APNIC region) and I can't say if that's what causes it or not. I'm about to undo all the IPv6 configuration and see if its more stable that way.
I searched the logs for "WAN is up" which indicates the system soft booted in some way and here's the timestamps:
Jul 27 07:33:07
Jul 25 22:27:33
Jul 23 06:01:15 (this is my normal weekly Sunday 6 Am reboot cron job)
Jul 20 23:19:19
You can see the gap in the time stamp and before each freeze event the last log is: dropbear: Exit before auth: Exited normally
In fact, if you just mount da damn thing to wall, it's a matter of physics: the warm air will have a much more easy flow upwards... meaning, leaving the unit sooner... I have mine on the wall for the past 6 years, never had any issue. (yeah, I realize earlier units were prone to overheat).. _________________ //-- alex --//
Joined: 12 Jun 2007 Posts: 32 Location: Aachen, Germany
Posted: Wed Sep 26, 2018 18:29 Post subject:
Hi,
this isn't necessarily related to the dd-wrt firmware. I think it might come due to aging. Mine is converted to, and i had to play with it a bit the last days going to stock fw and back...
What i found was, that almost those leds i used very frequent over time are all noticeable darker. Especially between LAN port 4 compared to LAN port 1. I nearly never used port 4 which might be the reason for it to shine brighter. _________________ |2e4per
Just got one converted. And, then noticed that WRT320N goes forward with new K3 DD-WRT releases and E2000 does not.
Darnit!
Does anyone have the 1305 CFE?
That one.
I need the second run CFE for WRT320N.
Or, even newer than boardrev=1305, so long as it is WRT320N.
Thanks! _________________ R6250 with fan on; wifi off
R6300.1 mips DD-WRT 42617 Giga AP
WNR3500Lv2 DD-WRT 33525 K3 Giga
E3000 5ghz multicast AP DD-WRT 33525 K2.6
WRT54GSv2 long range AP HyperWRT 15
2 WR841Nv9 DD-WRT 33006 AP
Just got one converted. And, then noticed that WRT320N goes forward with new K3 DD-WRT releases and E2000 does not.
Darnit!
I'm not following? You use the trailed build to upgrade the k3x nv60k devices (same as with my E2500's). The k3x nv60k file went missing as some point...
Edit: Note that back when it was still there (e.g. 2013), it was the same size as the trailed Linksys builds anyway (Netgear trailed builds are slightly bigger for their header). _________________ #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