Netgear R7000 WiFi disconnect/invalid password

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page 1, 2  Next
Author Message
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Mon Mar 19, 2018 7:21    Post subject: Netgear R7000 WiFi disconnect/invalid password Reply with quote
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)
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12837
Location: Netherlands

PostPosted: Mon Mar 19, 2018 12:19    Post subject: Reply with quote
One thing you can try (strongly recommended) telnet to your router and issue:
Code:
erase nvram && reboot

Put settings in manually, for wifi settings use mixed.
Kong's latest (test) builds should be good.

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Tue Mar 20, 2018 4:10    Post subject: Thanks Reply with quote
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.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Tue Mar 20, 2018 13:41    Post subject: Re: Thanks Reply with quote
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
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Wed Mar 21, 2018 0:56    Post subject: Thanks Reply with quote
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?
Xeon2k8
DD-WRT Guru


Joined: 11 Feb 2016
Posts: 1288

PostPosted: Wed Mar 21, 2018 13:00    Post subject: Re: Thanks Reply with quote
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)
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Fri Mar 23, 2018 3:12    Post subject: So far so good Reply with quote
30h ago i re-flashed, erased, rebooted, configured with very small steps (save/apply cycles). And using N/AC-mixed, and separate names for radio.

So far so good. I'll let it cook for a week and monitor the situation.

When doing the full reconfig i do realize that the setup has a few bits and pieces

DDNS, Guest WLAN (Isolated with NAT), Dual DHCP (DNSMasq), UPNP and a few port/range forwards, and SSHd (for admin access).

But so far so good.
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Sun Mar 25, 2018 7:47    Post subject: Reply with quote
I had one deadlock in my system after about 26h, but it seems to have coincided with ISP issues so I will give it the benefit of a doubt.

Some more details of the setup:

Flashed 35030 (from 20 march) as CHK

erase nvram && reboot


different SSID on all radios
wl0 wl0.1 wl1 (guest WLAN/unbridged, NAT with network isolation)


DHCPd additional for Guest wl0.1 and port assigned to VLAN3 (Untrusted/Guest Wired)

10.0.0.1/255.255.255.0 (Lan and WLAN)
10.0.1.0/255.255.255.0 (Guest Wireless)
10.0.2.0/255.255.255.0 (Untrusted/Guest Wired)


DDNS, SSHd, UPNP and port forward, port forward range, syslog (in memory only atm since i do not want to mess with USB support)
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Mon Mar 26, 2018 5:39    Post subject: Crash! :-/ Reply with quote
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?
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Tue Mar 27, 2018 0:44    Post subject: Reply with quote
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?
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Tue Mar 27, 2018 1:11    Post subject: Reply with quote
linust wrote:
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.
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Tue Mar 27, 2018 3:13    Post subject: Reply with quote
Ok. Now smaller pictures (both in kb and somewhat in pixels)


Status.PNG
 Description:
Status page. Memory, load, and RX/TX seems good...
 Filesize:  57.13 KB
 Viewed:  4905 Time(s)

Status.PNG



2.png
 Description:
Failed NTP update
 Filesize:  73.17 KB
 Viewed:  4908 Time(s)

2.png



1.png
 Description:
Failed auth
 Filesize:  33.17 KB
 Viewed:  4908 Time(s)

1.png


edgar_is
DD-WRT Novice


Joined: 21 Feb 2018
Posts: 7

PostPosted: Wed Mar 28, 2018 4:09    Post subject: Reply with quote
This has been happening to me as far as I can remember. I've followed instructions on proper resetting before and after flashing.

This is especially annoying when I'm out of town and suddenly my home network goes down and I can't access my Canary camera or HomeKit devices.

Last firmware I was running was kong r35030M (02/19/1Cool. I just did a ddup update to the latest firmware 35530.

The only thing out of the ordinary on my network is that I have a Raspberry Pi acting as my DNS server using Pi-Hole.
linust
DD-WRT Novice


Joined: 16 Jan 2018
Posts: 13

PostPosted: Wed Mar 28, 2018 11:04    Post subject: Reply with quote
Hi @edgar_is

Do you have a Guest WLAN or multiple DHCP setup?
fhteagle
DD-WRT Novice


Joined: 21 Mar 2018
Posts: 6

PostPosted: Wed Mar 28, 2018 15:26    Post subject: Reply with quote
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.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum