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.

lala_cai

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

Frankflash

Senior Member
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


it has been reported many times in forums
just debugging code for asus
 

lala_cai

Occasional Visitor
it has been reported many times in forums
just debugging code for asus
Hi,

I'm not talking about the debugging code.
I'm facing an issue whereby 2.4GHz disconnect all the clients and no longer allow connection even though I can see the SSID

I attached the logs to see if there are better ways to troubleshoot the issue.
thanks
 

Matthew Patrick

Senior Member
Hi,

I'm not talking about the debugging code.
I'm facing an issue whereby 2.4GHz disconnect all the clients and no longer allow connection even though I can see the SSID

I attached the logs to see if there are better ways to troubleshoot the issue.
thanks
And sometimes it works again? Mine happens on 386 only and it's been fine for weeks on 384.19. I wps reset on 386 and it's still happening. It's basically disconnecting some clients on 2.4ghz and freezing all devices connected to 2.4ghz while not letting any connect to 2.4ghz for minutes at times. Then when it's done doing that it works fine again. And it does that every few minutes. Haven't tried _2 since doesn't seem anything has changed... But yeh it's not a hw issue since 384.19 works just fine for weeks now
 

Frankflash

Senior Member
Hi,

I'm not talking about the debugging code.
I'm facing an issue whereby 2.4GHz disconnect all the clients and no longer allow connection even though I can see the SSID

I attached the logs to see if there are better ways to troubleshoot the issue.
thanks

only Asus can fix it you should send logs to asus wifi is closed scorce and Merlin cant fix it
 

lala_cai

Occasional Visitor
And sometimes it works again? Mine happens on 386 only and it's been fine for weeks on 384.19. I wps reset on 386 and it's still happening. It's basically disconnecting some clients on 2.4ghz and freezing all devices connected to 2.4ghz while not letting any connect to 2.4ghz for minutes at times. Then when it's done doing that it works fine again. And it does that every few minutes. Haven't tried _2 since doesn't seem anything has changed... But yeh it's not a hw issue since 384.19 works just fine for weeks now

Nope, it will not work again as I have camera which reports to the cloud which will notify me it has been disconnected for 30 minutes.
On the 384.19, it will still happen once maybe in weeks but not as frequent as 386 (in days).
 

Wishmaster1965

Regular Contributor
Was hoping to test openVPN today after the new update to 386.1.2 but no devices can connect back to home. Upon checking the router its missing the tun interfaces

Tried a reboot to no effect. So looks like I will have to rebuild the router from scratch again. :mad:
 
Last edited:

GregS

Occasional Visitor
Upgraded a week or two ago and just noticed some wl commands don't work anymore on my AX88:

[email protected]:/# wl -i wl0.1 assoclist | wc -l
wl: wl driver adapter not found

[email protected]:/# wl ver
Broadcom BCA: 17.10 RC121.37
wl0: Jan 16 2021 07:02:35 version 17.10.121.37 (r789389) FWID 01-f6b943ee
 

jpthsd

Regular Contributor
For RT-AX86U with latest 386.1_2 or 386.1, the main page of AX86U has a HTML frame/page issue, it covers the wireless information lines...Is there any fix for that? It only happens on AX86U but AC86U main web page looks right!
 

L&LD

Part of the Furniture
I haven't seen that issue. How long are your SSIDs? What browsers have you tested? What about a screen snip?
 

Wanabo

Occasional Visitor
On a RT-AC88U
# wl -i wl0.1 assoclist | wc -l
1

t# wl ver
1.363 RC2.0
wl0: Nov 24 2020 14:12:26 version 10.10.69.69040 (r793144) FWID 01-******
 

joegreat

Very Senior Member
Upgraded a week or two ago and just noticed some wl commands don't work anymore on my AX88:

[email protected]:/# wl -i wl0.1 assoclist | wc -l
wl: wl driver adapter not found

[email protected]:/# wl ver
Broadcom BCA: 17.10 RC121.37
wl0: Jan 16 2021 07:02:35 version 17.10.121.37 (r789389) FWID 01-f6b943ee
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... :rolleyes:
 

QuikSilver

Very Senior Member

knight401

New Around Here
q.PNG

ac88u 386.1_2
wifi 5G 160mhz work perfect
but I got huge transmit amout
is it correctly?
thanks
 

jpthsd

Regular Contributor
I haven't seen that issue. How long are your SSIDs? What browsers have you tested? What about a screen snip?
my SSID about 10 characters,,,the frame of router page info covering the wireless SSID info on the top thus it only shows Operation mode and Firmware version...it's only happened on the main page. (Tested Edge Chrome, Google Chrome, Firefox, Opera, all are the same)...
 

fitnesspmm

Regular Contributor
I just did an upgrade from 384.18 to 386.2.1 where the login screen has been blank for over 60 minutes now when I try to log in. After about 10-15 minutes, it goes back to the login screen and hangs on 'transferring data from 192.168.1.1. Any suggestions?

I also rebooted the router after 20 minutes after upgrading before I read the log file to wait up to an hour. Would this cause any issues?
 
Last edited:

Butterfly Bones

Very Senior Member
I just did an upgrade from 384.18 to 386.2.1 where the login screen has been blank for over 60 minutes now when I try to log in. After about 10-15 minutes, it goes back to the login screen and hangs on 'transferring data from 192.168.1.1. Any suggestions?

I also rebooted the router after 20 minutes after upgrading before I read the log file to wait up to an hour. Would this cause any issues?

point #4
From RMerlin directly - NO
  • Webui very slow or unreachable after upgrading (this is normal as the router is doing database maintenance, just give it time, can take 5-60 mins depending on the router model)
 

fitnesspmm

Regular Contributor

point #4
From RMerlin directly - NO

It's been nearly 2 hours now.... I just hope rebooting the router after upgrading didn't stuff it up....

It's done, took just over 2 hours. Need to update the log file to say it can take up to 3 hours I think.
 
Last edited:

LimJK

Very Senior Member
I have been running smoothly with Merlin 386.1_2 for about a week. Thank You! :)

My Configuration:
  • AiMesh Router: AX88U 386.1_2 + 2 x AiMesh Nodes: AC86U 386.1_2
  • Backhaul (Priority:"Auto", Type:"Wired"), Asus GX-U1051 5-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre
After Upgrading Firmware to 386.1_2, I did Factory reset for AiMesh Nodes first & followed by Router and use Merlin default NVRAM setting except with the following changes:
  • Enabled AiProtection: ON
  • USB Application
    • UPnP Media Server: OFF
    • Samba Share: OFF
  • LAN:
    • 40 items in my DHCP manually Assigned IP List
  • Wireless:
    • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Control Channel: Auto, Universal Beamforming: Disable
    • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Control Channel: Auto
  • WAN DDNS:
    • DNS Privacy Protocol: DoT (using Cloudflare)
    • Using Asus DDNS Service with Let’s Encrypt
  • IPv6: Enable
    • Native
  • VPN Servers (Connecting one at a time with the following clients):
    • OpenVPN works with
      • MacBookPro Tunnelblick 3.8.5beta04 (build 5640),
      • iPhoneXsMax iOS OpenVPN Connect 3.2.3
    • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
      • Cisco IPSec
      • IKEv2 (while connection works, there is no Status information on IPSec VPN Server)
    • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9
  • Scripts on amtm 3.1.8FW
    • Diversion 4.1.12 uiDivStats 2.3.2 Skynet 7.2.3 connmon 2.8.4
 
Last edited:
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