388.9_alpha1 Firmware for RT-AX58U, GT-AX11000, and GT-AXE11000

[visortgw]

One strange thing I see with this alpha is the proliferation of the check_wgc_ep process, what does this process do?

View attachment 64439
View attachment 64440
View attachment 64441

Are you using WireGuard?

 

[commodoro]

Are you using WireGuard?

Yes, I have WireGuard Server up and running but only with this alpha I see this, with the 388.8_4 this process is not present

 

[Tvlz]

@RMerlin

Firefox:
WAN page inspect

Caused by commit "webui: remove NAT type FAQ link that points to the wrong page", fix by also removing line 179 of Advanced_WAN_Content.asp

Site Survey inspect

Need to move the jquery.js line to the top in /www/sysdep/FUNCTION/SITE_SURVEY/Advanced_Wireless_Survey.asp

 

[nagyimre1980]

@RMerlin
The loading of the Main_ConnStatus_Content.asp page (System Log - Active Connections) was fixed a few versions ago!

At that time, the page loading became much faster (if I recall correctly, it was a sorting error).

Now, since version 388.9_alpha1, it has become very slow again! 10-15 sec
Could it be that the previous fix is missing. THX

 

[Zastoff]

Smooth upgrade to 3004.388.9_alpha2-g848412c9ca on RT-AX88u
Thanks RMerlin

edit: My Windows SSH client get error after this update "LIBSSH2 returned LIBSSH2_ERROR_KEX_FAILURE

Mar 25 07:32:56 RT-AX88U dropbear[203312]: Exit before auth from <192.168.1.xx:49xxx>: No matching algo kex

SSH from my android works fine, Will test another SSH client on my computer (SmarTTY may be outdated)

edit1: SmarTTY update was available and now works again

 

[octopus]

New build is out:
3004_388.9_alpha2-g848412c9ca

OneDrive

www.asuswrt-merlin.net

 

[underdose]

Dirty upgrade from alpha1. Nothing to report in the logs and everything works as expected.

 

[Mutzli]

24h up and running well. Checked "Display public IP address for Wireguard clients" and it works as described.

 

[shabbs]

New build is out:
3004_388.9_alpha2-g848412c9ca

OneDrive

www.asuswrt-merlin.net

Just catching these now... loading up on my RT-AX86U APs as we speak... Let's GO!!!

EDIT: Upgraded all my APs. 2nd reboot completed across the board. So far so good - no issues to report. IOT devices all good. Nest HD Cams all good.

Alpha builds across the board now. LOL! Living on the edge.

 

[Ripshod]

Little niggle to report.
I have a 2.4GHz guest network set up for some smart sockets. I've based it on the Customized Network in GNP, and assign VPN via VPN Director. If I set it to Nord/OpenVPN everything is fine, but if I set Nord/Wireguard all the devices are going through deauth/auth cycles every two minutes. This is repeatable even after a reset.
Not a deal breaker for sure - I'm sticking with it.

 

[Calkulin]

Anyone else have nothing displaying on the System Status section of the Network Map page?

 

[karateca]

Anyone else have nothing displaying on the System Status section of the Network Map page?

View attachment 64639

Hi, for me work perfect in my axe11000. Try to clean cache in the browser,

 

[robinjoo1]

Anyone else have nothing displaying on the System Status section of the Network Map page?

View attachment 64639

works fine for me
GT-AX11000pro
using latest alpha 2 release

 

[Aarlin303]

Everything good so far for me (axe11100)

 

[shabbs]

Anyone else have nothing displaying on the System Status section of the Network Map page?

No issues here on my RT-AX86U in AP mode...

 

[Calkulin]

Hi, for me work perfect in my axe11000. Try to clean cache in the browser,

Clearing cache nor trying different computers fixes the issue. Downgrading to Alpha 1 doesn't either but downgrading to 388.8_4 did. I've tested on a RT-AX58U, RT-AX88U and GT-AX11000 and they all have the same issue for me

works fine for me
GT-AX11000pro
using latest alpha 2 release
View attachment 64646

GT-AX11000 Pro is now running 3006 firmware, so not the same firmware anymore as the non Pro models

Everything good so far for me (axe11100)

No issues here on my RT-AX86U in AP mode...

View attachment 64650

Unfortunately the 1 RT-AX86U I could try it to see if it works on there, I don't have remote access to, so I can't verify if it works on that model but the issue is present for me on a RT-AX58U, RT-AX88U and GT-AX11000 running Alpha 1 and 2

 

[karateca]

Clearing cache nor trying different computers fixes the issue. Downgrading to Alpha 1 doesn't either but downgrading to 388.8_4 did. I've tested on a RT-AX58U, RT-AX88U and GT-AX11000 and they all have the same issue for me



GT-AX11000 Pro is now running 3006 firmware, so not the same firmware anymore as the non Pro models




Unfortunately the 1 RT-AX86U I could try it to see if it works on there, I don't have remote access to, so I can't verify if it works on that model but the issue is present for me on a RT-AX58U, RT-AX88U and GT-AX11000 running Alpha 1 and 2

So must be something just in your network, you try to reset and see if persist. Cuz to rare everyone have all fine but just u have all bad.

 

[ExtremeFiretop]

Spoiler: Previous Report

@RMerlin

Just a friendly report that when testing the latest alpha for the GT-AXE11000 (Setup as a node to the parent GT-BE98 Pro)
I did notice some great positives with this alpha! For example, now the 6GHz radio on the GT-AXE11000 node works out of the box!!!

388.9 Radio:

Admin@GT-AXE11000-4BD0:/tmp/home/root# wl -i wl2.1 status
SSID: "SSIDREMOVED-6GHz"
Mode: Managed   RSSI: 0 dBm     SNR: 0 dB       noise: -94 dBm  Channel: 6g37/160
BSSID: XX:XX:XX:XX:XX:XX        Capability: ESS ShortPre RRM
Supported Rates: [ 6(b) 9 12 18 24(b) 36 48 54 ]
HE Capable:
        Chanspec: 6GHz channel 47 160MHz (0x692f)
        Primary channel: 37
        HT Capabilities: 40MHz SGI20 SGI40
        Supported HT MCS :
        Supported HE MCS:
            20/40/80 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
            160 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
QBSS Channel Utilization: 0x8 (3 %)

Previously in 388.8_4 I had to use a script to fix the 6GHz radio since it looked like this after pairing the node:

388.8_4 Radio:

Admin@GT-AXE11000-4BD0:/tmp/home/root# wl -i wl2.1 status
SSID: "SSIDREMOVED-6GHz"
Mode: Managed   RSSI: 0 dBm     SNR: 0 dB       noise: -92 dBm  Channel: 6g37/160
BSSID: 00:00:00:00:00:00        Capability: ESS ShortPre RRM
Supported Rates: [ 6(b) 9 12 18 24(b) 36 48 54 ]
HE Capable:
        Chanspec: 6GHz channel 47 160MHz (0x692f)
        Primary channel: 37
        HT Capabilities: 40MHz SGI20 SGI40
        Supported HT MCS :
        Supported HE MCS:
            20/40/80 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
            160 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
QBSS Channel Utilization: 0xff (100 %)

So thats a great improvement! The 6Ghz now works out of the box when pairing to the parent!

Now for the reports; I did noticed some 5GHz devices no longer connecting, (including the node itself struggling to connect to the parent over 5GHz).
I factory reset the node and was still unable to get some 5GHz devices connected to my node. (Not all, just some)

Checking the configuration differences between my working and non-working setup quickly; I noticed no differences in the output of the 5GHz radios for both firmware's...

388.9 Radio:

Admin@GT-AXE11000-4BD0:/tmp/home/root# wl -i wl1.1 status
SSID: "SSIDREMOVED-5GHz"
Mode: Managed   RSSI: 0 dBm     SNR: 0 dB       noise: -87 dBm  Channel: 149/80
BSSID: XX:XX:XX:XX:XX:XX       Capability: ESS ShortPre RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
        Chanspec: 5GHz channel 155 80MHz (0xe09b)
        Primary channel: 149
        HT Capabilities: 40MHz SGI20 SGI40
        Supported HT MCS : 0-31
        Supported VHT MCS:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
        Supported HE MCS:
            20/40/80 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
            160 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
QBSS Channel Utilization: 0x64 (39 %)

And 388.8 Radio:

Admin@GT-AXE11000-4BD0:/tmp/home/root# wl -i wl1.1 status
SSID: "SSIDREMOVED-5GHz"
Mode: Managed   RSSI: 0 dBm     SNR: 0 dB       noise: -85 dBm  Channel: 149/80
BSSID: XX:XX:XX:XX:XX:XX        Capability: ESS ShortPre RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
        Chanspec: 5GHz channel 155 80MHz (0xe09b)
        Primary channel: 149
        HT Capabilities: 40MHz SGI20 SGI40
        Supported HT MCS : 0-31
        Supported VHT MCS:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
        Supported HE MCS:
            20/40/80 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
            160 MHz:
                NSS1 Tx: 0-11        Rx: 0-11
                NSS2 Tx: 0-11        Rx: 0-11
                NSS3 Tx: 0-11        Rx: 0-11
                NSS4 Tx: 0-11        Rx: 0-11
QBSS Channel Utilization: 0x52 (32 %)

But I did notice a difference in the IP route table between the working and non-working firmwares:

388.9 Routes:

Admin@GT-AXE11000-4BD0:/tmp/home/root# ip route show
default via 192.168.50.1 dev br0
127.0.0.0/8 dev lo scope link
192.168.50.0/24 dev br0 proto kernel scope link src 192.168.50.2
239.0.0.0/8 dev br0 scope link

And: 388.8 Routes:

Admin@GT-AXE11000-4BD0:/tmp/home/root# ip route show
default via 192.168.50.1 dev br0
127.0.0.0/8 dev lo scope link
192.168.50.0/24 dev br0 proto kernel scope link src 192.168.50.2

Unfortunately the only difference I've found so far in 388.9 is for that extra multicast route (covering 239.x.x.x) "239.0.0.0/8 dev br0 scope link "
All that to say, I'm not sure yet why some devices aren't connecting on the 5GHz of the node on 388.9; but figured I should report it before it goes beta stage.

Downgrading the firmware back to 388.8_4 has resolved my issues right away (and gave me the above outputs to compare). My TV that has been refusing to connect to the nodes 5GHz node on 388.9 for the last 2 days instantly connected when downgrading.
I could also stay on 388.9 and work around the issue over the last 2 days by simply having my problematic Samsung TV connect to the nodes 2.4GHz (which worked) or the parents 5GHz (which also worked) but never the nodes 5GHz on 388.9.

Just circling back to my original report with Alpha 1 on the GT-AXE11000, still the same issues with Alpha2.
Interestingly, instead of looking at radios and routes this time, I looked at nvram values for the 5GHz radio, and only notice these changes:

Added to 388.9
wl1.1_owe_groups=19 20 21
wl1.1_owe_ptk_workaround=1
wl1.1_sae_pwe=1
wl1_acs_excl_chans_dfs=
wl1_acs_excl_chans_dfs_2=
--------------------------------
Missing from 388.9
wl1_sel_bw=160
wl1_sel_channel=100
wl1_sel_nctrlsb=0

Not sure if they are related since I can't unset the values; as every time I run service restart_wireless it just re-populates them from the parent router.
So alpha 2 still not functioning correctly as an AiMesh node. I tried adding the missing values and those stick (did not unset), but don't resolve my issues.

Of course as per the previous report, again nothing appears to have changed with the Radio configuration and it's even broadcasting on the same channel.
So why it fails in this alpha I couldn't say.

I tried updating the parent to the latest firmware alpha as well (3006.102_4) and same issue, did not help.
I have rolled back to stable, which has resolved my issues.

(only after doing a factory reset and re-pair)

 

[ExtremeFiretop]

Anyone else have nothing displaying on the System Status section of the Network Map page?

View attachment 64639

So must be something just in your network, you try to reset and see if persist. Cuz to rare everyone have all fine but just u have all bad.

@Calkulin

Can you provide a screenshot of the output of the F12 debug screen please?
What errors do you see; if any?

 

[aex.perez]

A few minutes ago, took a bit on the AX88u and was prompted to manually reboot, then WAN/DHCP took a awhile to grab an IP Address (ISP DHCP Error from the router, so claimed) but it did evemtually got it.

Noticed the device icons were updated on the AiMesh devices, and need to check why the wifi devices that typically bind to the nodes haven't (yet)?

Now for the testing to commence...