Posted: Sun Dec 31, 2017 14:43 Post subject: Re: Steps
I would use the latest, same file names but instead of using either 21676 or 25697, use 34311. I understand you are already on a higher build (25697>21676) but you must downgrade to upgrade So you would get:
1: Hard Reset 30-30-30 (Factory Defaults, through GUI, don't use the reset button)
2: Flash - K3X_21676_mega_nv60K
3: Hard Reset 30-30-30 (Factory Defaults, through GUI, don't use the reset button)
4: - K3.X_34311_mega_e3000
5: Hard Reset 30-30-30 (Factory Defaults, through GUI, don't use the reset button)
6: reconfigure everything
before I flash the K3.X_34311_mega_e3000, I have to flash the K3.x_21676_mega_nv60K first.
Only then can I use the current K3.X version which has no nv60 extension
Joined: 04 Jan 2007 Posts: 11546 Location: Wherever the wind blows- North America
Posted: Mon Jan 01, 2018 13:57 Post subject: Re: NV60
As you can read (I hope so), I already have a xxx version on the device!
So I can not install K2.6_21676_mini_e3000 !!!
That would destroy the device.
The K2.6_21676_mini_e3000 I can install if I have a Linksys version on the device!
The K2.6_21676_mini_e3000 version is the first version I need to install on an E3000 when I come from the Linksys version !!
So thank you for the nonsensical advice.
If the exact procedure is too much for you, you do not have to write an answer!
If you have a K2.6 build on the device now and are trying to go to K3.x....then you just follow the instructions...
If you don't start with the K2.6_21676_mini_e3000 build... then K2.6_21676_mega.nv60k...it won't upgrade to the K3.x correctly.
Feel free to follow any nonsensical advice you like...but I actually have an E3000 that I've bricked and recovered at least a dozen times now.
With all the posts floating in this thread...exactly what build is currently on your device....it is easy to get lost in it all.
Due to a lot of work I was not able to carry out the installation yet. I'll probably do that tomorrow.
Since there are new problems since January and I must to completely renew the router anyway, I would like to ask a question:
there are already current a " K3.xx " versions in which the problem "Meltdown and Spectre " was fixed?
Posted: Sat Jan 06, 2018 21:35 Post subject: Meltdown and Spectre
Meltdown and Spectre only effect Intel, AMD and ARM CPUs. The Linksys E3000 is Broadcom based, it is not affected. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
UBNT EdgeRouter X - switch
Posted: Wed Jan 17, 2018 21:27 Post subject: HTTPS Gui Issue
I'm came across this thread while searching for replacement firmware that had been patched against KRACK. Thank you to the contributors for the great instructions on how to upgrade to K3.X. I'm coming from non-DD-WRT firmware and the instructions were perfect.
I've upgraded to the Dec 29, 2017 release for the Linksys E3000 (dd-wrt.v24-34311_NEWD-2_K3.x_mega-e3000.bin). Everything has been configured to my liking and things are smooth. However, I have been unable to get HTTPS local/remote Gui access to work. Both Firefox and Chrome time out with Firefox complaining that the "Secure Connection Failed".
This seems to be a TLS or SSL issue that reminds me of when browsers dropped legacy support post-heartbleed. Netstat shows HTTPS listening.
I have also tried the Jan 7 (34411 release). I've performed 30/30/30 resets and Gui default resets.
I have the following questions/concerns:
1. Is the Heartbleed bug present in this firmware?
2. Is KRACK (really) patched in this firmware?
3. Is there a reason for the out-of-date handshake between my browser and the software running on the router (eg: space constraints)?