Javascripts are minified during firmware build, for space reasons. The original code is properly formatted.
388.9_alpha1 Firmware for RT-AX58U, GT-AX11000, and GT-AXE11000
- Thread starter visortgw
- Start date
Dirty Upgrade no issues.
Seems Asus has updated the Privacy Terms in this update.
ASUS PRIVACY NOTICE
Welcome to use this ASUS Software/web GUI interface (“this Software”/ “this Interface”) for ASUS networking products (“ASUS Product”)! Please read this Notice carefully:
- In order to provide you with the following functions, by clicking “Agree” below, you agree to share your following data related to your ASUS Product(s) associated with this Software/ Interface:
- Function of account log-in: For easier management of your ASUS Product(s) and related services (such as binding your ASUS Product(s) under your account), you may need to provide ASUS with your login email address of this Software.
- Functions of ASUS firmware and security upgrades, DDNS (Dynamic Domain Name System for connecting ASUS Product(s) with changing or fixed IP address), remote access service that allows this Software and some third party services (Alexa/Google Assistant/IFTTT) to remotely connect to your ASUS Product(s), backup/transfer service for the configuration settings among ASUS Products, management of multiple ASUS Products and push notification service:In order to provide you with the above functions and to assess and improve ASUS services and improve stability, you may need to provide ASUS with your IP address, MAC address, DDNS name, the country of manufacture, model name, firmware and software module version, security version, manufacture date and version of hardware, firmware update data (such as execution method, time and numbers of firmware update), system status (such as usage status of fan, CPU, RAM, flash memory and voltage), numbers and time of boot-ups, the time/network/LAN-port you use to connect to your ASUS Product(s), crash history, product name and code, the number of times of security events with ASUS, login/usage status, as well as screen size, language settings and type of mobile device (such as iOS device).
- Third party-related services:
- Alexa/Google Assistant/IFTTT: If you use any of these services, you agree that ASUS may share your IP address and Mac address to Amazon.com Inc./Google Inc./ IFTTT Inc. in order to remotely connect your ASUS Product(s) with these services.
- Third party Software Development Kit (SDK) for push notification function: To provide you with the above service, you agree that ASUS may use SDKs developed by third parties. We may change the list of SDKs from time to time, and update the list via this Notice. Below is the current SDK for this function: Google Firebase for Android SDK, with its data collection notice released by Google Inc. at https://firebase.google.com/docs/android/play-data-disclosure.
- For the services provided by third parties, please note that your information may be collected by those third parties. For more information, please refer to the privacy- related statement issued by the third parties.
- Please kindly note: If you click “Disagree” below or disable the sharing of the above data of paragraph 1 with ASUS through “Administration” page of this Interface, or if you are a child thus preventing the collection of the above data by ASUS, it may result in the following effects:
- The inability to update to the latest firmware version and unable to receive the most up-to-date security protection on your ASUS Product(s). However, to protect the security of your ASUS Product(s) and ensure the compliance with laws, for upgrades addressing important security issues or meeting legal/regulatory requirements, those upgrades will still be downloaded and installed automatically.In this case, ASUS will collect your IP address, hashed MAC address, the country of manufacture, model name, firmware and software module version and security version, which is necessary data for ASUS to deliver these important upgrades to your ASUS Product(s) associated with this Software/ Interface.
- The functions listed in paragraph 1 for this Software/ Interface may not be worked normally without the above data of paragraph 1 for providing those services. The essential functions of ASUS Products will not be affected, such as internet connection and local settings stored in your ASUS Product(s).
- ASUS is committed to protecting and respecting your privacy; you may visit “Administration->Policy” at this Interface to enable/disable the sharing of your above data with ASUS at all times. To know more about how ASUS protects your privacy, please visit ASUS’ Privacy Policy.
Last edited:
Also something new I noticed under firmware upgrades. @RMerlin will this affect Merlin builds going forward in terms of stock firmware being forced onto routers?
Edit: My only hope is ASD or this security upgrade doesn't cause grievances.
Some further discussion on it can be found here: https://www.snbforums.com/threads/security-upgrade-option-on-rt-ax88u-pro.88714/
www.snbforums.com
Edit: My only hope is ASD or this security upgrade doesn't cause grievances.
Some further discussion on it can be found here: https://www.snbforums.com/threads/security-upgrade-option-on-rt-ax88u-pro.88714/
Auto Firmware Upgrade made official - a new Note in Asus FAQ
In this Firmware Update FAQ: https://www.asus.com/support/FAQ/1008000/ ... a new Note appeared recently: This gives you an explanation why your router auto upgraded to different* Asuswrt version even with Auto Firmware Upgrade set to OFF. * - When/if it happens I'm assuming it will auto...
www.snbforums.com
Last edited:
Excellent thank you for the clarification.
ExtremeFiretop
Very Senior Member
@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:
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:
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:
And 388.8 Radio:
But I did notice a difference in the IP route table between the working and non-working firmwares:
388.9 Routes:
And: 388.8 Routes:
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 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:
Code:
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:
Code:
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:
Code:
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:
Code:
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:
Code:
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 linkAnd: 388.8 Routes:
Code:
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.2Unfortunately 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.
Last edited:
ExtremeFiretop
Very Senior Member
I should also mention that I am using the Wireguard VPN on the primary router with VPN Director, and I do have the node set to bypass the VPN so I can access it from my desktop also bypassing the VPN:
But these same rules work fine on 388.8_4 and no changes are made, and the TV is not added to this list.
But these same rules work fine on 388.8_4 and no changes are made, and the TV is not added to this list.
visortgw
Very Senior Member
Just for grins, have you tried the latest Asus baseline firmware for the GT-AXE11000 on the AiMesh node? I have the same GT-BE98 Pro as you for primary router with latest Merlin firmware, and I am using latest Asus baseline 3.0.0.4.388_24403-g48ccb61 firmware on my GT-AXE16000 AiMesh node. I see the same 239.0.0.0/8 route on the AiMesh node as you do with the Merlin alpha, but I am NOT having issues with 5 Gb device connections.
ExtremeFiretop
Very Senior Member
Interesting, no I have not tried the stock firmware. I may give it a go to see.
I didn't expect the route to be an issue either, it's just a multicast route but I figured I'd check routes since I know this update included changes to Wireguard which I am using.
Tbh I ran out of time to poke until I had to get stuff up and running again. I'll flash the baseline stock firmware and test again.
ExtremeFiretop
Very Senior Member
ExtremeFiretop
Very Senior Member
And back to this alpha; the issue with 5GHz is found on the node again:
ExtremeFiretop
Very Senior Member
And follow up question.. As a node? Or Primary router?
As a node is how mine is operating.
Last edited:
ExtremeFiretop
Very Senior Member
Okay thanks; that additional clarification helps narrow down further.
Similar threads
- Locked
Similar threads
Similar threads
-
-
robocfg Not Available on Asus GT-AXE11000 (Asuswrt-Merlin 388.8_4)?- Started by garycnew
- Replies: 9
-
-
Not seeing any server certificate information on the ddns page after changing ASUS official firmware to 3004.388.8_4-gnuton1.
- Started by scootertramp
- Replies: 0
-
Bell Fibe (Canada) with Asus RT-AX88U Pro running firmware 3004.388.8_4 appears throttled- Started by Philip Bondi
- Replies: 15
-
-
-
Losing internet every 10 days or so with Telus ISP and RT-AX86U (Merlin 3004.388.8_4)- Started by tallytr
- Replies: 42
-
-
Latest threads
-
-
AXE16000 connected but without internet- Started by Thermaltake
- Replies: 0
-
-
-
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!