What's new

Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

  • 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.
RC2-9 dirty upgrade from RC2-8
RT-AC86U + RT-AC68u.
QoS - WAN/LAN Bandwidth Monitor not work
 
@ASUSWRT_2020 Thanks for this update.
Too bad that on XT8, static routing on the node always poses a problem in wireless :(
The report of the bug to Asus seems to progress :)
 
Do you have Guest Network 1 (2.4GHz) enabled?
If not, will you have time to test it (enable it, get some devices connect to it, then wait a bit to see if the internet gets disconnected)? Hope you can help to confirm the problem I experienced on RT-AC5300. Thanks.

I do not use the guest network but I can try this out for you but probably until the weekend. So I am looking for total drop of internet when guest network is on or only on the guest network?
 
I do not use the guest network but I can try this out for you but probably until the weekend. So I am looking for total drop of internet when guest network is on or only on the guest network?
Thank you! No rush.
Yes, expect total internet drop, and the router admin page will show the internet status is disconnected.
 
VLAN is in 2021 roadmap.
For the generic user, VLAN is very hard to understand and causes lots of problems. We plan to make network group management instead of VLAN.
It will include guest network, bandwidth limiter ... etc.
It is not an easy project but will bring benefits to most users.


and bufferbloat mitigation Mechanisms from make wifi better project
 
My Configuration:
  • AiMesh Router: AX88U 9.0.0.4_386_41157-gd618756 + 2 x AiMesh Nodes: AC86U 9.0.0.4_386_41157-gd618756
  • Backhaul (Priority:"Auto", Type:"Wired"), Cisco SG100D 8-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre
My personal SOP to Upgrade from Merlin 386.1_alpha4 -> Stock RC2-B9 9.0.0.4_386_41157:

(1) Upgrade AiMesh Nodes:
  • Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Node (One Node at a time)
  • AiMesh -> Topology -> Select AiMesh Node -> Remove Node (One Node at a time to Factory Reset Node)
(2) Upgrade AiMesh Router:
  • Administration -> System -> Select “Format JFFS partition” & “Enable JFFS custom scripts and configs” -> Apply
    • (I prefer to start everything from scratch - don’t do this if you prefer to preserve anything from JFFS partition)
  • Reboot Router
  • Administration -> Upgrade Firmware -> Select and Upgrade AiMesh Router
  • Administration -> Restore/Save/Upload Setting -> Factory Default - Restore (Initialize)
(3) After Full Factory Reset of AiMesh Router / Nodes, I tried to leave NVRAM using Stock FW default values, except with the following changes:
  • AiProtection - Enable
  • Wireless:
    • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Fixed Control Channel: 11, Roaming Assistant, Explicit / Universal Beamforming: Disable
    • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Fixed Control Channel: 149, Roaming Assistant: Disable
  • WAN DDNS: Using Asus DDNS Service with Let’s Encrypt
  • VPN Servers:
    • OpenVPN works with MacBookPro Tunnelblick 3.8.5beta01, iPhoneXsMax iOS OpenVPN Connect 3.2.2
    • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
    • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9
(4) Add AiMesh Nodes
(5) Reboot AiMesh Network
  • AiMesh -> System Settings -> Reboot (AiMesh Router & Nodes)
I have been running smoothly for about 2 (Edit :)) over 27 hours. Thank You :)
Glad to report that, I have been running 9.0.0.4_386_41157-gd618756 smoothly for about 48 hours, Thank You :)
 
@ASUSWRT_2020 Slightly off topic: A feature request, Please add DHCP option 61 to the WAN config when "Automatic IP" is selected. Marlin F/W has this but less of the newer routers are supported by Marlin and some people don't trust/want 3rd party firmware and would not be confident doing:

nvram set wan0_clientid=<client id>@skydsl|<some hex digits>
nvram set wan_clientid=<client id>@skydsl|<some hex digits>
nvram set wan_clientid_type=0
nvram set wan1_clientid_type=0

This is needed for Sky Broadband in the UK, they are one of the largest ISP in the UK. If you did this and documented it I am sure you would sell more routers in the UK
Thanks!
 
@ASUSWRT_2020

Seems my Intel AX200 M.2 card drop connection on 5Ghz after awhile, ~1-2min on a RT-AX86U.
Updated Intel driver to: 22.10.0

Dec 3 16:21:08 wlceventd: wlceventd_proc_event(505): eth7: Auth 78:2B:46:F2:B1:9C, status: Successful (0)
Dec 3 16:21:08 wlceventd: wlceventd_proc_event(534): eth7: Assoc 78:2B:46:F2:B1:9C, status: Successful (0)
Dec 3 16:21:08 hostapd: eth7: STA 78:2b:46:f2:b1:9c IEEE 802.11: associated
Dec 3 16:21:08 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Dec 3 16:21:08 hostapd: eth7: STA 78:2b:46:f2:b1:9c RADIUS: starting accounting session 486DD16D984DEC93
Dec 3 16:21:08 hostapd: eth7: STA 78:2b:46:f2:b1:9c WPA: pairwise key handshake completed (RSN)
Dec 3 16:21:08 kernel: CONSOLE: 208521.084 wlc_ap_authresp: status 0
Dec 3 16:21:08 kernel: CONSOLE: 208521.085 wlc_ap_process_assocreq_done status 0
Dec 3 16:21:08 kernel: CONSOLE: 208521.085 wl1: STA 78:2b:46:f2:b1:9c has associated tx_type 2
Dec 3 16:21:08 kernel: CONSOLE: 208521.088 iov:SCB_DEAUTH
Dec 3 16:21:08 kernel: CONSOLE: 208521.089 tx:prep:802.1x
Dec 3 16:21:08 kernel: CONSOLE: 208521.089 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 5
Dec 3 16:21:08 kernel: CONSOLE: 208521.091 tx:prep:802.1x
Dec 3 16:21:08 kernel: CONSOLE: 208521.092 iov:SCB_AUTH
Dec 3 16:21:08 kernel: CONSOLE: 208521.099 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 0
Dec 3 16:21:23 kernel: CONSOLE: 208535.808 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 6
Dec 3 16:23:09 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 78:2B:46:F2:B1:9C, status: 0, reason: Unspecified reason (1)
Dec 3 16:23:09 hostapd: eth7: STA 78:2b:46:f2:b1:9c IEEE 802.11: disassociated
Dec 3 16:23:09 kernel: CONSOLE: 208639.376 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 9 tid 0
Dec 3 16:23:09 kernel: CONSOLE: 208639.376 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 9 tid 5
Dec 3 16:23:09 kernel: CONSOLE: 208639.376 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 9 tid 6
Dec 3 16:23:09 kernel: CONSOLE: 208639.376 wl1: random key value: 906A33BB9AD128B94C28021E3BF704864698C4ED1DD1048A66F61DF1F5FB70E2
Dec 3 16:23:09 kernel: CONSOLE: 208639.377 wl1: wlc_txbf_delete_link_serve failed for 78:2b:46:f2:b1:9c
Dec 3 16:23:09 kernel: CONSOLE: 208639.380 iov:SCB_DEAUTH
Dec 3 16:23:09 kernel: CONSOLE: 208639.380 iov:SCB_DEAUTH

[
Dec 3 17:17:59 wlceventd: wlceventd_proc_event(505): eth7: Auth 78:2B:46:F2:B1:9C, status: Successful (0)
Dec 3 17:17:59 wlceventd: wlceventd_proc_event(534): eth7: Assoc 78:2B:46:F2:B1:9C, status: Successful (0)
Dec 3 17:17:59 hostapd: eth7: STA 78:2b:46:f2:b1:9c IEEE 802.11: associated
Dec 3 17:17:59 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Dec 3 17:17:59 hostapd: eth7: STA 78:2b:46:f2:b1:9c RADIUS: starting accounting session BF180BF8C0A823D3
Dec 3 17:17:59 hostapd: eth7: STA 78:2b:46:f2:b1:9c WPA: pairwise key handshake completed (RSN)
Dec 3 17:17:59 kernel: CONSOLE: 211848.826 wlc_ap_authresp: status 0
Dec 3 17:17:59 kernel: CONSOLE: 211848.827 wlc_ap_process_assocreq_done status 0
Dec 3 17:17:59 kernel: CONSOLE: 211848.828 wl1: STA 78:2b:46:f2:b1:9c has associated tx_type 2
Dec 3 17:17:59 kernel: CONSOLE: 211848.831 iov:SCB_DEAUTH
Dec 3 17:17:59 kernel: CONSOLE: 211848.832 tx:prep:802.1x
Dec 3 17:17:59 kernel: CONSOLE: 211848.833 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 5
Dec 3 17:17:59 kernel: CONSOLE: 211848.834 tx:prep:802.1x
Dec 3 17:17:59 kernel: CONSOLE: 211848.836 iov:SCB_AUTH
Dec 3 17:17:59 kernel: CONSOLE: 211848.858 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 6
Dec 3 17:17:59 kernel: CONSOLE: 211848.911 wl1.0: wlc_send_bar: for 78:2b:46:f2:b1:9c seq 0x1 tid 0
Dec 3 17:20:03 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 78:2B:46:F2:B1:9C, status: 0, reason: Unspecified reason (1)
Dec 3 17:20:03 hostapd: eth7: STA 78:2b:46:f2:b1:9c IEEE 802.11: disassociated
Dec 3 17:20:03 kernel: CONSOLE: 211969.589 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 26 tid 0
Dec 3 17:20:03 kernel: CONSOLE: 211969.589 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 26 tid 5
Dec 3 17:20:03 kernel: CONSOLE: 211969.589 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 78:2b:46:f2:b1:9c AID 26 tid 6
Dec 3 17:20:03 kernel: CONSOLE: 211969.589 wl1: random key value: 822F3754764B860E49AC03889752A171A7548EF2E7090E97D8EF31FDEE5585AD
Dec 3 17:20:03 kernel: CONSOLE: 211969.590 wl1: wlc_txbf_delete_link_serve failed for 78:2b:46:f2:b1:9c
Dec 3 17:20:03 kernel: CONSOLE: 211969.593 iov:SCB_DEAUTH
Dec 3 17:20:03 kernel: CONSOLE: 211969.593 iov:SCB_DEAUTH
/QUOTE]

@ASUSWRT_2020
Can you please confirm this behaviour. Start when I played with wpa2/wpa3 settings and newer get it back to function. Now I get DEAUTH on 5Ghz band.
 
Last edited:
@ASUSWRT_2020 can we get an option to only allow ac/ax on the 5GHz Band? For example I have an RT-AX88U, and i'm trying to steer 802.11n clients to my 2.4GHz band and my ac/ax clients to my 5GHz band, but I've only got the option for N/AC/AX Mixed.

Edit: I should have mentioned that I'd like to be able to use the same ssid for both either via smart connect or individually setting the bands with the same name.

Thanks!
 
Last edited:
Some massive log entries in this RC2-B9
Code:
Dec  1 11:25:48 miniupnpd[1409]: addmasqueraderule() : chain UPNP-POSTROUTING not found
Dec  1 11:25:48 miniupnpd[1409]: add_redirect_rule2(): addmasqueraderule returned -1
Dec  1 11:25:48 miniupnpd[1409]: addmasqueraderule() : chain UPNP-POSTROUTING not found
Dec  1 11:25:48 miniupnpd[1409]: add_redirect_rule2(): addmasqueraderule returned -1

@sanke1 Please try this AX88U beta firmware. It included a patch for miniupnpd.
https://www.dropbox.com/s/3skr5ft4banvjpe/RT-AX88U_9.0.0.4_386_41180-g488af35_cferom_ubi.w?dl=0
 
GT-AX11000

Hello, after the last update (RC9) I reset the device and set it manually, but I still have problems with time scheduling: the devices listed, even if unlocked, have problems accessing the internet and the only solution is to completely disable the time scheduling function. Also I would like to know, if possible, why the firmware of GT-AX11000 is smaller in size than RT-AX88U and others, when it has always been larger in size? Thanks
 
Status
Not open for further replies.

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!

Members online

Top