SR-G
Occasional Visitor
So i have a GT-AX6000.
At first with 3004.388.4 since months, and everything was working fine.
A few weeks ago, i updated it with 3004.388.5.
Then i started to encounter these symptoms on all my wireless devices (android tablets, amazon echo show, amazon echo gen 1, ...) :
- no more internet access for devices connected through wireless (both 2.4GHZ and 5GHZ) (amazon echo saying that no internet access are ok, android tablets being wireless connected but without internet access, and so on)
- but wired devices (RJ45) were still having full internet access and were working fine
After a router reboot, everything was of course working fine again.
I encountered this once per week during the two first weeks, then it started to happen ... like once per day (at random time).
In the end, a couple of days ago (27th), i reverted the firmware to 3004.388.4, and now everything seems stable again (but only since 4-5 days now).
In the logs, i found (after increasing the size of the logs) nothing at all :
- even when the issue was happening, i was surprisingly still seeing some association / disassociation of a few SHELLY devices (the ones powered through batteries, and only reporting informations from time to time)
- at first i saw many errors happening at regular basis and that were (per information found on this forum) related to "ASUSNAT" - so, thinking it may be the culprit, i disabled the corresponding option under Tools > Other settings - but it was not related to this problem in the end, and the problem has still been happening with ASUSNAT disabled
- other than that, nothing special in the logs at any time
For ex. here, i have the problem around 12:20 and i rebooted at 12:25) (for ex., "C0:49:EF:8E:26:CC" is a Shelly humidity and temperature sensor) :
Extra notes :
- "Smart Connect" has never been activated on my side
- on top of Asus Merlin, i only have Diversion + amtm installed, with Pixelserv-tls activated, and nothing else
So now i don't know what to do :
- try again 388.5
- stick on 388.4 until 388.6 is out, in the hope that the problem won't happen again
- stick on 388.4 forevever
- try 388.5 / .6 with a full reset of the router and reconfigure everything manually <-- i'm definitely NOT willing to do that, as it's A LOT of work / as a lot of time is needed to reconfigure everything and as there is 0 guarantee that it will solve the issue anyway
Any ideas ? Anyone had the same issue and has found the culprit ?
At first with 3004.388.4 since months, and everything was working fine.
A few weeks ago, i updated it with 3004.388.5.
Then i started to encounter these symptoms on all my wireless devices (android tablets, amazon echo show, amazon echo gen 1, ...) :
- no more internet access for devices connected through wireless (both 2.4GHZ and 5GHZ) (amazon echo saying that no internet access are ok, android tablets being wireless connected but without internet access, and so on)
- but wired devices (RJ45) were still having full internet access and were working fine
After a router reboot, everything was of course working fine again.
I encountered this once per week during the two first weeks, then it started to happen ... like once per day (at random time).
In the end, a couple of days ago (27th), i reverted the firmware to 3004.388.4, and now everything seems stable again (but only since 4-5 days now).
In the logs, i found (after increasing the size of the logs) nothing at all :
- even when the issue was happening, i was surprisingly still seeing some association / disassociation of a few SHELLY devices (the ones powered through batteries, and only reporting informations from time to time)
- at first i saw many errors happening at regular basis and that were (per information found on this forum) related to "ASUSNAT" - so, thinking it may be the culprit, i disabled the corresponding option under Tools > Other settings - but it was not related to this problem in the end, and the problem has still been happening with ASUSNAT disabled
- other than that, nothing special in the logs at any time
For ex. here, i have the problem around 12:20 and i rebooted at 12:25) (for ex., "C0:49:EF:8E:26:CC" is a Shelly humidity and temperature sensor) :
Dec 27 12:20:12 wlceventd: wlceventd_proc_event(662): eth6: Disassoc C0:49:EF:8E:35:1C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 12:20:12 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind C0:49:EF:8E:35:1C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 27 12:22:35 kernel: CPU: 1 PID: 27859 Comm: dcd Tainted: P O 4.19.183 #1
Dec 27 12:22:35 kernel: Hardware name: GTAX6000_50991 (DT)
Dec 27 12:22:35 kernel: pstate: 200f0010 (nzCv q A32 LE aif)
Dec 27 12:22:35 kernel: pc : 00000000f79539d8
Dec 27 12:22:35 kernel: lr : 0000000080808080
Dec 27 12:22:35 kernel: sp : 00000000ffeab0f0
Dec 27 12:22:35 kernel: x12: 0000000000000000
Dec 27 12:22:35 kernel: x11: 0000000000000000 x10: 000000000007e66c
Dec 27 12:22:35 kernel: x9 : 00000000f67fd008 x8 : 00000000000a387e
Dec 27 12:22:35 kernel: x7 : 0000000000000010 x6 : 0000000000000000
Dec 27 12:22:35 kernel: x5 : 00000000000a3884 x4 : 00000000fefefeff
Dec 27 12:22:35 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Dec 27 12:22:35 kernel: x1 : 0000000000000107 x0 : 0000000000000000
Dec 27 12:22:57 wlceventd: wlceventd_proc_event(685): eth6: Auth C0:49:EF:8E:26:CC, status: Successful (0), rssi:-58
Dec 27 12:22:57 wlceventd: wlceventd_proc_event(722): eth6: Assoc C0:49:EF:8E:26:CC, status: Successful (0), rssi:-58
Dec 27 12:23:12 wlceventd: wlceventd_proc_event(662): eth6: Disassoc C0:49:EF:8E:26:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 12:23:12 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind C0:49:EF:8E:26:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Dec 27 12:24:34 wlceventd: wlceventd_proc_event(685): eth6: Auth 90:78:B2:58:8F:BF, status: Successful (0), rssi:0
Dec 27 12:24:34 wlceventd: wlceventd_proc_event(722): eth6: Assoc 90:78:B2:58:8F:BF, status: Successful (0), rssi:-70
Dec 27 12:25:11 wlceventd: wlceventd_proc_event(685): eth6: Auth C0:49:EF:8E:35:1C, status: Successful (0), rssi:0
Dec 27 12:25:11 wlceventd: wlceventd_proc_event(722): eth6: Assoc C0:49:EF:8E:35:1C, status: Successful (0), rssi:-57
Dec 27 12:25:27 wlceventd: wlceventd_proc_event(662): eth6: Disassoc C0:49:EF:8E:35:1C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 27 12:25:27 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind C0:49:EF:8E:35:1C, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
May 5 07:05:16 kernel: klogd started: BusyBox v1.25.1 (2023-08-21 15:34:18 EDT)
Extra notes :
- "Smart Connect" has never been activated on my side
- on top of Asus Merlin, i only have Diversion + amtm installed, with Pixelserv-tls activated, and nothing else
So now i don't know what to do :
- try again 388.5
- stick on 388.4 until 388.6 is out, in the hope that the problem won't happen again
- stick on 388.4 forevever
- try 388.5 / .6 with a full reset of the router and reconfigure everything manually <-- i'm definitely NOT willing to do that, as it's A LOT of work / as a lot of time is needed to reconfigure everything and as there is 0 guarantee that it will solve the issue anyway
Any ideas ? Anyone had the same issue and has found the culprit ?
Last edited: