Posted: Mon Mar 19, 2018 7:21 Post subject: Netgear R7000 WiFi disconnect/invalid password
I have been having DD-WRT WIFI disconnect issues on R7000
I have observed the exact same issue on R7000 on 33675, 34320, 35030, to name a few (KONG versions). It might have been present on earlier firmware but I do not have a record of it.
Typically I get into a situation where SSID is no longer broadcasted. A total freeze. Sometimes after 3 hours, sometimes after 3 days. Driving the family crazy (and me towards stock FW :/)
Symptom:
The SSID is still broadcasted, but the password is no longer accepted (on iPad, iPhone 6, iPhone X, and Windows 10 pc).
This is not related to range. I can be sitting stationary 5 meters from my router with line-of-sight, and have it happen.
My setup (not sure if all relevant)
Separate Guest WLAN on WL0.1, with Network Isolation
Separate Guest VLAN (one port)
DNSMasq used for IP addresses in both default LAN/WLAN and the Guest
Judging from the forum I’m not alone in experiencing this.
Anyone got a lead on a solution?
@Imalilteapot, @blaser, @limerick_fr, @Vaako, @ludovic (my apologies if I wrongly identified you as sharing this issue)
Posted: Tue Mar 20, 2018 4:10 Post subject: Thanks
I've tried erasing nvram before, with no success.
I'll see if I can retry from scratch (based of netgear FW) in the weekend. But it seems to me that drivers or perhaps DHCP are the most likely culprits.
Sadly I have no effective way of reliably triggering the issue.
Posted: Tue Mar 20, 2018 13:41 Post subject: Re: Thanks
egc wrote:
Put settings in manually, for wifi settings use mixed.
linust wrote:
I've tried erasing nvram before, with no success.
I'll see if I can retry from scratch (based of netgear FW) in the weekend. But it seems to me that drivers or perhaps DHCP are the most likely culprits.
As egc alluded, to what is your Wireless Network Mode set? Don't use *-Only modes, Auto channel selection, nor the same SSIDs for different radios. If the Mode is Mixed, try N/AC-Mixed. _________________ #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
Posted: Wed Mar 21, 2018 0:56 Post subject: Thanks
Quote:
As egc alluded, to what is your Wireless Network Mode set? Don't use *-Only modes, Auto channel selection, nor the same SSIDs for different radios. If the Mode is Mixed, try N/AC-Mixed.
Thanks. I have tried both N/AC-mixed before as well as the default setting. I am not 100% sure about the doing nvram erase in conjunction with the mixed test though. Will do that.
I have consistently had the same SSID for both radios. Is that an issue with the current drivers, or just a way of facilitating detection of which radio went down?
Posted: Wed Mar 21, 2018 13:00 Post subject: Re: Thanks
linust wrote:
Quote:
As egc alluded, to what is your Wireless Network Mode set? Don't use *-Only modes, Auto channel selection, nor the same SSIDs for different radios. If the Mode is Mixed, try N/AC-Mixed.
Thanks. I have tried both N/AC-mixed before as well as the default setting. I am not 100% sure about the doing nvram erase in conjunction with the mixed test though. Will do that.
I have consistently had the same SSID for both radios. Is that an issue with the current drivers, or just a way of facilitating detection of which radio went down?
It's not an issue but for identifying the problem it would be good if you use different names. Maybe it's happening only in one band. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Mon Mar 26, 2018 5:39 Post subject: Crash! :-/
Yup that crashed. Two times this weekend.
I'm starting to suspect either DHCPd or the drivers for the radio.
Since
- I have multiple ranges served (one for LAN/WLAN, one fo Guest Wifi and one for a tagger port Port4/VLAN3
- I do not seem to get an address even when connecting with cable after a crash)
- I use 10.0.0.1/255.255.255.0 as LAN/WLAN range and some people seems to experience issues with it
I've revered the VLAN3 tagging and thus removed the additional DHCPd (now only two ranges are being served)
Should I add a separate USB key and direct syslogd messages there to capture events up until crash? Or is the USB support likely to influence the stability?
Crashed again. But this time only the guest WIFI crashed.
Guest WiFi is only on wl0.1
Both wl0 and wl1 works.
The only things unusual in syslog is the failed password events, and a ntp issue. Attaching images.
The time seems to be correct on the router so I doubt if the ntp has anything to do with it.
What other instrumentation should I do while the router is in this crashed but accessible state?
Crashed again. But this time only the guest WIFI crashed.
Guest WiFi is only on wl0.1
Both wl0 and wl1 works.
The only things unusual in syslog is the failed password events, and a ntp issue. Attaching images.
The time seems to be correct on the router so I doubt if the ntp has anything to do with it.
What other instrumentation should I do while the router is in this crashed but accessible state?
Smaller pictures please. _________________ I am far from a guru, I'm barely a novice.
Getting rid of the guest network on wl0.1 made a huge difference in stability on my R7000P with Kong 32000 and up. I went from ~12 hours between reboots to closer to a week.