working good here so far ( hold shift reload browser after boot if buttons say undefined ) _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
OpenVPN CLIENT works fine (nordvpn server)
5GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
2.4GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
NAS via USB Samba also working fine
Updated 2x WRT1200AC v1 from r39927 to r39944 with no reset, no issues using Waterfox 56.2.10 (64 bit) Up-time 45+ minutes Usual OpenVPN client yellows in syslog. No reds with this release.
Wired, wireless,OpenVPN client, DNSMasq and VPN passthru (Corp VPN by-passes OpenVPN Client) working as expected with no wired/wireless or OpenVPN drops noticed after update. All wireless devices connected.
Kernel Version Linux 4.9.180 #1065 SMP Tue Jun 4 02:14:52 CEST 2019 armv7l
Router Crashed and rebooted somewhere in the 6th hour, SO i reflashed this time resetting and reloading backup nvram, see what we get this time around.
Update: seems to be ok now _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Everything seems to work OK (samba, wireguard vpn etc.) till I've notice that I don't have at all wifi AP on 2.4ghz band and as well I couldn't connect on 5ghz.
I can see the AP on 5ghz band but I get all the time "Connection failed" message when I try to connect any client...
So, I logged on on ssh an typed the command:
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
I got the next thing with the remark that 2g is disable...
driver name: mwlwifi
chip type: 88W8864
hw version: 7
driver version: 10.3.8.0-20181120
firmware version: 0x0702091b
power table loaded from dts: no
firmware region code: 0x30
mac address: 00:25:9c:14:29:48
2g: disable
5g: enable
antenna: 4 4
irq number: 44
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000007
radio: enable
iobase0: e0c00000
iobase1: e0d80000
tx limit: 768
rx limit: 64
qe trigger number: 21025
Booted back in the second partition where I had version r39884 (05-30-2019) and the problem with the wifi still persist.
Before the upgrade everything was working fine in this firmware version...
Now I'm back with ddwrt version r39884 (05-30-2019) with no wifi.
Any ideea guys how can I fix back my wifi?
Thank you in advance for any advice. _________________ Linksys WRT1900ACSv2 with DD-WRT v3.0-r48886 std (05/16/22)
WiFi: 2.4ghz(disabled), 5ghz(Client/AC-Only)
Wireguard Mullvad client PBC
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Wed Jun 05, 2019 19:10 Post subject:
flock wrote:
Updated using FF 67.0.1 (x64)
Everything seems to work OK (samba, wireguard vpn etc.) till I've notice that I don't have at all wifi AP on 2.4ghz band and as well I couldn't connect on 5ghz.
I can see the AP on 5ghz band but I get all the time "Connection failed" message when I try to connect any client...
So, I logged on on ssh an typed the command:
cat /sys/kernel/debug/ieee80211/phy0/mwlwifi/info
I got the next thing with the remark that 2g is disable...
driver name: mwlwifi
chip type: 88W8864
hw version: 7
driver version: 10.3.8.0-20181120
firmware version: 0x0702091b
power table loaded from dts: no
firmware region code: 0x30
mac address: 00:25:9c:14:29:48
2g: disable
5g: enable
antenna: 4 4
irq number: 44
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000007
radio: enable
iobase0: e0c00000
iobase1: e0d80000
tx limit: 768
rx limit: 64
qe trigger number: 21025
Booted back in the second partition where I had version r39884 (05-30-2019) and the problem with the wifi still persist.
Before the upgrade everything was working fine in this firmware version...
Now I'm back with ddwrt version r39884 (05-30-2019) with no wifi.
Any ideea guys how can I fix back my wifi?
Thank you in advance for any advice.
Interestingly, I have a similar problem with my 2.4 whereas it doesn't even show on the wireless page. My 5Ghz however is fine although I don't use it in AP mode but rather as a Client Bridge.
My loss of 2.4 didn't start due to an upgrade but rather because I had to replace the fan in my V1 and in the process I assumed I damaged the connector for the WiFi module. Since I had a location for which I only need it to operate as a client with cameras on ethernet it serves well.
I also ran the check command and received the same results as you. I ran the command on another V1 in client mode (5Ghz) and although it is running numerous devices off the 2.4 the results indicated that the 2.4 was enabled and the 5 was disabled.
In short don't depend on the results you get back from the command check.
I upgraded my remote V1 to r39944 without any problems and all is working fine. Since your ACS and the V1 both use the same WiFi chips I can only assume you may have a hardware failure just I did, even though the circumstances may be different.
Hopefully someone else will jump in and be of more assistance. Sorry for the bad news from me. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55460
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55460 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55460 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55460
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
have you both tried making a nvram backup, then reflash with what ever firmware you want to go to with the reset to default option then restoring the nvram backup? ( note: if you use static under wan setup then you need to re input this section only after restore of backup ) after a nvram backup restore i give it 5 mins or so and go turn the router off then on as well.
i find doing this fixes stuff like this for me
where the new problem carries over even going to previous firmware.
on a side note on this build i notice my 2.4ghz bridge seems to screw up with the 2m transmit thing unless i change it to gmode only.. ( keep in mind this is a long distance bridge like 1.5 acres)
G-Only
Radioname Interface Uptime TX Rate RX Rate Info Signal
ath0 23:45:15 54M 54M LEGACY -65 -96 31 66%
ngmixed will do this mess a good bit.
Radioname Interface Uptime TX Rate RX Rate Info Signal
ath0 23:45:15 2M 54M LEGACY -65 -96 31 66% _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.