What's new

[384.18_Alpha Builds] Testing all variants

  • 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!

384.18 alpha working well on my 5300 ,no problems so far
 
AX56U Latest beta.
I like performing a factory restore so i keep my setup simple as i can.
NextDNS installed on routers memory.
Performance (and wifi) is stellar. I still can't believe how amazingly fast AX56U is.
No problems, no hiccups, no nothing.
 
Ax88U GPL (3.0.0.4.384.9107) released @RMerlin
 
Smooth update to 384.13_8-gaf00569f60 on 87u
(Uptime 28 days and 18 hours on 384.13_8)
Thanks RMerlin :)
 
Ax88U GPL (3.0.0.4.384.9107) released @RMerlin
I noticed the latest AX58U alpha allows OFDMA DL + UL and AX MU-MIMO setting in Wireless Advanced. The present AX88U only OFDMA DL.
Hopefully this GPL adds this support.
 
Put the newest alpha on my AX88U (couldn't resist any longer) all seems pretty good.
 
ASUS_Wireless_Router_RT_AX88U_WAN_LAN_Bandwidth_Monitor.jpg
Has anyone else mentioned the clocks in QOS don't have numbers anymore? o_O

Firefox and Chrome
 
Last edited:
The latest g6368a955e8 alpha only shows OFDMA DL on my RT-AX56U. I reverted back to g38ed4a85db and now have the OFDMA DL + UL and AX MU-MIMO option again. Also my vacuum refuses to connect on 2.4G on the latest but reverting fixes the issue,


eUi1DRe.png
 
Running selfcompiled Alpha1 with latest changes from yesterday on RT-AX88U. Perfect so far! ;)
 
The latest g6368a955e8 alpha only shows OFDMA DL on my RT-AX56U. I reverted back to g38ed4a85db and now have the OFDMA DL + UL and AX MU-MIMO option again. Also my vacuum refuses to connect on 2.4G on the latest but reverting fixes the issue,


eUi1DRe.png

https://github.com/RMerl/asuswrt-merlin.ng/commit/e5da1db648f01b3a3fafed8bec686a52eca235af

webui: hide OFDMA UL/MIMO settings for RT-AX88U and RT-AX56U

These require updated SDKs/GPLs, we currently only have the
one for the RT-AX58U.
 
only trouble is I rolled back to 384-17 rel and now cannot log in to router gives me wrong password or login name ,i've tried in4 browsers all the same . do i have to reset and start over ? or is there another easier way ?
thanks
 
only trouble is I rolled back to 384-17 rel and now cannot log in to router gives me wrong password or login name ,i've tried in4 browsers all the same . do i have to reset and start over ? or is there another easier way ?
thanks
Likely related to this blurb from 384.17 release notes, and now 384.18 is based on the newer GPL.
384.17 (26-Apr-2020)
Updating some models (like the RT-AC88U) from stock firmware
3.0.0.4.384_81790 and newer will require a factory default reset
after flashing Asuswrt-Merlin, due to a change in how Asus
stores the admin password starting with 384_81790.
 
Newest alfa for Ac86U in logs:
Code:
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind B4:E6:2D:C6:FE:DD, status: 0, reason: Michael failure (e)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(481): eth5: Disassoc B4:E6:2D:C6:FE:DD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 2C:3A:E8:2E:91:D2, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 5C:CF:7F:78:27:FD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 5C:CF:7F:58:47:C9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 2C:3A:E8:2E:8F:C5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 34:CE:00:A2:5E:03, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 5C:CF:7F:66:C0:EB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 78:11:DC:80:FC:F8, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 5C:CF:7F:92:D2:79, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 5C:CF:7F:92:30:A5, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:09+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind CC:50:E3:B6:63:98, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
<13>1 2020-05-30T19:15:10+02:00 AC86UG-7B53F3A-C wlceventd - - - wlceventd: WLCEVENTD wlceventd_proc_event(466): eth5: Deauth_ind 04:CF:8C:76:61:34, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

What doas "reason: Michael failure (e)" mean?
 
only trouble is I rolled back to 384-17 rel and now cannot log in to router gives me wrong password or login name ,i've tried in4 browsers all the same . do i have to reset and start over ? or is there another easier way ?
thanks

RT-AC88U, RT-AC3100 and RT-AC5300 started encrypting the httpd password with recent Asus releases. 384.18 incorporates this code, so reverting any of these three models to a previous version will require either logging in using a SSH key (if you had one set) to reset your password, or doing a factory default reset.

The notice was written for the Changelog, but it got lost in branch merges. As I said, the changelog itself is also "under development".
 
I've got the second variant of alpha1 loaded on two AC86Us. So far, so good.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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