I apologize for asking this question here. I'm sure you are tired of answer it, however, I have been studying this site, the Wiki, and the main DD-WRT pages for about two weeks now. I've taken numerous notes on the do's and don't s regarding initial upgrades. My problem stems from confusion about which build to use to go from the linksys firmware to the first DD-WRT build. The wiki page for my specific router, Cisco E2000, indicates that I should use this build, dd-wrt.v24-14929_NEWD-2_K2.6_std_usb_ftp-e2000.bin. However, the Database Search page indicates I should use this build, dd-wrt.v24-21061_NEWD-2_K2.6_mini-e2000.bin. Can I get an explanation as to which build I should use. Thank you.
The router database is old and outdated ... and some of the wiki is old outdated or updated with incorrect info.
Questions about the E2000 should be asked in the 'broadcom forum' but since I stopped by .....
The http://www.dd-wrt.com/wiki/index.php/Linksys_E2000 says -
As of July 2010 you can only use the trailed builds with the e2000 name in it for initial flashing and nothing else, using other bin's without the e2000 name in it for initial flashing may result in a bricked unit! After you have dd-wrt installed to your unit, you can then use the e2k-e3k.bin's for upgrading to newer builds. Using builds without e2k-e3k in the filename after initial flashing WILL BRICK YOUR ROUTER!
K2.6 builds after that have trouble with VAPs -- any newer build than that you might want a K3.x ...
then again you really should ask all this in the 'broadcom forum' -- they will prolly kick us outta here.
So going by the first part of your post, I can use the NV60k build after the 21061 mini initial install.
That is correct...
Read announcements top of this forum.
Read the peacock thread.
There is a chart listed in e2000 wiki listing some builds and what they will and will not do...but some are K3.x builds. If you have super fast internet the k3.x will be slower doing a NAT connection ..slower than a K2.6 build.
The 25974 I mentioned should be ok for most anything you want to do.
Many dd-wrt builds do some things better on some routers with a specific build. Just depends on what you really need it for.
To find out most things about the e2000 do a google >>> 'redhawk e2000 dd-wrt'
He played with one for ages...guess he probably still does.
The router database is old and outdated ... and some of the wiki is old outdated or updated with incorrect info.
Questions about the E2000 should be asked in the 'broadcom forum' but since I stopped by .....
The http://www.dd-wrt.com/wiki/index.php/Linksys_E2000 says -
As of July 2010 you can only use the trailed builds with the e2000 name in it for initial flashing and nothing else, using other bin's without the e2000 name in it for initial flashing may result in a bricked unit! After you have dd-wrt installed to your unit, you can then use the e2k-e3k.bin's for upgrading to newer builds. Using builds without e2k-e3k in the filename after initial flashing WILL BRICK YOUR ROUTER!
K2.6 builds after that have trouble with VAPs -- any newer build than that you might want a K3.x ...
then again you really should ask all this in the 'broadcom forum' -- they will prolly kick us outta here.
I really appreciate the tip on firmware version. I was having all sorts of issues with Repeater Bridge and WDS. Switched to 25974 and all problems are solved.
The router database is old and outdated ... and some of the wiki is old outdated or updated with incorrect info.
Questions about the E2000 should be asked in the 'broadcom forum' but since I stopped by .....
The http://www.dd-wrt.com/wiki/index.php/Linksys_E2000 says -
As of July 2010 you can only use the trailed builds with the e2000 name in it for initial flashing and nothing else, using other bin's without the e2000 name in it for initial flashing may result in a bricked unit! After you have dd-wrt installed to your unit, you can then use the e2k-e3k.bin's for upgrading to newer builds. Using builds without e2k-e3k in the filename after initial flashing WILL BRICK YOUR ROUTER!
K2.6 builds after that have trouble with VAPs -- any newer build than that you might want a K3.x ...
then again you really should ask all this in the 'broadcom forum' -- they will prolly kick us outta here.
I really appreciate the tip on firmware version. I was having all sorts of issues with Repeater Bridge and WDS. Switched to 25974 and all problems are solved.
Yes Sir, all k2.6 builds after January 2015 seem to have Repeater Bridge broken and many have lots problems with a VAP just for guest network.
There should be no problem using an old build if it's working for you.... It is within your network so shouldn't have any worry.
If you wanted to use it for a main gateway or an openVPN setup I would suggest using a newer K3.x build.
You would have to search about the E2000.... I don't have one and don't know how well it would do with a K3.x build
I really appreciate the tip on firmware version. I was having all sorts of issues with Repeater Bridge and WDS. Switched to 25974 and all problems are solved.
There should be no problem using an old build if it's working for you.... It is within your network so shouldn't have any worry.
If you wanted to use it for a main gateway or an openVPN setup I would suggest using a newer K3.x build.
You would have to search about the E2000.... I don't have one and don't know how well it would do with a K3.x build
Status: working as AP, basic settings 2,4GHz and 5Ghz are working, uptime 24H
@jjwatmyself - are you the same user from XDA? If so, then 'hey!' _________________ #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
Yes Sir, all k2.6 builds after January 2015 seem to have Repeater Bridge broken and many have lots problems with a VAP just for guest network.
There should be no problem using an old build if it's working for you.... It is within your network so shouldn't have any worry.
If you wanted to use it for a main gateway or an openVPN setup I would suggest using a newer K3.x build.
You would have to search about the E2000.... I don't have one and don't know how well it would do with a K3.x build
Interested in your comment:
mrjcd wrote:
It is within your network so shouldn't have any worry ... If you wanted to use it for a main gateway ... I would suggest using a newer K3.x build.
Yes Sir, all k2.6 builds after January 2015 seem to have Repeater Bridge broken and many have lots problems with a VAP just for guest network.
There should be no problem using an old build if it's working for you.... It is within your network so shouldn't have any worry.
If you wanted to use it for a main gateway or an openVPN setup I would suggest using a newer K3.x build.
You would have to search about the E2000.... I don't have one and don't know how well it would do with a K3.x build
Interested in your comment:
mrjcd wrote:
It is within your network so shouldn't have any worry ... If you wanted to use it for a main gateway ... I would suggest using a newer K3.x build.
Is there a vulnerability?
I couldn't possibly answer that with certainty without knowing your network and what the exact config of this router is.
Some things could be more vunerable than need be.....there are several years of updates to some components of the firmware than what was recommended back in the old days.
Some things are updated in attempt to make better some for purely security reasons ....many changes are for a little of both.
CVE and other fixes are pulled in periodically, plus s/w packages have their own updates that do the same. So it depends a bit on what services you use; e.g. Samba... _________________ #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
Warning! ⚠ All builds after 33215 will brick your E2000. 33215 works great though and is a 3.x kernel.
Edit:
OpenVPN / SSHD / DDNS all seem to work as well.