R7000 forces wireless clients to re-authenticate

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
NM6636
DD-WRT Novice


Joined: 19 Nov 2022
Posts: 3

PostPosted: Fri Nov 25, 2022 21:31    Post subject: R7000 forces wireless clients to re-authenticate Reply with quote
Hi there! I have a Netgear R7000 currently running DD-WRT version r50927. At random intervals, the WiFi connection drops and the clients are given a prompt to re-enter the network username and password. After entering credentials, the connection is stable for a few hours until it repeats. This isn't a client issue; it occurs on multiple devices. This issue is also not exclusive to version r50927, I have been noticing this occurrence for a few months now, even back to versions in July.

I have previously resorted to version r48567 (3/23/22), which does not have this issue. However, I would like to stay on more recent DD-WRT versions due to security reasons. I have tried to solve this issue through multiple resets, both a factory reset from the GUI and "nvram erase && reboot" into the terminal, and even upgrading/downgrading to more recent versions. One person instructed me to disable TurboQAM, that did nothing to solve it. All of these measures failed to solve this issue.

Wireless settings are as follows:




Wireless security is WPA2-PSK with CCMP-128 (AES) algorithm.

I noticed this in the syslog:
Code:
Nov 25 15:10:15 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPREQUEST(br0) 192.168.8.179 a2:3e:ab:de:82:de
Nov 25 15:10:15 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPACK(br0) 192.168.8.179 a2:3e:ab:de:82:de
Nov 25 15:13:20 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPREQUEST(br0) 192.168.8.227 46:0e:cc:ca:8e:ff
Nov 25 15:13:20 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPACK(br0) 192.168.8.227 46:0e:cc:ca:8e:ff
Nov 25 15:13:39 DD-WRT kern.warn kernel: [256765.663223] br0: received packet on eth1 with own address as source address
Nov 25 15:13:39 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPREQUEST(br0) 192.168.8.69 9c:29:76:32:ec:cc
Nov 25 15:13:39 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPACK(br0) 192.168.8.69 9c:29:76:32:ec:cc DESKTOP-PGUA9K0
Nov 25 15:14:52 DD-WRT daemon.debug ntpclient[9331]: Connecting to 2.pool.ntp.org [209.51.161.238] ...
Nov 25 15:14:52 DD-WRT daemon.info ntpclient[9331]: Time set from 2.pool.ntp.org [209.51.161.238].
Nov 25 15:14:52 DD-WRT daemon.info process_monitor[1837]: Cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
Nov 25 15:14:52 DD-WRT daemon.info process_monitor[1837]: Local timer delta is 0
Nov 25 15:15:29 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPREQUEST(br0) 192.168.8.128 24:41:8c:36:77:8e
Nov 25 15:15:29 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPACK(br0) 192.168.8.128 24:41:8c:36:77:8e DX4860
Nov 25 15:33:10 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPREQUEST(br0) 192.168.8.227 46:0e:cc:ca:8e:ff
Nov 25 15:33:10 DD-WRT daemon.info dnsmasq-dhcp[1570]: DHCPACK(br0) 192.168.8.227 46:0e:cc:ca:8e:ff
Nov 25 16:00:44 DD-WRT daemon.info httpd[1273]: [httpd] : Authentication fail


Every time this disconnection and forced re-authentication occurs, there is an error in the syslog stating "br0: received packet on eth1 with own address as source address", which I believe is a NAT feedback loop. Since this error occurs in sync with the disconnections, I am confident this is the error that's causing this issue. This error message occurs more often with "eth2" in place of "eth1", but the same error with both interfaces occur. Looking under the "Networking" tab, I can see that eth1 is the 2.4GHz interface and eth2 is the 5GHz interface.

I have looked through this forum yet found no working solutions. Some people suggested changing the name of the SSID (the SSID is the same for both wireless interfaces), yet it was working fine on older versions of DD-WRT so I don't see how it could be the culprit; and it is most favorable for my setup to have both interfaces under one SSID.

Does anyone know how I could fix this? Thanks in advance!
Sponsor
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6410
Location: UK, London, just across the river..

PostPosted: Fri Nov 25, 2022 23:23    Post subject: Reply with quote
"I don't see how it could be the culprit; and it is most favourable for my setup to have both interfaces under one SSID. "

not very bright and good idea, try to rename those...
post a pic of advanced wi fi settings, ack time must be 900 or 1350 for better results..

i dont see any disconnection in this log all seams normal apart of this ...

br0: received packet on eth1 with own address as source address

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
NM6636
DD-WRT Novice


Joined: 19 Nov 2022
Posts: 3

PostPosted: Fri Nov 25, 2022 23:52    Post subject: Reply with quote
Alright, I'll try separating the SSIDs when there is a good time to do so (multiple people share this network).
Here are my advanced wireless settings:
2.4GHz:


5GHz:
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1899

PostPosted: Sat Nov 26, 2022 2:00    Post subject: Reply with quote
Start here, but don't get configurations confused as the sticky and wiki are a mess:

BCM Best Wifi Settings

You may have to go back several revisions in wiki history to get a clearer picture in relation to Broadcom.

_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
L30Z3N
DD-WRT Novice


Joined: 15 Oct 2020
Posts: 10

PostPosted: Wed Nov 30, 2022 12:56    Post subject: Reply with quote
It's happening something similar to my R7000 a few months ago. I lost internet connection from all devices without Wi-Fi disconnections. Olders version didn't have this issue. I'm now on Firmware: DD-WRT v3.0-r50671 std (10/26/22).
NM6636
DD-WRT Novice


Joined: 19 Nov 2022
Posts: 3

PostPosted: Sat Dec 03, 2022 15:56    Post subject: Reply with quote
Sorry for the late reply, I've been extremely busy lately.

I changed the name of the 2.4GHz and 5.GHz WiFi networks and the wireless disconnection ceased. The error with eth1/eth2 receiving a packet with itself as the source address still shows up in the syslog for some reason. Thanks!
Display posts from previous:    Page 1 of 1
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