Whoops, you're right, I disabled Guest Network 1 due to the log spamming. Already had forgotten, thanks.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...
Release Asuswrt-Merlin 386.1 is now available
- Thread starter RMerlin
- Start date
- Status
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
Very Senior Member
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
Occasional Visitor
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
Very Senior Member
Apparently this is configured by nvram variable sshd_enable.
Even after setting it manually to 1 ("LAN & WAN") via SSH (and restarting sshd),
EDIT: I can log in remotely via SSH once and then
Can somebody else please test/verify this?
Last edited:
XIII
Very Senior Member
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?
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?
Last edited:
fitnesspmm
Regular Contributor
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.
I think I'll go back to 384.18, I found no issues with this version compared to the new versions.
scarzy
Occasional Visitor
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
Very Senior Member
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
Regular Contributor
No longer supported:
| RT-AC87U | 384.13_10 |
Even asus stock are staying at 382 with bug fix release only.
Wade Coxon
Senior Member
Double check the shipping charge too. For me it shows up as $50US!!
maxbraketorque
Very Senior Member
Interesting. Mine was $5.00 shipping to the West Coast.
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
Regular Contributor
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.
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
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 6EDIT:
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
Last edited:
KingBravery
Senior Member
Try remove node and add it back. If can't add back, check your WPS setting.
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.
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
Regular Contributor
WPS?
I have WPS turned off as the unit is connected by cable to the main router.
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
- Status
Similar threads
- Locked
Similar threads
Similar threads
-
Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14
- Started by B0GDAN
- Replies: 1
-
Release Asuswrt-Merlin 386.14 is now available for AC models
- Started by RMerlin
- Replies: 186
-
-
Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models
- Started by RMerlin
- Replies: 79
-
Beta Asuswrt-Merlin 386.13 beta is now available for AC models
- Started by RMerlin
- Replies: 32
-
Release Asuswrt-Merlin 386.12_6 is now available for AC models
- Started by RMerlin
- Replies: 168
-
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
- Started by RMerlin
- Replies: 23
-
Several Questions Re:Asuswrt-Merlin Feature Implementation
- Started by fenixreign
- Replies: 2
-
-
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
- Started by RMerlin
- Replies: 70