Intermittent loss of Wi-Fi since upgrading to 386.7

[Lord_Vader]

I have flashed my AX86U with stock Asuswrt 49447. Let’s see how it goes.

Please let us know.

 

[Treadler]

Have seen this here, during which, router LED’s that I have set to ‘off’ manually using the switch on the router, would switch on, as if by magic.


The router didn’t reboot so far as I could see, but wifi was interrupted for a brief time.

What I did:
Set ‘format JFFS at next reboot’ = yes. Apply, then reboot.
Restore JFFS from back up.
So far, 55 hours uninterrupted wifi. Still watching…….

I spoke too soon. Managed another couple of hours then LEDS came on, wifi disconnected.

 

[alan6854321]

I spoke too soon. Managed another couple of hours then LEDS came on, wifi disconnected.

Did your router reboot itself (what's the current uptime)?

If so, you might be suffering from the problem I mentioned in post #33 above.

The reboot in these cases seem to be much faster than usual, the WiFi returns in less than one minute, so unless you're looking out for it you might not even realize there's been a reboot.

 

[Treadler]

Did your router reboot itself (what's the current uptime)?

If so, you might be suffering from the problem I mentioned in post #33 above.

The reboot in these cases seem to be much faster than usual, the WiFi returns in less than one minute, so unless you're looking out for it you might not even realize there's been a reboot.

No, definitely no reboot. Uptime 2+ days.

Wireless clients are all showing a time connected of only a few minutes, despite all remaining present & accounted for.

Interesting, the many lines (100’s?) in syslog recording the glitch began with the message “FW Trap has happened”.

Aside from the periodic wifi disconnects, the firmware works just fine. Go figure…..

 

[Unetwork]

I agree with Makaveli's comment for the AX88U.
On my side, still nothing to report since more than 10 days.
No reboot of the router or cut of the Wifi in 2,4 Ghz or 5 Ghz.

 

[Makaveli]

To follow up from my previous post.

I've had no router reboots and no WAN connection issues.

I posted my devices on 2.4 which has been solid no drops there now here is 5Ghz.

The device starting with the 56: is my Galaxy S10 cell phone which goes on and off the network as I leave the house.

The device starting with 50: is my work laptop which pretty much stays stationary until I'm in office Tue and Wed I work from home the rest of the week.

now that the week has started I will be on the work laptop alot more so will monitor it for connection drops but I haven't noticed anything so far while working in the last 10 days.

Here is info from wlceventd.log yesterday and this morning

Jul  3 02:44:46 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 56:A6:DC:1F:79:91, status: Successful (0)
Jul  3 04:12:08 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Unspecified reason (1)
Jul  3 04:12:08 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 04:12:08 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 04:12:11 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9)
Jul  3 04:12:11 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 50:E0:85:DB:5A:6A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  3 04:12:12 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 04:12:12 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 11:14:23 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 56:A6:DC:1F:79:91, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 11:14:23 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 56:A6:DC:1F:79:91, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 11:14:24 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  3 11:35:37 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 56:A6:DC:1F:79:91, status: Successful (0)
Jul  3 11:35:37 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 56:A6:DC:1F:79:91, status: Successful (0)
Jul  3 14:33:15 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Unspecified reason (1)
Jul  3 14:33:15 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 14:33:15 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 14:33:16 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Previous authentication no longer valid (2)
Jul  3 14:33:16 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 14:33:16 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 14:33:17 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Previous authentication no longer valid (2)
Jul  3 14:33:17 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(505): eth7: Auth 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 14:33:17 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 14:33:18 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 50:E0:85:DB:5A:6A, status: 0, reason: Previous authentication no longer valid (2)
Jul  3 14:33:26 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 50:E0:85:DB:5A:6A, status: Successful (0)
Jul  3 14:47:08 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  3 14:47:08 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  3 14:47:10 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 56:A6:DC:1F:79:91, status: Successful (0)
Jul  3 17:30:53 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 56:A6:DC:1F:79:91, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 17:30:53 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 56:A6:DC:1F:79:91, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul  3 17:30:54 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  3 20:15:01 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 56:A6:DC:1F:79:91, status: Successful (0)
Jul  4 08:15:02 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  4 08:15:02 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 56:A6:DC:1F:79:91, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul  4 08:15:04 RT-AX88U-0B10 wlceventd: wlceventd_proc_event(534): eth7: Assoc 56:A6:DC:1F:79:91, status: Successful (0)

 

[Tech9]

Please let us know.

I switched a few times between Asuswrt and Asuswrt-Merlin already. Asuswrt has more stable connection to AiMesh nodes, media bridges and repeaters. In your case with so many routers in AiMesh, the best firmware is stock Asuswrt on all. Asuswrt-Merlin on main and stock Asuswrt on nodes is an option, with wired node discovery during the setup. Then you pray nothing gets disconnected because you have to carry routers around again. If all your nodes are wired to the main router, stay with Asuswrt-Merlin on it. Wired AiMesh has no issues.

For some reason Wi-Fi in Asuswrt 46061 (or Asuswrt-Merlin 386.5_2) works more consistently than in Asuswrt 49447 (or Asuswrt-Merlin 386.7). The wireless drivers are different. I have described the differences I see here:

Release - Asuswrt-Merlin 386.7 is now available for all models

My initial setup was running only the RT-AX86U that replaced my pair of AC86U units. No Smart Connect but same SSID on both bands and Roam Assist turned on on both bands. It was a couple of my 2.4g IoT devices that kept dropping of and reconnecting while running 386.7 I decided to add one of my...

www.snbforums.com

Everyone has a different Wi-Fi environment though and has to test what works best. The above is what I see in my Wi-Fi environment.

 

[Tech9]

Asuswrt has more stable connection to AiMesh nodes, media bridges and repeaters.

To make it more clear - AX86U in stand alone configuration works well on both Asuswrt 49447 and Asuswrt-Merlin 386.7 firmware. When first time upgrading 46061->49447 or 386.5_2->386.7 do factory reset + initialize and configure from scratch. There are more changes under the hood this time.

 

[Unetwork]

Makaveli, same observation here since 10 days with the 386.7 version.
I use every day during my 8 hours of work a laptop connected in wifi 5 Ghz and no interruption to report.
Everything is very stable.

 

[Akki]

I've just had another short interruption to Wi-Fi on my RT-AX88U. I've saved the system log, but there's so many entries that I can't tell if there is anything in there that might give a clue as to what was happening when the Wi-Fi went down.

Hi guys,

I am experiencing exact same as @ but with my GT-AC53000.
Initially, I dirty flashed, and Wi-Fi disconnects were very frequent.
I then did factory resets and now Wi-Fi drops like 5-6 times per day - and that only for couple of seconds

 

[eibgrad]

Some of you guys need to be more specific when you say WiFi drops. 2.4GH, 5GHz, or both? It matters. Having both drop could be the router rebooting. If it's only 5GHz, it could be the use of DFS channels.

At least in the US, the router is required by the FCC to drop its low priority usage of the DFS channels in favor of any higher priority usage, such as airports, weather stations, etc. As soon as your router detects interference, it drops the connection in order to find another channel. That can lead to unreliable WiFi.

Even old 2.4GHz wireless handsets and microwave ovens have been known to kill 2.4GHz WiFi.

But if everyone just keeps telling us their WiFi is unstable, w/ few specifics, it's hard to tell if this is just normal interference, or something else. I just have a feeling that NOT everyone is experiencing the same problems for the same reasons. I suspect we're getting a wide mix, that also includes normal wireless outages as described above.

Now granted, I understand different firmware is behaving differently, but I don't know just how precisely the configurations are matched. Heck, the wireless drivers could be different and result in different channels when set to Auto.

 

[Treadler]

Some of you guys need to be more specific when you say WiFi drops. 2.4GH, 5GHz, or both? It matters. Having both drop could be the router rebooting. If it's only 5GHz, it could be the use of DFS channels.

At least in the US, the router is required by the FCC to drop its low priority usage of the DFS channels in favor of any higher priority usage, such as airports, weather stations, etc. As soon as your router detects interference, it drops the connection in order to find another channel. That can lead to unreliable WiFi.

Even old 2.4GHz wireless handsets and microwave ovens have been known to kill 2.4GHz WiFi.

But if everyone just keeps telling us their WiFi is unstable, w/ few specifics, it's hard to tell if this is just normal interference, or something else. I just have a feeling that NOT everyone is experiencing the same problems for the same reasons. I suspect we're getting a wide mix, that also includes normal wireless outages as described above.

Now granted, I understand different firmware is behaving differently, but I don't know just how precisely the configurations are matched. Heck, the wireless drivers could be different and result in different channels when set to Auto.

Not using DFS. Have checked, router not rebooting, just a wifi off/on, so short as to be hardly noticeable. Log goes absolutely crazy though, sometimes for up to 7 minutes!

The router will happily function for about 2 1/2 days between occurrences here.
Im thinking the time has come for me to stop being lazy, & do a full reset?
(I did a dirty upgrade).

I shall report back in 2 - 3 days…….

 

[Tech9]

But if everyone just keeps telling us their WiFi is unstable, w/ few specifics, it's hard to tell if this is just normal interference, or something else.

Yes, but don't expect everyone to know how Wi-Fi works. Even if you ask for specific details, you may not get the right answer. Most users are interested if Wi-Fi does work or it doesn't. Most users don't have spare routers to do time-consuming testing. Upgrade - issues, roll back - good. Wife pressure, work/learn from home... it's complicated. I can play all day with my Asus routers (perhaps you too), but I (we) don't disrupt anything.

 

[Lord_Vader]

I switched a few times between Asuswrt and Asuswrt-Merlin already. Asuswrt has more stable connection to AiMesh nodes, media bridges and repeaters. In your case with so many routers in AiMesh, the best firmware is stock Asuswrt on all. Asuswrt-Merlin on main and stock Asuswrt on nodes is an option, with wired node discovery during the setup. Then you pray nothing gets disconnected because you have to carry routers around again. If all your nodes are wired to the main router, stay with Asuswrt-Merlin on it. Wired AiMesh has no issues.

For some reason Wi-Fi in Asuswrt 46061 (or Asuswrt-Merlin 386.5_2) works more consistently than in Asuswrt 49447 (or Asuswrt-Merlin 386.7). The wireless drivers are different. I have described the differences I see here:

Release - Asuswrt-Merlin 386.7 is now available for all models

My initial setup was running only the RT-AX86U that replaced my pair of AC86U units. No Smart Connect but same SSID on both bands and Roam Assist turned on on both bands. It was a couple of my 2.4g IoT devices that kept dropping of and reconnecting while running 386.7 I decided to add one of my...

www.snbforums.com

Everyone has a different Wi-Fi environment though and has to test what works best. The above is what I see in my Wi-Fi environment.

3 out of 4 nodes conncted wired, 1 AX-92U wireless. Running stock on all nodes

I can confirm REVERTING to 386.5_2 SOLVED WiFi & WAN issue. No drop-outs for 24 hours!

Did a nuke reset again after flashing old firmware, and reloaded old settings from a config file I had runnin 386.5_2.

Seems to be some sort of WiFi drivers issue as you describe..?

 

[Unetwork]

(AX88U) For your information, I leave the 2.4 Ghz and 5 Ghz Wifi settings by default and the channels on AUTO. No exotic settings. As I said yesterday, no problem to report for 11 days now.
My work computer in 5 Ghz Wifi never has any interruption.
I am very satisfied with the 386.7 version.

 

[Lord_Vader]

Yes, when I updated to 386.7 I left every setting as stock, but without success. Might be that there are some internal differences between AX88 and AX68.

 

[Treadler]

(AX88U) For your information, I leave the 2.4 Ghz and 5 Ghz Wifi settings by default and the channels on AUTO. No exotic settings. As I said yesterday, no problem to report for 11 days now.
My work computer in 5 Ghz Wifi never has any interruption.
I am very satisfied with the 386.7 version.

AX88U, did the full reset today. 386.7.
After reset, had two wifi disconnects in the first hour, so, even worse than after I did the initial ‘dirty’ upgrade - sigh…….
I‘m much encouraged by your experience though. As I’m running a few amtm scripts, I’ll see if one/any of those is what’s giving me the issue.
Experimentation continuing.

 

[Unetwork]

AX88U, did the full reset today. 386.7.
After reset, had two wifi disconnects in the first hour, so, even worse than after I did the initial ‘dirty’ upgrade - sigh…….
I‘m much encouraged by your experience though. As I’m running a few amtm scripts, I’ll see if one/any of those is what’s giving me the issue.
Experimentation continuing.

With my AX88U, I have no Scripts, all options are almost default and as I said before, nothing to report on the LAN/WAN/WIFI/VPN.
I flashed the 386.7 version from the 386_5.2 then did a WPS reset + formatting of the JFFS partition + reboot (I insist on this point to avoid any problem) I then manually reconfigured all my settings (without importing a backup) and did a last reboot to apply.
Here is a screen from my work laptop that has been connected in 5 Ghz (auto channel, everything by default) since 07H00 today without any problem.
I turn the computer on early in the morning and turn it off at night when work is done. I have been doing this for over 11 days now and no interruptions.
I also have android smartphones that connect and stay connected for more than 3 hours (when I watch youtube) without any problem.

Solid as a rock.

 

[lindros2]

Take a look at this thread .....

Sporadic GT-AXE11000 reboots due to kernel panic

I bought GT-AXE11000 last spring and at some moment looking at the uptime noticed it gets rebooted from time to time once 3-4 weeks. Nothing helpful were in native logs, so I did establish remote logging and was able to receive things like this each time it got rebooted...

www.snbforums.com

This says it all: "Pretty much tired of arguing with support trying to persuade them anything at this point. The last resort I had - was scheduling everyday reboot, which seems increases the odds of router to "survive" to the end of the day."

Sounds similar to my AX11000 woes... replaced May 2022.
(except mine didn't kernel panic; it lost connection when the main router had a power outage or Wi-Fi channel changed - and it only started doing that after 16-18 months, right around 386.5 upgrade)

 

[TheLyppardMan]

3 out of 4 nodes conncted wired, 1 AX-92U wireless. Running stock on all nodes

I can confirm REVERTING to 386.5_2 SOLVED WiFi & WAN issue. No drop-outs for 24 hours!

Did a nuke reset again after flashing old firmware, and reloaded old settings from a config file I had runnin 386.5_2.

Seems to be some sort of WiFi drivers issue as you describe..?

After the continuing random dropout problems after 2x clean installs of 386.7_0, I have done a dirty downgrade to 386.5_2 and so far, there have not been any interruptions (tempting fate by saying that I know). Here's the current uptime without any issues:-