ASUS RT-AX86U local network WIFI Ping issue 388.1

[geoffroyg]

Hi,

I have 3 AX86U in Aimesh (wifi backhaul)

Since I upgraded to 388.1, I am getting a lot of short disconnect issue on WIFI, and also very slow ping to wifi devices on the local network. No issue on ethernet.

Anyone else experiencing this? If anyone has an idea of what could cause this?

Pinging a wifi device connected to the Main router.

Request timeout for icmp_seq 0
64 bytes from 192.168.3.203: icmp_seq=0 ttl=64 time=1666.141 ms
Request timeout for icmp_seq 2
64 bytes from 192.168.3.203: icmp_seq=1 ttl=64 time=2297.984 ms
64 bytes from 192.168.3.203: icmp_seq=2 ttl=64 time=1297.898 ms
64 bytes from 192.168.3.203: icmp_seq=3 ttl=64 time=450.337 ms
64 bytes from 192.168.3.203: icmp_seq=4 ttl=64 time=225.543 ms
64 bytes from 192.168.3.203: icmp_seq=5 ttl=64 time=1284.424 ms
64 bytes from 192.168.3.203: icmp_seq=6 ttl=64 time=592.623 ms
64 bytes from 192.168.3.203: icmp_seq=7 ttl=64 time=770.034 ms


Pinging one of the satelite Aimesh ax86u gives these results:

PING 192.168.3.210 (192.168.3.210): 56 data bytes
64 bytes from 192.168.3.210: icmp_seq=0 ttl=64 time=2.190 ms
64 bytes from 192.168.3.210: icmp_seq=1 ttl=64 time=8.886 ms
64 bytes from 192.168.3.210: icmp_seq=2 ttl=64 time=32.671 ms
64 bytes from 192.168.3.210: icmp_seq=3 ttl=64 time=52.867 ms
64 bytes from 192.168.3.210: icmp_seq=4 ttl=64 time=75.811 ms
64 bytes from 192.168.3.210: icmp_seq=5 ttl=64 time=3.677 ms
64 bytes from 192.168.3.210: icmp_seq=6 ttl=64 time=19.809 ms
64 bytes from 192.168.3.210: icmp_seq=7 ttl=64 time=1.942 ms
64 bytes from 192.168.3.210: icmp_seq=8 ttl=64 time=70.872 ms
64 bytes from 192.168.3.210: icmp_seq=9 ttl=64 time=81.417 ms
64 bytes from 192.168.3.210: icmp_seq=10 ttl=64 time=3.099 ms

 

[kernol]

Hi,

I have 3 AX86U in Aimesh (wifi backhaul)

Since I upgraded to 388.1, I am getting a lot of short disconnect issue on WIFI, and also very slow ping to wifi devices on the local network. No issue on ethernet.

Anyone else experiencing this? If anyone has an idea of what could cause this?

Pinging a wifi device connected to the Main router.

Request timeout for icmp_seq 0
64 bytes from 192.168.3.203: icmp_seq=0 ttl=64 time=1666.141 ms
Request timeout for icmp_seq 2
64 bytes from 192.168.3.203: icmp_seq=1 ttl=64 time=2297.984 ms
64 bytes from 192.168.3.203: icmp_seq=2 ttl=64 time=1297.898 ms
64 bytes from 192.168.3.203: icmp_seq=3 ttl=64 time=450.337 ms
64 bytes from 192.168.3.203: icmp_seq=4 ttl=64 time=225.543 ms
64 bytes from 192.168.3.203: icmp_seq=5 ttl=64 time=1284.424 ms
64 bytes from 192.168.3.203: icmp_seq=6 ttl=64 time=592.623 ms
64 bytes from 192.168.3.203: icmp_seq=7 ttl=64 time=770.034 ms


Pinging one of the satelite Aimesh ax86u gives these results:

PING 192.168.3.210 (192.168.3.210): 56 data bytes
64 bytes from 192.168.3.210: icmp_seq=0 ttl=64 time=2.190 ms
64 bytes from 192.168.3.210: icmp_seq=1 ttl=64 time=8.886 ms
64 bytes from 192.168.3.210: icmp_seq=2 ttl=64 time=32.671 ms
64 bytes from 192.168.3.210: icmp_seq=3 ttl=64 time=52.867 ms
64 bytes from 192.168.3.210: icmp_seq=4 ttl=64 time=75.811 ms
64 bytes from 192.168.3.210: icmp_seq=5 ttl=64 time=3.677 ms
64 bytes from 192.168.3.210: icmp_seq=6 ttl=64 time=19.809 ms
64 bytes from 192.168.3.210: icmp_seq=7 ttl=64 time=1.942 ms
64 bytes from 192.168.3.210: icmp_seq=8 ttl=64 time=70.872 ms
64 bytes from 192.168.3.210: icmp_seq=9 ttl=64 time=81.417 ms
64 bytes from 192.168.3.210: icmp_seq=10 ttl=64 time=3.099 ms

I'm afraid most of us with RT-AX86U's are experiencing quirkiness with 388.1 - especially with AiMesh as a Node for this router model.
You will see from my signature that I have reverted to 386.5_2 firmware on both of my RT-AX86U's and am back enjoying rock stead and speedy service from main and node.

You only other option is to run 388.1 on the main router only - and then run Asus stock firmware on the AiMesh Nodes.
Sadly you will not get any support at all from the developer of Merlinware because AiMesh is closed source and beyond his control - as are all WiFi drivers and their bugs.

 

[geoffroyg]

I'm afraid most of us with RT-AX86U's are experiencing quirkiness with 388.1 - especially with AiMesh as a Node for this router model.
You will see from my signature that I have reverted to 386.5_2 firmware on both of my RT-AX86U's and am back enjoying rock stead and speedy service from main and node.

You only other option is to run 388.1 on the main router only - and then run Asus stock firmware on the AiMesh Nodes.
Sadly you will not get any support at all from the developer of Merlinware because AiMesh is closed source and beyond his control - as are all WiFi drivers and their bugs.

Thank you for your answer. I did downgrade to 386.5_2 and all problem solved. I found the issue, because I had to understand, what was causing those gigantic ping on my local network.

The answer is Guest Network. I was using a guest network and funneled it to a wireguard VPN. I wanted to have a specific SSID that would be directed to VPN. That caused the issue. I wanted to get rid of my other set of Aimesh routers specifically for that VPN... I guess they will stay for a while untill this is fixed.

 

[kernol]

Take note that on firmware 386.5_2 you must set "NO" in answer to "Intercept NTP client requests" on the Administration > System tab.

There is a bug in the coding which was fixed in 388.1 - but exists still in 386.5_2 and in 386.7_2
If you answer YES to intercept ... the redirection of Guest Networks to a VPN Client simply does not work.

 

[przemekwawa]

You only other option is to run 388.1 on the main router only - and then run Asus stock firmware on the AiMesh Nodes.
Sadly you will not get any support at all from the developer of Merlinware because AiMesh is closed source and beyond his control - as are all WiFi drivers and their bugs.

For me it didnt worked. I have installed 388.1 on main router and Asus stock on AiMesh, but have same problems. So I believe only reverting both, router and node, to previous would be solution (will do that and check during next following days)

 

[brummygit]

Yes I have similar and found my AX86U nodes were dropping offline briefly even using stock firmware on the nodes and Merlin 388.1 on my RT-AX88U main router. There is something broken in 388 affecting the AX86U either with the Merlin main router losing the AX86U nodes, or in the stock AX86U firmware running as a node (more likely). I don't have the chance to run stock firmware to test on my main router as my network is awful without CAKE QoS.

I posted more info in this thread https://www.snbforums.com/threads/a...ing-with-new-firmware-when-downloading.82384/

 

[kkholimi]

My AX86U performance become erratic with latest Asus Merlin 388.1 upgrade. WAN speeds irregular, and wifi connections drops intermittently. Downgraded back to 386.7_2 and everything went back smooth steady.

 

[Morris]

I must wonder what it is that all of you experiencing problems are doing that I'm not. For one thing, my nodes are connected via ethernet. Before I wired my nodes, I found that 80 wide was much more stable yet I know part of the 160 wide issue is DFS use and my proximity to an airport.

 

[Morris]

Hi,

I have 3 AX86U in Aimesh (wifi backhaul)

Since I upgraded to 388.1, I am getting a lot of short disconnect issue on WIFI, and also very slow ping to wifi devices on the local network. No issue on ethernet.

Anyone else experiencing this? If anyone has an idea of what could cause this?

Pinging a wifi device connected to the Main router.

Request timeout for icmp_seq 0
64 bytes from 192.168.3.203: icmp_seq=0 ttl=64 time=1666.141 ms
Request timeout for icmp_seq 2
64 bytes from 192.168.3.203: icmp_seq=1 ttl=64 time=2297.984 ms
64 bytes from 192.168.3.203: icmp_seq=2 ttl=64 time=1297.898 ms
64 bytes from 192.168.3.203: icmp_seq=3 ttl=64 time=450.337 ms
64 bytes from 192.168.3.203: icmp_seq=4 ttl=64 time=225.543 ms
64 bytes from 192.168.3.203: icmp_seq=5 ttl=64 time=1284.424 ms
64 bytes from 192.168.3.203: icmp_seq=6 ttl=64 time=592.623 ms
64 bytes from 192.168.3.203: icmp_seq=7 ttl=64 time=770.034 ms


Pinging one of the satelite Aimesh ax86u gives these results:

PING 192.168.3.210 (192.168.3.210): 56 data bytes
64 bytes from 192.168.3.210: icmp_seq=0 ttl=64 time=2.190 ms
64 bytes from 192.168.3.210: icmp_seq=1 ttl=64 time=8.886 ms
64 bytes from 192.168.3.210: icmp_seq=2 ttl=64 time=32.671 ms
64 bytes from 192.168.3.210: icmp_seq=3 ttl=64 time=52.867 ms
64 bytes from 192.168.3.210: icmp_seq=4 ttl=64 time=75.811 ms
64 bytes from 192.168.3.210: icmp_seq=5 ttl=64 time=3.677 ms
64 bytes from 192.168.3.210: icmp_seq=6 ttl=64 time=19.809 ms
64 bytes from 192.168.3.210: icmp_seq=7 ttl=64 time=1.942 ms
64 bytes from 192.168.3.210: icmp_seq=8 ttl=64 time=70.872 ms
64 bytes from 192.168.3.210: icmp_seq=9 ttl=64 time=81.417 ms
64 bytes from 192.168.3.210: icmp_seq=10 ttl=64 time=3.099 ms

Thank you for your answer. I did downgrade to 386.5_2 and all problem solved. I found the issue, because I had to understand, what was causing those gigantic ping on my local network.

The answer is Guest Network. I was using a guest network and funneled it to a wireguard VPN. I wanted to have a specific SSID that would be directed to VPN. That caused the issue. I wanted to get rid of my other set of Aimesh routers specifically for that VPN... I guess they will stay for a while untill this is fixed.

When you downgraded, was did you have the router on the same channel as when you had the long pings? The pings you are showing are typical of a congested network or channel