Release Asuswrt-Merlin 386.1 is now available

GregS · Feb 21, 2021

joegreat said:
Wrong interface? On my AX88 5G WLAN is on eth7 and 2.4G on eth6 and wl commands works fine there..
Did you enable wl0.1 (guest network)? There are currently some (logging) issues with guest 1 - maybe you run into another problem...

Whoops, you're right, I disabled Guest Network 1 due to the log spamming. Already had forgotten, thanks.

chongnt · Feb 21, 2021

bluepoint said:
You'll see the kernel prompt(log) when you access "Adapttive QOS" then exit from it, that's normal.

Thanks for pointing this out. Just realized there are so many messages by just access "Adaptive QoS" page. Even /jffs/scripts/nat-start is run.

XIII · Feb 21, 2021

XIII said:
Currently not on my local network and can't log in remotely on my router via SSH (though I thought I enabled that).

I did enable it, but as soon as I log out and back in again it reverts to “LAN only”.

Is this a known bug of this release? (On AC86u)

jomcty · Feb 21, 2021

lala_cai said:

I'm facing a problem with RT-AC86U where the devices is unable to connect to 2.4GHz after a certain time (from days to weeks). I can see the SSID but it just refused to connect.
I have no problem with 5GHz. This issues seems to begin from 384.18 onwards and now I'm on 386.1_2 and it's still happening.
By the time I notice the problem and view the logs, its already rolled over.

Any method or any logs I can check for the issue?

Code:

Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 28:6C:07:B9:00:A2, status: Successful (0), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:00 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 00:03:7F:77:0D:76, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind 84:D8:1B:20:A6:8F, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:01 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth 34:CE:00:FB:63:2C, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(490): eth5: Deauth_ind B0:95:75:70:B0:4E, status: 0, reason: Class 2 frame received from nonauthenticated station (6), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth B0:95:75:70:B0:4E, status: Successful (0), rssi:0
Feb 20 14:46:02 wlceventd: wlceventd_proc_event(526): eth5: Auth 84:D8:1B:20:A6:8F, status: Successful (0), rssi:0

Try manually assigning your 2.4 MHz channel to the one with the least signal. I had this problem with my IoT Nexx Garage Opener until did that.

XIII · Feb 21, 2021

XIII said:
I did enable it, but as soon as I log out and back in again it reverts to “LAN only”.

Is this a known bug of this release? (On AC86u)

Apparently this is configured by nvram variable sshd_enable.

Even after setting it manually to 1 ("LAN & WAN") via SSH (and restarting sshd), ~~I cannot log in via SSH remotely.~~

EDIT: I can log in remotely via SSH once and then ~~the variable sshd_enable is reset to 2...~~ remote log in via SSH fails again.

Can somebody else please test/verify this?

XIII · Feb 21, 2021

OOPS: I forgot that I had done a factory reset and Skynet was still set to Secure Mode (which disables WAN access).

However, even disabling Secure Mode does not help.

EDIT: Seems solved after upgrading to 386.1 Alpha 2 and/or unbanning my (external) IP in Skynet?

fitnesspmm · Feb 21, 2021

Everything fine except my Swann Security Cameras lag and drop out, any suggestions on how to fix?

I think I'll go back to 384.18, I found no issues with this version compared to the new versions.

scarzy · Feb 21, 2021

maxbraketorque said:
I've got a fan setup like those for one of my AC86Us. I also have another AC86U with the fan in the link below. It snaps in place rather than requiring tape, screws or velcro. And it has an adjustable speed and dust filter. Its very nifty. Delivery time was much faster than indicated on the Amazon website.

https://www.amazon.com/gp/product/B07XDGXWC3/?tag=snbforums-20

This looks great! I noticed one of the reviews says this fan did not fit on the AC2900 (AC86u). Can you confirm you are using this fan as intended by snapping in place on a RT-AC86u? I just wanted to check before placing an order. Any idea how many degrees this dropped your CPU temperature? Thanks for your help!

maxbraketorque · Feb 21, 2021

scarzy said:
This looks great! I noticed one of the reviews says this fan did not fit on the AC2900 (AC86u). Can you confirm you are using this fan as intended by snapping in place on a RT-AC86u? I just wanted to check before placing an order. Any idea how many degrees this dropped your CPU temperature? Thanks for your help!

Yes, it fits my AC86U as intended, and the air flow ports on the back of the router match up with the air flow ports on the fan assembly. The GT-AC2900 has different air flow ports.

ROG Rapture GT-AC2900 | Gaming Routers｜ROG - Republic of Gamers｜ROG USA

NVIDIA GeForce Now recommended wifi router for Steam, Uplay cloud gaming, console game, mobile game. Easy setup NAT open, wide range and smooth signal.

rog.asus.com

RT-AC86U｜WiFi Routers｜ASUS USA

ASUS has a range of wireless routers suitable for every purpose. Whether it's for your home, for business trips, or for any other need or environment, there's an ASUS router for you.

www.asus.com

alex1236hk · Feb 21, 2021

Rango said:
No more AC-87U Merlin updates?

What is the latest scoop?

Thank you in advance.

No longer supported:

RT-AC87U

384.13_10

Even asus stock are staying at 382 with bug fix release only.

Wade Coxon · Feb 21, 2021

scarzy said:
I just wanted to check before placing an order.

Double check the shipping charge too. For me it shows up as $50US!!

maxbraketorque · Feb 21, 2021

Wade Coxon said:
Double check the shipping charge too. For me it shows up as $50US!!

Interesting. Mine was $5.00 shipping to the West Coast.

lala_cai · Feb 22, 2021

jomcty said:
Try manually assigning your 2.4 MHz channel to the one with the least signal. I had this problem with my IoT Nexx Garage Opener until did that.

Normally I’ll just fixed to channel 1 after the initial reset. Will try to fixed it to other channel and see if this is still happening.

miniterror · Feb 22, 2021

My AI Mesh node doesnt connect to the main router since this morning.
Not sure if related to this firmware or a different bug though.
I have a AX-86U as main router and use a AX-58U as wired node for the upper levels of my house.
Just started work and noticed i had a weak WiFi signal on the laptop.
I can ping the IP of the Mesh node, i can access the webgui of the node but its states it cant reach the Mesh router, wich is strange as my client can reach the node through the router.

I dont see anyhting in the logs of the router about a connection attempt of the node.
Rebooting the node from the router AIMesh menu actually reboots the node, so the connection from the router to the node seems to work.

Code:

-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Feb 22 08:55:36 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered disabled state
Feb 22 08:55:36 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
SNIP BLOG EMIT
Feb 22 08:55:42 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:42 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 1000 mbps full duplex
Feb 22 08:55:42 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:55:42 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:55:44 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:44 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:44 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered learning state
Feb 22 08:55:45 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22a0
Feb 22 08:55:45 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2360
Feb 22 08:55:46 RT-AX86U-FB40 kernel: br0: topology change detected, propagating
Feb 22 08:55:46 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered forwarding state
Feb 22 08:55:48 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Feb 22 08:55:48 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered disabled state
Feb 22 08:55:48 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1b68
SNIP BLOG EMIT
Feb 22 08:55:56 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:00 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 1000 mbps full duplex
Feb 22 08:56:00 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22c0
Feb 22 08:56:00 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:56:00 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 40:2f:86:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA e4:a7:a0:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 44:07:0b:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 88:d0:39:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 14:c1:4e:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth6: STA 04:cf:8c:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 64:a2:f9:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.488 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.488 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.590 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA c0:ee:fb:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:02 RT-AX86U-FB40 kernel: CONSOLE: 147202.693 tx:prep:802.1x
Feb 22 08:56:02 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:02 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:02 RT-AX86U-FB40 hostapd: eth7: STA 28:c2:1f:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:02 RT-AX86U-FB40 kernel: CONSOLE: 147203.191 tx:prep:802.1x
Feb 22 08:56:02 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered learning state
Feb 22 08:56:04 RT-AX86U-FB40 kernel: br0: topology change detected, propagating
Feb 22 08:56:04 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered forwarding state
Feb 22 08:56:05 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22a0
Feb 22 08:56:12 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:12 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:13 RT-AX86U-FB40 kernel: device br0 entered promiscuous mode
Feb 22 08:56:17 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1b88
SNIP BLOG EMIT
Feb 22 08:56:18 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:19 RT-AX86U-FB40 kernel: device br0 left promiscuous mode
Feb 22 08:56:21 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:21 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:26 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1c28
Feb 22 08:56:30 RT-AX86U-FB40 kernel: CONSOLE: 147231.041 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Feb 22 08:56:32 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2
SNIP BLOG EMIT
Feb 22 08:57:09 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2380
Feb 22 08:57:10 RT-AX86U-FB40 kernel: CONSOLE: 147270.640 wl1.0: wlc_send_bar: for 40:2f:86:XX:XX:XX seq 0x846 tid 0
Feb 22 08:57:11 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1ac8
Feb 22 08:57:13 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:57:18 RT-AX86U-FB40 kernel: CONSOLE: 147278.401 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xedf tid 6
Feb 22 08:57:25 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22e0
SNIP BLOG EMIT
Feb 22 08:57:30 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22e0
Feb 22 08:57:30 RT-AX86U-FB40 kernel: CONSOLE: 147290.790 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Feb 22 08:57:38 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2
SNIP BLOG EMIT
Feb 22 08:57:54 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:57:59 RT-AX86U-FB40 kernel: CONSOLE: 147320.112 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xf2e tid 6
Feb 22 08:57:59 RT-AX86U-FB40 kernel: CONSOLE: 147320.113 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xf2e tid 6

EDIT:
Just rebooted everything and still the same problem.
Looking at my WiFi networks i can now also see the Open ASUS network and from the strength i assume its the AX58U.
But im not able to actually connect too it

KingBravery · Feb 22, 2021

miniterror said:

My AI Mesh node doesnt connect to the main router since this morning.
Not sure if related to this firmware or a different bug though.
I have a AX-86U as main router and use a AX-58U as wired node for the upper levels of my house.
Just started work and noticed i had a weak WiFi signal on the laptop.
I can ping the IP of the Mesh node, i can access the webgui of the node but its states it cant reach the Mesh router, wich is strange as my client can reach the node through the router.
View attachment 31074
I dont see anyhting in the logs of the router about a connection attempt of the node.
Rebooting the node from the router AIMesh menu actually reboots the node, so the connection from the router to the node seems to work.

Code:

-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Feb 22 08:55:36 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered disabled state
Feb 22 08:55:36 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
SNIP BLOG EMIT
Feb 22 08:55:42 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:42 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 1000 mbps full duplex
Feb 22 08:55:42 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:55:42 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:55:44 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:44 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:55:44 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered learning state
Feb 22 08:55:45 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22a0
Feb 22 08:55:45 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2360
Feb 22 08:55:46 RT-AX86U-FB40 kernel: br0: topology change detected, propagating
Feb 22 08:55:46 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered forwarding state
Feb 22 08:55:48 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Feb 22 08:55:48 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered disabled state
Feb 22 08:55:48 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1b68
SNIP BLOG EMIT
Feb 22 08:55:56 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:00 RT-AX86U-FB40 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 1000 mbps full duplex
Feb 22 08:56:00 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22c0
Feb 22 08:56:00 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:56:00 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered listening state
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 40:2f:86:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA e4:a7:a0:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 44:07:0b:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 88:d0:39:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 14:c1:4e:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth6: STA 04:cf:8c:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA 64:a2:f9:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.488 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.488 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.489 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 kernel: CONSOLE: 147202.590 tx:prep:802.1x
Feb 22 08:56:01 RT-AX86U-FB40 hostapd: eth7: STA c0:ee:fb:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:02 RT-AX86U-FB40 kernel: CONSOLE: 147202.693 tx:prep:802.1x
Feb 22 08:56:02 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:02 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:02 RT-AX86U-FB40 hostapd: eth7: STA 28:c2:1f:XX:XX:XX WPA: group key handshake completed (RSN)
Feb 22 08:56:02 RT-AX86U-FB40 kernel: CONSOLE: 147203.191 tx:prep:802.1x
Feb 22 08:56:02 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered learning state
Feb 22 08:56:04 RT-AX86U-FB40 kernel: br0: topology change detected, propagating
Feb 22 08:56:04 RT-AX86U-FB40 kernel: br0: port 2(eth3) entered forwarding state
Feb 22 08:56:05 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22a0
Feb 22 08:56:12 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:12 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:13 RT-AX86U-FB40 kernel: device br0 entered promiscuous mode
Feb 22 08:56:17 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1b88
SNIP BLOG EMIT
Feb 22 08:56:18 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:19 RT-AX86U-FB40 kernel: device br0 left promiscuous mode
Feb 22 08:56:21 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:21 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:56:26 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1c28
Feb 22 08:56:30 RT-AX86U-FB40 kernel: CONSOLE: 147231.041 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Feb 22 08:56:32 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2
SNIP BLOG EMIT
Feb 22 08:57:09 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2380
Feb 22 08:57:10 RT-AX86U-FB40 kernel: CONSOLE: 147270.640 wl1.0: wlc_send_bar: for 40:2f:86:XX:XX:XX seq 0x846 tid 0
Feb 22 08:57:11 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x1ac8
Feb 22 08:57:13 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:57:18 RT-AX86U-FB40 kernel: CONSOLE: 147278.401 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xedf tid 6
Feb 22 08:57:25 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22e0
SNIP BLOG EMIT
Feb 22 08:57:30 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x22e0
Feb 22 08:57:30 RT-AX86U-FB40 kernel: CONSOLE: 147290.790 wl1: wlc_ampdu_recv_addba_resp: 44:07:0b:XX:XX:XX: Failed. status 37 wsize 64 policy 1
Feb 22 08:57:38 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x2
SNIP BLOG EMIT
Feb 22 08:57:54 RT-AX86U-FB40 kernel: _blog_emit, blogp = 0x23c0
Feb 22 08:57:59 RT-AX86U-FB40 kernel: CONSOLE: 147320.112 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xf2e tid 6
Feb 22 08:57:59 RT-AX86U-FB40 kernel: CONSOLE: 147320.113 wl1.0: wlc_send_bar: for 14:c1:4e:XX:XX:XX seq 0xf2e tid 6

EDIT:
Just rebooted everything and still the same problem.
Looking at my WiFi networks i can now also see the Open ASUS network and from the strength i assume its the AX58U.
But im not able to actually connect too it

Try remove node and add it back. If can't add back, check your WPS setting.

Suzib6sw · Feb 22, 2021

miniterror said:
My AI Mesh node doesnt connect to the main router since this morning.
Not sure if related to this firmware or a different bug though.
I have a AX-86U as main router and use a AX-58U as wired node for the upper levels of my house.
Just started work and noticed i had a weak WiFi signal on the laptop.
I can ping the IP of the Mesh node, i can access the webgui of the node but its states it cant reach the Mesh router, wich is strange as my client can reach the node through the router.

EDIT:
Just rebooted everything and still the same problem.
Looking at my WiFi networks i can now also see the Open ASUS network and from the strength i assume its the AX58U.
But im not able to actually connect too it

I saw something Similar twice before. .. Once was after power cuts.. the node router came up but the WAN led was red. Second time, it came back up bit everything looked ok except no connectivity .. These have ethernet back haul.. In the 1st case, just adding the node back in the GUI worked, the Second case, the WPS button reset on the node and then re-add via the GUI worked. I would suggest , if you had power spikes or drops, you get the node on a UPS or at the very lease, a surge protector.

ottofreud · Feb 22, 2021

ottofreud said:
Perhaps. Can't withdraw at the moment to test. But if i get some low use time this weekend, I'll test it for an hour or so with clients powering on and off.

Over the weekend I played around with this problem and did not get very far with respect to a solution. I would disconnect and reconnect clients to see if the client list would auto update. Things I tried to see if I could get the client list to auto update:

Action	Result	Comment
Withdrew from Trend Micro / rebooted	No Auto Update without forcing refresh in status window	Both wireless and wired clients would not update
Toggled Jumbo Frames on / rebooted	No Auto Update without forcing refresh in status window	Both wireless and wired clients would not update
Toggled Jumbo Frames off / rebooted	No Auto Update without forcing refresh in status window	Both wireless and wired clients would not update
Removed Mesh Node (TM still not active) / rebooted	No Auto Update without forcing refresh in status window	Both wireless and wired clients would not update
Made config and jffs backup / hard reset / reapplied backups	No Auto Update without forcing refresh in status window	Both wireless and wired clients would not update
Hard reset / Manual setup (no TM / no mesh node)	Wireless clients auto update / some wired clients auto update	Wired clients that auto updated seem to be "newer" clients. That is, had NIC cards that were from 2016 or newer. Brand of NIC seemed irrelevant (Realtek, Broadcom, INTEL, etc.)
Hard reset / Manual setup TM active (FlexQoS) (no mesh node)	Wireless clients auto update / some wired clients auto update	No change in behavior from above
Hard reset / Manual setup TM active (FlexQoS) . Hard Reset Mesh Node and re-added it to the main router	Wireless clients auto update / some wired clients auto update	No change in behavior from above

miniterror · Feb 22, 2021

KingBravery said:
Try remove node and add it back. If can't add back, check your WPS setting.

WPS?
I have WPS turned off as the unit is connected by cable to the main router.

Suzib6sw said:
I saw something Similar twice before. .. Once was after power cuts.. the node router came up but the WAN led was red. Second time, it came back up bit everything looked ok except no connectivity .. These have ethernet back haul.. In the 1st case, just adding the node back in the GUI worked, the Second case, the WPS button reset on the node and then re-add via the GUI worked. I would suggest , if you had power spikes or drops, you get the node on a UPS or at the very lease, a surge protector.

Thx, its working now after i fully resetted the device.
I am not aware of powerspikes or drops, none of my devices have ever had power problems and the main fuses are still intact
Im going to monitor if it happens again

L&LD · Feb 22, 2021

If you remove the AiMesh node and want to add it back into the network again, then WPS must be turned on to be able to do so.

Afterward, disable it.

ABuNeNe · Feb 22, 2021

just upgraded to 389.1.2, did a factory reset and try to install Diversion but it's seem like hanging as seen below. Any idea?

Thread starter	Title	Forum	Replies	Date
B	Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14	Asuswrt-Merlin	1	Oct 27, 2024
	Release Asuswrt-Merlin 386.14 is now available for AC models	Asuswrt-Merlin	215	Jul 20, 2024
	Beta Asuswrt-Merlin 386.14 beta is now available	Asuswrt-Merlin	35	Jul 1, 2024
	Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models	Asuswrt-Merlin	79	Apr 7, 2024
	Beta Asuswrt-Merlin 386.13 beta is now available for AC models	Asuswrt-Merlin	32	Mar 28, 2024
	Release Asuswrt-Merlin 386.12_6 is now available for AC models	Asuswrt-Merlin	168	Feb 26, 2024
	Please add Asuswrt-merlin to GT-BE98 (Non-pro) version	Asuswrt-Merlin	22	Saturday at 2:26 PM
	Release Asuswrt-Merlin 3004.388.8_4 is now available	Asuswrt-Merlin	92	Nov 17, 2024
	Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices	Asuswrt-Merlin	67	Nov 3, 2024
F	Several Questions Re:Asuswrt-Merlin Feature Implementation	Asuswrt-Merlin	2	Oct 16, 2024

Release Asuswrt-Merlin 386.1 is now available

Occasional Visitor

Very Senior Member

Very Senior Member

Occasional Visitor

Very Senior Member

Very Senior Member

Regular Contributor

Occasional Visitor

Very Senior Member

Regular Contributor

Senior Member

Very Senior Member

Occasional Visitor

Regular Contributor

Senior Member

Regular Contributor

Occasional Visitor

Regular Contributor

Part of the Furniture

Occasional Visitor

Similar threads

Similar threads

Support SNBForums w/ Amazon

Sign Up For SNBForums Daily Digest