Hi Gurus,

Have you tried to connect the AX53u with AX86s/u ? as Media Bridge or Repeater or Node.

I cannot get it to work, it keep showing this error in the logs regardless any of the 3 mode I use:

May 5 13:08:32 kernel: [ 223.414051] Set_Channel_Proc: Channel(161), Cert(0), Quick(0)
May 5 13:08:32 kernel: [ 223.420110] rtmp_set_channel(caller:Set_Channel_Proc+0x170/0x250), Channel(161), quick_ch_change:0.
May 5 13:08:32 kernel: [ 223.429356] APStop() Invalid oper(1)
May 5 13:08:32 kernel: [ 223.432963] APStartUp() Invalid oper(1)
May 5 13:08:32 kernel: [ 223.446859] I/F(apcli1) Set_ApCli_Enable_Proc::(enable = 1)
May 5 13:08:36 kernel: [ 227.374390] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
May 5 13:08:37 kernel: [ 228.464269] ApSiteSurvey_by_wdev::Failed!!!Scan is running, please try again after scan done!
May 5 13:08:38 kernel: [ 229.374368] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(0),AUTH(0),ASSOC(0)
May 5 13:08:40 kernel: [ 231.374358] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
May 5 13:08:41 kernel: [ 232.504197] I/F(apcli1) Set_ApCli_Enable_Proc::(enable = 0)
May 5 13:08:50 kernel: [ 241.693183] Set_Channel_Proc: Channel(161), Cert(0), Quick(0)
May 5 13:08:50 kernel: [ 241.699112] rtmp_set_channel(caller:Set_Channel_Proc+0x170/0x250), Channel(161), quick_ch_change:0.
May 5 13:08:50 kernel: [ 241.708319] APStop() Invalid oper(1)
May 5 13:08:50 kernel: [ 241.711895] APStartUp() Invalid oper(1)
May 5 13:08:50 kernel: [ 241.730609] I/F(apcli1) Set_ApCli_Enable_Proc::(enable = 1)

But it can connect well if I connect to my old AC86u.
I tried disable AX mode on my AX86s , but still same error, I am running out of ideas.

Make sure both AX86S and AX53U is running the latest firmware
Use a WiFi name without space or symbol

Try both of these first

RT-AX82U can support up to 2Gbps?

My current 800mbps can only get about 500mbps wifi-5ghz on iPhone 14 Pro Max

Yes, AX86s is running on Asus Merlin 388.1

AX53u is running on the firmware that just updated on 30-March.

No special charecters on the Wifi Name, in fact the same wifi can be connected by the AX53u to the AC86u. just after switching to AX86s, it stop working.
Is there any features in AX86s that is not supported by AX53u ?

I already switch to 80Mhz and using channel 161.

Regards

Try channel 36 or 44

No luck, same error, just in the log will show the correct channel:

May 5 13:08:50 kernel: [ 241.699112] rtmp_set_channel(caller:Set_Channel_Proc+0x170/0x250), Channel(XX), quick_ch_change:0

"XX" based on the AP channel, but all other error remains the same.

Have you tried the stock firmware just to rule out any issue with Merlin

AC53u (Stock) -> AX86s (Merlin) - Not ok
AC53u (Stock) -> AC86u (Merlin) - ok
AC86u (Merlin) -> AX86s (Merlin) - ok

Don't seems like Merlin issue.

This post has been edited by seanswn: Apr 1 2023, 05:54 PM

There's a bug affecting AiMesh between BCM and MTK AX models previously.

Not sure whether Merlin backported that fix.

388.1 is based on the ancient 388_21224 GPL. Meanwhile, AX86S already received 3 new updates on the official channel.

From what I see on the official firmware release changelog, there are AiMesh related changes on 2 of the updates.

Upgraded to 388.2 beta on Merlin, same issue no change :-(

When will ET12 be sold here? Seems to be taking a long time.

On most scenario, the XT12 will be faster. In fact, I can tell you that the components of XT12 and ET12 are exactly same apart from the 6GHz antennas.

It's only slightly faster if you have a 6GHz capable device and that is subjected to signal strength as well.

The signal of 6GHz is so much weaker than 5GHz so it's kinda counter-intuitive.

Wow interesting. If 6ghz signal is weaker doesn't make sense. But it's WiFi 6e ready, was thinking about future proofing.

But seems prices have gone up, I think previously on lzd I saw the xt12 2x can get for about sub 3k with vouchers etc. Now it's like 4k 🤐

Anyone is using AX56U with Merlin firmware?

I found two odd issue after upgrading to 388.1, and 388.2 Beta.

1. The router has 4 CPU cores, but on the 2 firmware versions above, only 3 cores are utilised, while the 4th core stays idle pretty much all the time.
2. The CPU usage on 388.1 & 388.2 Beta are also a lot higher than on 386.7_2, with the "sysstate" process using up quite a lot of CPU time.

Rolling back to 386.7_2 fixes both of the issues above.

This post has been edited by siaush: Apr 1 2023, 11:37 PM

Yup, the same reason why 5GHz is much weaker than 2.4GHz. As the frequency is higher, the penetrating power is lower and it's exponential.

As for now, the XT12 is capable of providing 800Mbps reliably on the mesh node, it should last me a long long time.

I don't think XT12 (2 pack ) had even gone below RM3k cause I would've sapu more.

@AsusMY - any help ?

Hi seanswn,

We only support stock firmware in this forum topic.

As suggested by blacktubi, have you try both the router in stock firmware? This is because from your testing, the RT-AX86S are still in merlin firmware.

AC53u (Stock) -> AX86s (Merlin) - Not ok
AC53u (Stock) -> AC86u (Merlin) - ok
AC86u (Merlin) -> AX86s (Merlin) - ok

Thank you

May 5 13:07:22 kernel: [ 153.713005] APStop() Invalid oper(1)
May 5 13:07:22 kernel: [ 153.716851] APStartUp() Invalid oper(1)
May 5 13:07:22 kernel: [ 153.731759] I/F(apcli1) Set_ApCli_Enable_Proc::(enable = 1)
May 5 13:07:26 kernel: [ 157.505192] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
May 5 13:07:27 kernel: [ 158.755052] ApSiteSurvey_by_wdev::Failed!!!Scan is running, please try again after scan done!
May 5 13:07:28 kernel: [ 159.505175] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
May 5 13:07:30 kernel: [ 161.505165] cntl_connect_request,Return since CNTL not IDLE,CNTL(1),SYNC(2),AUTH(0),ASSOC(0)
May 5 13:07:31 kernel: [ 162.794987] I/F(apcli1) Set_ApCli_Enable_Proc::(enable = 0)
May 5 13:07:40 kernel: [ 171.989236] Set_Channel_Proc: Channel(161), Cert(0), Quick(0)
May 5 13:07:40 kernel: [ 171.995145] rtmp_set_channel(caller:Set_Channel_Proc+0x170/0x250), Channel(161), quick_ch_change:0.
May 5 13:07:40 kernel: [ 172.004509] APStop() Invalid oper(1)
May 5 13:07:40 kernel: [ 172.008519] APStartUp() Invalid oper(1)

It is exactly the same error with Stock Firmware in AX86s.

Ax86s -3.0.0.4.388_22525
AX53u - 3.0.0.4.386_68691

Hi seanswn,

May I ask, are you able to add the RT-AX53U using ethernet cable?

If no, can you send a feedback using the router GUI at Administration->Feedback.

PM me the email address used once done. Will request RD to check the feedback sent.

Thank you

Yes, but that only is for MESH setup.

Media Bridge and Repeater mode does not work or does not required Ethernet.