RT-AC68U client WiFi loss after some time

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sat Jul 23, 2022 9:18    Post subject: Reply with quote
There is no experimental driver for the RT-AC68U, just whatever it is offered.

Since this is Broadcom the following is available.



Capture.PNG
 Description:
 Filesize:  11.28 KB
 Viewed:  1856 Time(s)

Capture.PNG



_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
Sponsor
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Sat Jul 23, 2022 9:24    Post subject: Reply with quote
please show what is displayed for channels 36 or 100
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Sat Jul 23, 2022 11:58    Post subject: Reply with quote
I take the silence as confirmation.
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sat Jul 23, 2022 12:24    Post subject: Reply with quote
channels 36/100 are visible only when LL

and other channels are visible depending on UL, LU, UU, LL obviously

Im guessing this a Regulatory Domain restrictions.

Anyway, my channels are selected specifically, in relation what neighboring Wireless channels are in use + not overlap with those channels in the neighboring wireless spectrum, So there is no interference.

Another thing that occurs to me, is some individuals may force disconnects on other network clients, for instance if your shit in interfering with theirs and they are motivated enough to send you a message, or another reason to force clients on other networks to disconnect, could also be viewed as a sign of active penetration attempts.

I use https://vremsoftwaredevelopment.github.io/WiFiAnalyzer/ its does its job doesn't collect data/analytics/telemetry and is opensource and best yet, free, its not been actively developed of late, and Im guessing it suffers from the opensource man issue, lack of contributors/developers.



Capture.PNG
 Description:
 Filesize:  6.43 KB
 Viewed:  1800 Time(s)

Capture.PNG



Capture.PNG
 Description:
 Filesize:  6.76 KB
 Viewed:  1807 Time(s)

Capture.PNG



_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)


Last edited by the-joker on Sat Jul 23, 2022 12:44; edited 2 times in total
ho1Aetoo
DD-WRT Guru


Joined: 19 Feb 2019
Posts: 2927
Location: Germany

PostPosted: Sat Jul 23, 2022 12:38    Post subject: Reply with quote
Yes, if 36 and 100 are only visible when LL is selected then the extension channels are swapped.

36 and 100 are actually UU only

see: https://wiki.dd-wrt.com/wiki/index.php/Basic_Wireless_Settings#Wireless_Channel

Quote:
!!!For BCM routers, you need to swap UU, UL, LU, and LL meanings (Not sure if this is a BCM issue or how BS coded the tables in the code)!!!

FOR BCM-confirmed that in the table below you need to swap:

UU- Select LL in gui
UL- Select LU in gui
LU- Select UL in gui
LL-Select UU in gui


that means if the OP has selected "52 LL" then this is the correct setting for his Broadcom router.

On all other devices "52 UU" would be the correct setting.
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sat Jul 23, 2022 12:46    Post subject: Reply with quote
Broadcom, what else is there to be said about that.

Anyway, the op has plenty good information to work for on his Broadcom, same as mine coincidentally. And he also has suggestions of tools in order to pick better channels, and perhaps stop annoying his neighbors. Im guessing this is whats happening in part its a guess only since we lack the right information to make educated factual claims.

_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
xaoslaad
DD-WRT Novice


Joined: 09 Jul 2022
Posts: 13

PostPosted: Sat Jul 23, 2022 14:53    Post subject: Reply with quote
ho1Aetoo wrote:
I take the silence as confirmation.


Sleeping... it was 2 AM when I was done looking last night. My silence means I was exhausted.

It's run for 9+ hours, in a few minutes it will be 10 hours without problems rekeying on 49326.

I can look at making the change(s) you suggested and bringing it back up to date. I can also try updating to r49361 as I suggested. What has changed that a few revs back no issue, and now there is?
xaoslaad
DD-WRT Novice


Joined: 09 Jul 2022
Posts: 13

PostPosted: Sat Jul 23, 2022 15:15    Post subject: Reply with quote
the-joker wrote:
Broadcom, what else is there to be said about that.

Anyway, the op has plenty good information to work for on his Broadcom, same as mine coincidentally. And he also has suggestions of tools in order to pick better channels, and perhaps stop annoying his neighbors. Im guessing this is whats happening in part its a guess only since we lack the right information to make educated factual claims.


I can back down to r49326, maybe r49361, of dd-wrt and it works, or use an alternate firmware like tomato, and it works. Or I can update to 49392+ and it doesn't.

I'm not clear what information I haven't given you that you want that's in my power to give? I don't have a serial cable to hook up. If that's what it takes to you to prove something is wrong I'm willing to buy one and go through the effoty.

I can try updating the few settings for 5G where I am definitely seeing the problem that have been suggested, but as far as I'm understanding you the channel and extension channel are correct.

This chart, say 52 UU should be 52LL in the GUI for broadcom. https://wiki.dd-wrt.com/wiki/index.php/Basic_Wireless_Settings#Wireless_Channel
the-joker
DD-WRT Developer/Maintainer


Joined: 31 Jul 2021
Posts: 2146
Location: All over YOUR webs

PostPosted: Sat Jul 23, 2022 16:34    Post subject: Reply with quote
I think theres a misunderstanding somewhere.

I posited as a guess that perhaps some neighbor was purposefully knocking your client off, read my previous two posts before this one. But we cannot prove that because there is no information to either prove or disprove my guess.

In any case, I cannot duplicate your issues, my channels and setup allow to put myself away from any neighbor interference by a really long shot, Im always at latest builds and often quite ahead as I test dev builds due to my contributions to UI Im currently at https://svn.dd-wrt.com/changeset/49547 and shortly will be at https://svn.dd-wrt.com/changeset/49557

I also flash builds daily so perhaps I dont notice anything since after flashing I have to reboot and My wifi clients are not on 24/7

Im not dismissing your claims that previous builds work better, but there are no changes from those builds to current driver wise afaik for the RT-AC68U. Broadcom drivers are closed source and fixing them is not a developers wet dream I assure you, so often these are unchanged for long periods.

I have also read by other members using that they noticed the wifi throughput as suffered, but again, no drivers were changed, so it must be another component.

https://svn.dd-wrt.com/changeset/49554 already includes Broadcom side the first for a while which may affect our routers so maybe that will improve the issue you face.

Here is my advice in the meanwhile if we cant get to the bottom of the issue. Use the wifi analizer pick a channel thats not crowded or doesn't overlap with the neighbors if at all possible and see how that fairs.

_________________
Saving your retinas from the burn!🔥
DD-WRT Inspired themes for routers
DD-WRT Inspired themes for the phpBB Forum
DD-WRT Inspired themes for the SVN Trac & FTP site
Join in for a chat @ #style_it_themes_public:matrix.org or #style_it_themes:discord

DD-WRT UI Themes Bug Reporting and Discussion thread

Router: ANus RT-AC68U E1 (recognized as C1)
xaoslaad
DD-WRT Novice


Joined: 09 Jul 2022
Posts: 13

PostPosted: Sun Jul 24, 2022 3:06    Post subject: Reply with quote
49361 was the last good version. My neighbor is _really_ good if he can figure out when I'm upgrading my router and cause my clients to bounce on the hour when they should rekey.

I'll wait roll back to 49361 and wait for 49547 and 49557 to land in a release and see if they improve things. If not I guess I'll look for an alternative for a longer term option.

49326:
Code:

$ sudo journalctl -u wpa_supplicant -n 10 -f | grep -i -e Associated -e Group -e PTK -e reason=16
Jul 23 00:59:46 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: Associated with 04:42:1a:9f:2e:44
Jul 23 00:59:46 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:44 [PTK=CCMP GTK=CCMP]
Jul 23 01:59:45 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 02:59:39 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 03:59:37 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 04:59:36 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 05:59:34 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 06:59:33 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 07:59:32 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 08:59:26 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 09:59:23 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 10:59:21 pixelbook.home.lan wpa_supplicant[964]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]


49361:
Code:

$ sudo journalctl -u wpa_supplicant -n 10 -f | grep -i -e Associated -e Group -e PTK -e reason=16
Jul 23 11:46:07 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:44
Jul 23 11:46:07 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:44 [PTK=CCMP GTK=CCMP]
Jul 23 12:32:13 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 13:32:09 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 14:32:06 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 15:31:54 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 16:31:48 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 17:31:40 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 18:31:38 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 19:31:35 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]
Jul 23 20:31:34 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Group rekeying completed with 04:42:1a:9f:2e:44 [GTK=CCMP]


49392:
Code:

$ sudo journalctl -u wpa_supplicant -n 10 -f | grep -i -e Associated -e Group -e PTK -e reason=16
Jul 23 20:56:38 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:44
Jul 23 20:56:39 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:44 [PTK=CCMP GTK=CCMP]
Jul 23 21:56:36 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:9f:2e:44 reason=16
Jul 23 21:56:37 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:32
Jul 23 21:56:37 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:32 [PTK=CCMP GTK=CCMP]


49544:
Code:

$ sudo journalctl -u wpa_supplicant -n 10 -f | grep -i -e Associated -e Group -e PTK -e reason=16
Jul 23 22:00:11 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:44
Jul 23 22:00:11 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:44 [PTK=CCMP GTK=CCMP]
Jul 23 23:00:15 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:9f:2e:44 reason=16
Jul 23 23:00:18 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:32
Jul 23 23:00:18 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:32 [PTK=CCMP GTK=CCMP]
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Sun Jul 24, 2022 3:21    Post subject: Reply with quote
All I see is normal log entries from your Fedora client. This was a waste of time. I could see if you lost internet connectivity for 5 minutes or something blatantly obvious that it hung up.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
xaoslaad
DD-WRT Novice


Joined: 09 Jul 2022
Posts: 13

PostPosted: Sun Jul 24, 2022 3:29    Post subject: Reply with quote
reason 16 is group key handshake timeout.

It's not normal. It's failing to rekey. And specifically with anything after 49361. You are being purposefully obtuse.

"[40457.929636] wlp1s0: deauthenticated from 04:42:1a:9f:2e:44 (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT)"

And it is causing disruptions. I often lose internet and get prompted to reconnect. It's a 50/50 crapshoot whether it roams to the other AP or just disconnects. It's not normal behavior. It was rock solid stable until updating beyond that release. I didn't come here and report it because I saw some logs. I started watching the logs because I was getting disconnected.

Instead I have theories about my neighbor and sasquatch when I'm plainly showing logs that rekeying is failing beyond a 49361.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Sun Jul 24, 2022 4:42    Post subject: Reply with quote
The post above my previous comment does not contain that log entry whatsoever, which is what I was commenting on and your previous post shows that it is re-keying. You are referring back to the OP of this thread and we have no idea if you took any advice on adjusting your wifi settings. Posting partial logs creates a breakdown in communication. Quite frankly, it seems as if you want to argue and not provide verification and proof of any configuration changes to you router or client or full logs from the router and client of the issue.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
xaoslaad
DD-WRT Novice


Joined: 09 Jul 2022
Posts: 13

PostPosted: Sun Jul 24, 2022 4:55    Post subject: Reply with quote
kernel-panic69 wrote:
The post above my previous comment does not contain that log entry whatsoever, which is what I was commenting on and your previous post shows that it is re-keying. You are referring back to the OP of this thread and we have no idea if you took any advice on adjusting your wifi settings. Posting partial logs creates a breakdown in communication. Quite frankly, it seems as if you want to argue and not provide verification and proof of any configuration changes to you router or client or full logs from the router and client of the issue.


It does.
Code:

$ sudo journalctl -u wpa_supplicant -n 10 -f | grep -i -e Associated -e Group -e PTK -e reason=16
Jul 23 22:00:11 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:44
Jul 23 22:00:11 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:44 [PTK=CCMP GTK=CCMP]
Jul 23 23:00:15 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:9f:2e:44 reason=16
Jul 23 23:00:18 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: Associated with 04:42:1a:9f:2e:32
Jul 23 23:00:18 pixelbook.home.lan wpa_supplicant[970]: wlp1s0: WPA: Key negotiation completed with 04:42:1a:9f:2e:32 [PTK=CCMP GTK=CCMP]


See specifically:
Code:

wpa_supplicant[970]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=04:42:1a:9f:2e:44 reason=16


"reason=16". When this is logged in the journal the other is logged in dmesg. I've shared this all in prior comments.

I've shared it happens both with iwd with the same reason code, so it's no specific to wpa_supplicant on the client. I've shared that I've reproduced it on a laptop with an AX201 card and another with a 7265.

This is on the 5G connection. The only thing that was suggested I change there is to change the ACK timing to 1350. I've done that.

I incorrectly set the wpa/wpa2 instead of just wpa2 psk on the 2.4GHz when reconfiguring the router. It's been changed. As has the ack timing there. No change.

Frankly, I doubt if I brought you the laptop and router and showed it in front of you that you'd agree. The modus operandi seems to be to gaslight with conspiracies about hackers attacking my wireless network from my neighbors basement.

I have no more interest in arguing this. I'll flash the stock firmware and find something else to protect my network, provide vpn, dns etc. behind the cable modem. Bug reports and evidence do not seem welcome.

I fully understand the broadcom stuff is closed source and there are limits to what can be done but you won't even acknowledge the existence of a problem.
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6856
Location: Romerike, Norway

PostPosted: Sun Jul 24, 2022 6:49    Post subject: Reply with quote
Wireless->Wireless Security

There is a Key Renewal Interval Option.

Default is 3600.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
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