Firmware 386.4 Issues - Unable to add AiMesh Node over ethernet

[L&LD]

It may be faster to just use a different control channel, reboot, and test.

 

[Tech9]

Nope, problem is back again.

You may have better luck if you break AiMesh and use Router + AP configuration. It works always, it's more stable and you have more control over the AP, including different channels and tx power. After recent reported issues with AX68U routers I would say don't get another one. Read around, the threads are pages long. If you like Asuswrt-Merlin, use an Asus router as router and build a proper SMB AP's Wi-Fi system.

both routers have 386.4. I would never let them live on different versions

Both routers are different hardware with different software. 386.4 in AC68U is not the same as 386.4 on AX68U. By the way, I wouldn't use 386.4 firmware. I wouldn't use Asuswrt-Merlin on the node as well. If you want more stable AiMesh, use stock Asuswrt. Read the very long thread about AC68U issues when used in AiMesh with Asuswrt-Merlin. Something is wrong there, because it works well with the same base Asuswrt.

But as i wrote - before 386.4 problem was not present.

I stopped testing 386.4 on AC86U somewhere in the middle of the release thread because the router wasn't stable. First time with Asuswrt-Merlin. Wait for 386.5 release or revert to 386.3_2. The previous Asuswrt-Merlin works well, some folks did >100 days uptime, including AiMesh configurations. This may be your possible solution, instead of wasting your time with troubleshooting unknown issues. Test and see what works for you.

 

[pirx73]

@Tech9 @L&LD first of all - thank you both a lot for your help and meaningful advice!
[mini-rant]
unlike this response:

386.5 Alpha1?

You're talking about the second Alpha release in the above? That was the first drop of RT-AX88U Alpha. Upgrading the RT-AX86U AP now with the new Alpha 1.... EDIT: And filthy upgrade of the RT-AX86U AP is done. All good so far. Time for a coffee...

www.snbforums.com

where person just spouts copypaste WiFi basics and acts patronizing without providing even a single bit of meaningful insight to solve the issue!
This is waste of time and does not help to solve the issue in any way.
As does Universal Solution to Life Universe and Everything so loved in this forum - Holy Reset to Factory Defaults.
If i would tell that to my customers every time they had issues with their wireless networks our company would ran out of customers really fast.
You need to find the issue and solve it without doing "format c:" every fracking time you have an issue.
Only time when you would perform such reset in enterprise world would be an upgrade from ver 1.0 to 10.0 which in many cases requires several steps and careful planning.
[/mini-rant]
[coming_out]
As a former WiFi engineer (and former CCNA Wireless) who designed, configured and surveyed wireless networks for several years i believe i still remember WiFi basics pretty well.
I designed WiFi networks for small condos (2-3 APs), schools (10+ APs), hospitals (20-30 APs) and universities (30-40 APs) ending with National Library of my country having 60 (later 120) APs.
Configured and surveyed many networks. Too bad my country is too small to work as wireless engineer alone and i had to leave.
[/coming_out]

You may have better luck if you break AiMesh and use Router + AP configuration. It works always

Thanks! I was actually thinking about this config when i first bought AX68, but i decided to give AiMesh a try.
To my defense i can say that network ran rock-stable on 386.3_2 since August. I never had any issues.
Currently due to my medical condition i can't go to the second floor and reset AC68 so i went for easiest solution - reverted to the 386.3_2 as you suggested.
I will monitor the net to see how it behaves now but switching AC68 to AP mode is on the todo list as soon as i get back on my feet (literally).

After recent reported issues with AX68U routers I would say don't get another one.

You scared me here. I honestly did not had any issues with AX68 except for this AiMesh one and even that only with 386.4.
I don't see many options for myself besides AX68 because if i would want to shell out 400+€ for the AP i would go for enterprise-level one.
Don't need 500€ router which looks like upside-down spider. Do you have any suggestions for a sensible AX68 replacement? RT-AX92U perhaps?
Ha, found they are being sold in 2-packs:

Wireless

www.dateks.lv

 

[Tech9]

As does Universal Solution to Life Universe and Everything so loved in this forum - Holy Reset to Factory Defaults.

Indeed. You got served the links already.

Do you have any suggestions for a sensible AX68 replacement?

No. I have wasted quite a bit of time testing AiMesh in different configurations with different routers and firmwares and I would not invest money in this. If you are happy with AX68U, perhaps another is the best AiMesh way. Otherwise go with proven SMB solutions. It doesn't have to be enterprise level, good AX AP's are available under $200. The issue with Asus as router is no VLAN's support and your network configuration options will be limited. AX92U is older model "3-band" router initially intended to be AC system with AX wireless backhaul. Later firmware versions allow AX clients. No Asuswrt-Merlin support.

 

[hancox]

@pirx73 Seriously, try to non-merlin stock for the AX68, or merlin 385 alpha. I have an AX68 which was dropping 5GhZ randomly without warning, and it stabilized on newer firmware cuts.

 

[pirx73]

@hancox thanks, but i will stay on 386.3_2 until 386.5 is fully released, i can't afford to play arround with alpha versions when we work from home and stable network is a must.

 

[hancox]

@hancox thanks, but i will stay on 386.3_2 until 386.5 is fully released, i can't afford to play arround with alpha versions when we work from home and stable network is a must.

Completely understand. In your situation, i would consider the newer stock firmware, unless merlin gives you something mission-critical.

 

[pirx73]

@Tech9 happy to report that i switched AC68U over to AP mode. No issues so far.

 

[pirx73]

@Tech9 alas, i spoke too soon...

Once i upgraded AX68 to 386.5_2 problems begun again.
AC stayed on ASUS own firmware.
Trying to isolate problem i removed AC68 from the setup so AX68 was only wifi router.
I also tried AC68 as AP node, as AIMESH node with ASUS own software etc...
With 386.3_2 it was fine. And very moment i moved AX68 back to 386.5_2 problems reappeared.
Laptops begun disconnecting again, but then i caugth this in the log very moment disconnect happen:

May  6 13:36:11 kernel: wl1: PSM microcode watchdog fired at 314485 (seconds). Resetting.
May  6 13:36:11 kernel: wl1: reason = psm watchdog at 314485 seconds. corerev 131 ucode revision 1626.28204 features 0x3106
May  6 13:36:11 kernel: psmdebug 0x00000024 pc 0x01ff000e phydebug 0x41 macctl 0x4160403 maccmd 0x4
May  6 13:36:11 kernel: psm_brc 0xa000 psm_brc_1 0x0018 M_UCODE_DBGST 0x2
May  6 13:36:11 kernel: brwk_0 0x2401 brwk_1 0x0014 brwk_2 0x22a0 brwk_3 0x0ff2 brwk_4 0x0006
May  6 13:36:11 kernel: ifsstat      0xaf   ifsstat1     0xff   txectl       0x481c txestat      0x405
May  6 13:36:11 kernel: rxestat1     0x4104 rxestat2     0x1340 rcv_frmcnt   0x0    rxe_rxcnt    0x91  
May  6 13:36:11 kernel: wepctl       0x0  
May  6 13:36:11 kernel: aqmf_ready0  0x0    aqmf_ready1  0x2    aqmf_ready2  0x0    aqmf_ready3  0x0  
May  6 13:36:11 kernel: aqmf_ready4  0x0    wepstat      0x8000 wep_ivloc    0x1a   wep_psdulen  0x35  
May  6 13:36:11 kernel: rxe_errval   0x0    rxe_errmask  0x20f  rxe_status3  0x20a  txe_status2  0x405
May  6 13:36:11 kernel: dbg_bmc_status 0x0    psm_chk0_err 0x0    psm_chk1_err 0x0  
May  6 13:36:11 kernel: PC :
May  6 13:36:11 kernel: R0: 0x24       0x24       0x24       0x24    
May  6 13:36:11 kernel: phydebug :
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: 0x21       0x21       0x21       0x21    
May  6 13:36:11 kernel: 0x1        0x1        0x1        0x1      
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: 0x0        0x0        0x0        0x0      
May  6 13:36:11 kernel: pktproc      0x101  pktproc      0x101  pktproc      0x101  pktproc      0x101
May  6 13:36:11 kernel: TxFifoStatus0 0x1c3  TxFifoStatus1 0x1c3
May  6 13:36:11 kernel: gpiosel      0x0    gpiolo       0x0    gpiohi       0x0  
May  6 13:36:11 kernel: gpiosel      0x1    gpiolo       0x0    gpiohi       0x0  
May  6 13:36:11 kernel: psm stack_status : 0x8000
May  6 13:36:11 kernel: psm stack_entries:
May  6 13:36:11 kernel: 0x0024
May  6 13:36:11 kernel: 0x02ac
May  6 13:36:11 kernel: 0x01dc
May  6 13:36:11 kernel: 0x0683
May  6 13:36:11 kernel: 0x00b6
May  6 13:36:11 kernel: 0x121e
May  6 13:36:11 kernel: 0x3e7d
May  6 13:36:11 kernel: 0x3123
May  6 13:36:11 kernel: 0) usr_count = 0, schedid = 0
May  6 13:36:11 kernel: 1) usr_count = 0, schedid = 0
May  6 13:36:11 kernel: 2) usr_count = 0, schedid = 0
May  6 13:36:11 kernel: 3) usr_count = 0, schedid = 0
May  6 13:36:11 kernel: wl1: fatal error, reinitializing, total count of reinit's[2]
May  6 13:36:11 kernel: CSIMON:  CSIMON[1.1.0] Initialization
May  6 13:36:11 kernel: CSIMON: M2M usr already registered ...
May  6 13:36:17 kernel: httpds (12069): drop_caches: 1

Two things caught my eye:
kernel: wl1: PSM microcode watchdog fired at 314485 (seconds). Resetting.
kernel: wl1: fatal error, reinitializing, total count of reinit's[2]

So it seems my wife's laptop's Intel AX200 card is causing this. And best of all - i have no ability to fix this.
You might say - upgrade driver, see does it help. Yes, AX200 driver on her laptop is 03.03.2021 so year old.
But i have no ability to upgrade it. My wife does not have admin rights on it whatsoever and her government institution
sysadmins ... i won't be able to persuade them to help with this issue, because their concern is office where "everything works" instead of our home.
So i reverted AX68 back to 386.3_2 again and left there. Maybe i will try with 386.7 when Merlin releases it.
Another solution i found is to disable "802.11ax / Wi-Fi 6 mode" on 5GHz band, it also seems to help.
Or i could just plug in her laptop via cable. That i can also do.