What's new

[Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Getting this on 14 had no issues on 13

Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth3: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)

Log was full full just cut a clip
Any ideas ?
https://www.snbforums.com/threads/b...ta-is-now-available.60037/page-39#post-531993
 
Getting this on 14 had no issues on 13

Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth3: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)

Log was full full just cut a clip
Any ideas ?
it's the logs one of your samsung devices, try to disconect and reconnect manually that device
 
Upgraded both my AC68U and AC86U from 384.13 to 384.14 - both in wireless router mode and basic config.

AC68U works just fine with over a week uptime whereas I have some issues with the AC86U - wifi disconnects. Windows troubleshooter happens to easily resolve it by resetting the wifi adapter, stating the cause being invalid IP address of something like this. Never have had my pc randomly discconnecting and will revert back to 384.13 which was rock solid.

Thank you RMerlin for your time and support !
 
As I mentioned earlier if I could set PMF to "disable" (option disable didn't save on latest fw on rt-ax88u), I don't have any other issues, but with PMF set to "capable" or "enable" limit internet usage on android phones nearly to zero with full link speed between mobile and router. Because of that I have to use 384.13 which allow to disable PMF (protected management frames), and make all nice and smooth.

@Merlin
Is there any chance to have ability to disable PMF in future release of your fw.
 
Off topic: I just want to take a minute to wish everyone here a very happy holiday season. Thank you for all the invaluable work you guys do. It's truly wonderful to be part of this outstanding community.
 
Hello guys!
I have a brand new rt-AX88U and i need your help. I have latest Merlin FW and i noticed that my sister's phone (Huawei P9) keeps dropping connection - like every 10 seconds or less. I did all possible, went through all suggestions could find on internet, but it keeps happening. It must be something in a phone rt-ax88 combo, since it doesn't happen when phone is connected to my other router (rt-ac87), set up as access point. And, it happens ONLY with this phone. Other wireless devices are fine.
Attached picture shows situation - note that phone was NOT in use at that time, it was 3-5m from router on the table. When in use, phone occasionally reports that " it switched to mobile data" (which prooves that it was indeed disconnected from wifi for a moment).

Does anyone has a suggestion what could be wrong? I did a "reset network settings" on Huawei phone, doesn't help.

Try changing the Authentication Method to Open System or WPA Auto-Personal.
 
Try changing the Authentication Method to Open System or WPA Auto-Personal.
Well... changing wifi to open is definitely not an option.. Ok, i could set it temporarily, , but since P9 is not too old phone i doubt it's the cause

However, since i changed wifi band from automatic (20/40M for 2.4G and 20/40/80M for 5G) to manual (40M and 80M, respectively) phone stopped disconnecting (for now). I also turned off smart wifi. I'll wait a while then i'll start to change settings back to previous one at the time to see who is to blaim.

Hoping for the best...
 
Getting this on 14 had no issues on 13

Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth3: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:54 syslog: WLCEVENTD wlceventd_proc_event(401): eth1: Disassoc 84:55:A5:67:62:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(420): eth1: Auth 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)
Dec 22 22:52:58 syslog: WLCEVENTD wlceventd_proc_event(449): eth1: Assoc 84:55:A5:67:62:CB, status: 0, reason: d11 RC reserved (0)

Log was full full just cut a clip
Any ideas ?

It annoys me, so in General Log I changed Log only messages more urgent than to Notice, a bodge but hey!
 
Last edited:
Is it? Not even to test if the problems go away? I shouldn't say that. Ofcoz you can turn of firewalls and other kind of "protections" to see if that help with a problem.

Yes, it is very poor advice. Turning off security is an open welcome for serious trouble.

If you want to test WiFi create and use a GUEST network which blocks intranet.

Turning off firewalls is totally stupid for obvious reasons. I used to spend many hours a day sitting at a bench fixing the mess people like you created by thinking it was okay to not have security turned on. PC techs rub their hands with glee as they earn $$$$$$$$$$$$$ fixing the "it's okay people's PC/laptops.
 
Got a strange problem using 384.14 on my Aimesh Nodes (2 ac1900u). With 384.13 speed was around 350 Mbps, updated to 384.14 and speed dropped to around 100 and stayed there. Reverted back to 384.13 without touching a thing and speed is back to around 350. Anybody got an idea why the speed is dropping the second I went to 384.14 on my nodes?

Main router RT-AC88U is on 384.14
 
On 384.14b I had a very bad download speed on a Samsung Galaxy Tab A tablet (SM-T580) with universal beamforming disabled on 5GHz ac. One thing I tried was enabling universal beamforming and since that was enabled the speed became normal.
Strange, never had any issues with disabling this and Airtime Fairness is always disabled too. Usually the opposite is true, if you enable this your newer devices will slow down to an older standard.
 
I think that i narrowed my problem down to channels and channels width. Since i have three routers i have channels manually set not to overlap. On 2.4 i set width to 20 MHz, on 5GHz i have set to 80MHz, but i used extended channels also (i've had set to 36, 52 and 100). So, it seems that problem is either in channel width or in those extended channels. I will experiment further to come down to a actual cause.

In the mean time i would use some advice: preffered channel width for 2.4GHz and 5GHz? I've read that for 2.4 GHz is best to use 20MHz, not 40. How about for 5GHz?
 
I think that i narrowed my problem down to channels and channels width. Since i have three routers i have channels manually set not to overlap. On 2.4 i set width to 20 MHz, on 5GHz i have set to 80MHz, but i used extended channels also (i've had set to 36, 52 and 100). So, it seems that problem is either in channel width or in those extended channels. I will experiment further to come down to a actual cause.

In the mean time i would use some advice: preffered channel width for 2.4GHz and 5GHz? I've read that for 2.4 GHz is best to use 20MHz, not 40. How about for 5GHz?
You right, 20mhz it's better for 2.4 because the posibles interferences from other devices not just wifi routers, for the 5 with 80mhz you should be ok, test with 80 and 40, sometimes I get better speeds with 40
 
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