Posted: Sun Feb 26, 2017 22:02 Post subject: Linksys EA6500v2 | 2.4GHz No Longer Works
I just upgraded from r30709 (which was rock solid) to r31277 and 2.4GHz went bad. I upgraded and reset settings, same thing. NVRAM is 24kb after cleanup script. Immediately after a reboot, 2.4GHz shows good signal, then about a second later it's down below -80dBm (at 5ft on my Galaxy S7 using WiFi Analyzer).
5GHz works fine (-35dBm).
Reverted back to r30709 and it didn't help. Went back to r31277. No direction to go but forward I guess.
Last edited by dacheze on Sat Mar 18, 2017 20:53; edited 1 time in total
Just upgraded to Firmware: DD-WRT v3.0-r31690 std (03/17/17) and 2.4GHz showed 5 bars strength for about 30 seconds then went back down to -80dBa.
Any commands I can run to see what's up?
---Edit----
I enabled Syslogd and Klogd. SSH'd to router:
#cat /var/log/messages shows:
Mar 18 21:21:36 JHR daemon.info mstpd: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 8
Mar 18 21:21:36 JHR kern.warn kernel: Hooks already unregistered
Mar 18 21:21:39 JHR user.info : NAS : NAS lan (wl0 interface) successfully started
Posted: Mon Mar 20, 2017 18:42 Post subject: Re: Linksys EA6500v2 | 2.4GHz No Longer Works
dacheze wrote:
Reverted back to r30709 and it didn't help. Went back to r31277. No direction to go but forward I guess.
Did you reset after you reverted back to 30709? Or else if this model can take an `erase nvram`, try that. I don't have this router, but I know a few models should not have 'erase nvram' done. Check the wiki and router/model thread(s). _________________ #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
@sploit -- gotta read the whole post before replying..
@jwh7 -- While searching around to see if 'erase nvram' is safe for my router, I found another post with a user that has the same router and issue as me (that even you replied to as well). Looks like the newer firmware is breaking 2.4GHz for us.
