Posted: Thu Jan 23, 2020 10:49 Post subject: WRT310N V2 radio "off" after install of v24-40559_
Dear developers,
I want to let you know that I have upgraded my Linksys WRT310-N V2 firmware to the newest dd-wrt.v24-40559_NEWD-2_K2.6_mini and the Wi-Fi radio switched to "off" permanently with it. I even did a 30/30/30 reset of the router (before and after flashing as it's proposed in your FAQ) and the radio was still off, so I had no SSID visible from any device.
Please note, that previously I had the v.24-sp2 Build 14896 08/07/10 NEWD-2 K2.6 mini installed on my device for about 5 years and I had NEVER any issue with this firmware.
Looking for the whole day I was very lucky to finally find that old firmware version on some ftp, as there is no such firmware available on your website and I have no access to your ftp!
When I have flashed back to the old firmware the radio was still off until I have done the 30/30/30 reset again!
Please be as kind as to correct this bug, meanwhile I suppose there should be a remark of it in the Router's Database.
Posted: Thu Jan 23, 2020 15:31 Post subject: Re: WRT310N V2 radio "off" after install of v24-40
Levitsky86 wrote:
I want to let you know that I have upgraded my Linksys WRT310-N V2 firmware to the newest dd-wrt.v24-40559_NEWD-2_K2.6_mini and the Wi-Fi radio switched to "off" permanently with it. I even did a 30/30/30 reset [...]
previously I had the v.24-sp2 Build 14896 08/07/10 NEWD-2 K2.6 mini installed on my device for about 5 years and I had NEVER any issue with this firmware.
14896 is a bad build, right from the Peacock Announcement, and 40559 isn't good either. The minimum old recommended build was 14929. From the wiki, it looks like 33679 was good too.
But first, try 41686; no need to reset before unless you enabled a bunch of services. After flashing, log into telnet (or SSH) and run `nvram erase && reboot` then manually set up. If wireless still isn't working, try 33679 and for that you need `erase nvram && reboot` instead).
Edit: thx kp...fixed. I forgot to highlight and URL-ize it. _________________ #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
Last edited by jwh7 on Thu Jan 23, 2020 18:04; edited 1 time in total
jwh7, I see that if I try to log into Telnet on my router is says that the login is incorrect. Does it use another login and password for Telnet and SSH that differs from the Web login, or not?
jwh7, I see that if I try to log into Telnet on my router is says that the login is incorrect. Does it use another login and password for Telnet and SSH that differs from the Web login, or not?
He was just pointing out my post that originally had the url syntax messed up. _________________ #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 have tried the newest version 41686 and radio is still "off" with it. I have executed `nvram erase && reboot` in Telnet and the device became unreachable for pretty long time. Luckily the 30/30/30 reset helped as I started thinking it became a brick and it was very nervous.
Now I have flashed back to the 14896 did the 30/30/30 reset and the radio turned on again.
As for the 14929 I would have to look for it on the Web.
I have tried the newest version 41686 and radio is still "off" with it. I have executed `nvram erase && reboot` in Telnet and the device became unreachable for pretty long time. Luckily the 30/30/30 reset helped
The GUI was unreachable after a long time? Just want to clarify it's not the telnet session, which would immediately disconnect. And after the 30-30-30 and going back into the GUI (or was it not available?), the radio was still off, without a means to enable? E.g. enable WPA2-AES and Apply to see if the SSID pops up.
If so, try 33679 as noted before, w/ the nvram difference. Btw, 14929 is just the next 'official' 2010 build after 14896. _________________ #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
1) I have flashed the firmware;
2) Run a command through Telnet and the Telnet have disconnected instantly.
3) The router became unreachable for about 5 minutes. - Definitely longer then after flashing the firmware.
4) Then it either turned on finally, or I have done the 30/30/30 reset (sorry I have forgotten already )
5) I saw in GUI that the radio was still turned off and I haven't try to enable the SSID, as its always enabled by default already. And besides, if the radio shows off status, I thought that there is no sense to try it.
6) So, I flashed back to the old firmware and had to do a 30/30/30 reset after that to make the radio switch to on.
kernel-panic69, many thanks for your links! I would try these builds when I'd have some free time.
6) So, I flashed back to the old firmware and had to do a 30/30/30 reset after that to make the radio switch to on.
This could just be a simple nvram parameter problem. Have you tried upgrading without resetting first?
Check this from telnet on your old working build:
nvram show |grep wl.*enab.*|grep -v wds
Then upgrade and check again...then reset and check again, and see if something disappears or changes to disable the radio. If so, put it back with:
nvram set {parameter}={value}
nvram commit && reboot
Run `dmesg` in each case too, to see if maybe the wireless driver is crashing. Same for this:
ps |grep -e wl -e nas|sed s:-k.*$::
(The `sed` strips out your SSID & p/w.)
A more thorough way to investigate nvram is to `nvram show` all cases and copy into a spreadsheet and sort/align, so you can check all diffs. _________________ #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
jwh7, sure I have tried flashing without reset first. I have started to flash with reset then to see if the radio would turn to on, or not.
Thanks for your help again! I would definitely try the solutions you've proposed when I've got some free time as my router is always in use .
Please also note that I am not a very skilled Linux user, so I may run only commands that won't need to run any other commands (except if you would tell me such few at once) to make the device work again.
So, I hope all of those commands you have written are safe for unskilled user. Thanks again!
This is what I've got with my working old build:
root@Linksys:~# nvram show |grep wl.*enab.*|grep -v wds
size: 19680 bytes (13088 left)
wl0_br1_enable=0
wl0_abenable=1
wl1_abenable=1
This is what I've got with my working old build:
root@Linksys:~# nvram show |grep wl.*enab.*|grep -v wds
size: 19680 bytes (13088 left)
wl0_br1_enable=0
wl0_abenable=1
wl1_abenable=1
Is it normal, or not?
Depends on what they (or a full nvram diff, or dmesg info) show when the wireless isn't working. _________________ #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
jwh7, I have just flashed to 14929 and it's fine! The radio is on and all of the settings have been saved (should I still do a reset and set up after flash in such case, or not?).
So, should I still try the 33679 too, or just leave the 14929 version?
Btw, I have checked the "nvram show |grep wl.*enab.*|grep -v wds" - and the parameters are just the same as I wrote above on 14896.
P.S. Well, I have tried the 33679 too! The radio is off with it! I have checked "nvram show |grep wl.*enab.*|grep -v wds" and those three parameters were the same as with the working versions (14929).
I have tried the `erase nvram && reboot` and it did nothing! The radio was still off. Did a 30/30/30 reset and the radio was off also.
So, I have flashed back to the latest working for me 14929.
You know, it seems to me that something is wrong with those newer firmwares with the new looking GUI design.
But I have made 2 files with `nvram show` for the working and not radios. So I would try to investigate them.