Release Asuswrt-Merlin 386.1 is now available

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.
Status
Not open for further replies.

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.
1613980445878.png

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
 
Last edited:

KingBravery

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.
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

Occasional Visitor
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

Occasional Visitor
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:
ActionResultComment
Withdrew from Trend Micro / rebootedNo Auto Update without forcing refresh in status windowBoth wireless and wired clients would not update
Toggled Jumbo Frames on / rebootedNo Auto Update without forcing refresh in status windowBoth wireless and wired clients would not update
Toggled Jumbo Frames off / rebootedNo Auto Update without forcing refresh in status windowBoth wireless and wired clients would not update
Removed Mesh Node (TM still not active) / rebootedNo Auto Update without forcing refresh in status windowBoth wireless and wired clients would not update
Made config and jffs backup / hard reset / reapplied backupsNo Auto Update without forcing refresh in status windowBoth wireless and wired clients would not update
Hard reset / Manual setup (no TM / no mesh node)Wireless clients auto update / some wired clients auto updateWired 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 updateNo change in behavior from above
Hard reset / Manual setup TM active (FlexQoS) . Hard Reset Mesh Node and re-added it to the main routerWireless clients auto update / some wired clients auto updateNo change in behavior from above
 

miniterror

Regular Contributor
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.

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

Part of the Furniture
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

New Around Here
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?

 

joe scian

Very Senior Member
perhaps try and install entware first using ep ( in amtm) ? make sure /tmp/mnt/8tb is formatted to ext4 with journalling enabled using option fd. Also make sure you have a swap file - ie 2gb - use sw
 

Igor

Regular Contributor
Why did the problem appear only with version 386.1_2? By the way, there is no solution.
 

skeal

Part of the Furniture
Yay! I got my AX88U back from repair. Got it all set up with 386.1_2, works perfect with AIMesh now, among other things. Thanks to @RMerlin for planting the seed in my head to get the router looked at. It was replaced not fixed. Does anyone know the CLI command to retrieve the hardware version on this router?
 

molinski70

New Around Here
Have problems with WiFi 5Ghz on my RT-AX86 with Merlin 386.1 and 386.1.2. It’s working for a couple of days and then disconnect. When I try to connect to 5Ghz it’s always saying it is wrong password. If I change firmware between 386.1 and 386.1.2 it is working again and not complaining about wrong password. Think it’s no problem with 2.4 ghz. Haven’t done any hard reset. Just dirty flashing.
 

ATLga

Senior Member
Have problems with WiFi 5Ghz on my RT-AX86 with Merlin 386.1 and 386.1.2. It’s working for a couple of days and then disconnect. When I try to connect to 5Ghz it’s always saying it is wrong password. If I change firmware between 386.1 and 386.1.2 it is working again and not complaining about wrong password. Think it’s no problem with 2.4 ghz. Haven’t done any hard reset. Just dirty flashing.
You answered your own question, last sentence.
 

Jeffrey Young

Senior Member
Yay! I got my AX88U back from repair. Got it all set up with 386.1_2, works perfect with AIMesh now, among other things. Thanks to @RMerlin for planting the seed in my head to get the router looked at. It was replaced not fixed. Does anyone know the CLI command to retrieve the hardware version on this router?

Have a look at the code example in the following post.

EDIT: The code shows how to get model and serial number, but not the version. Sorry


I've made notes myself as they will come in useful :)
 

ottofreud

Occasional Visitor
You answered your own question, last sentence.
So, is there any instance where upgrading FW does not require a Hard Reset?
 

michae1a1ee

New Around Here
Yesterday I updated my main router and AiMesh node (both RT-AC1900P) to 386.1_2
It took an hour for the GUI on the main router to be accessible, but after that all *seems* fine. Reading these last few posts, was I supposed to do something else? Is a hard reset a wiping of router settings, just a router reboot, or physically powering the unit completely off? As has been asked above, are any of those necessary?
 

L&LD

Part of the Furniture
@ottofreud yes, when the network is working as expected.
 

L&LD

Part of the Furniture
My expectations for my customers are also exceedingly high. No need to waste fuel, both of our time, and possible network outages just to save a few minutes. :)
 

Jack Yaz

Part of the Furniture
Since the new firmware all files and the directory with the name update are deleted after 24 hours.
Is this a bug or intend to work this way?

First I though I had a bug in my script: https://github.com/wbartels/IPSet_ASUS_Lite/issues/2
But even a directory outside skynet was deleted after 24 hours, for example /tmp/test/update/
At a guess, Asus' security daemon. If you save to /jffs/addons do you see the same deletion?
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top