Menu
What's new
By:
Filters Better Search

Release ASUS RT-AX86U Firmware version 3.0.0.4.386_49447 (2022/06/20)

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

I'm not choosing any DFS channels and I don't even get the option to select one b/c I have 160Mhz hard-coded. Otherwise, my 2 AX devices only connect at 80mhz. Do you have an AIMesh client?


1657399838635.png


or:

no dfs.jpg
 
SteverinoLA said:
I'm not choosing any DFS channels and I don't even get the option to select one b/c I have 160Mhz hard-coded. Otherwise, my 2 AX devices only connect at 80mhz. Do you have an AIMesh client?
Click to expand...

Yes, I have an AiMesh client node... see my signature.

You are setting a non-DFS control channel, but notice that your log entries are scanning for 160MHz bw... to use 160MHz bw, it must use DFS channels/radio spectrum in the U-NII-2a band. I was wondering if the log entries have anything to do with you not being able to select 2a band channels... if those DFS channels are missing for you, are they also missing for the scanning process. Surely your AX node supports the 2a band(?)... why would an AX router be so hobbled as to not support the 2a band... WiFI6 is hobbled enough as it is with only two 160MHz options and only one of those able to support legacy clients rquiring non-DFS control channels.

OE
 
Well the AX55 (my mesh client) is at the bottom end of the Asus line. If I remove it as AIMesh client, then my 86U get DFS channels back including when I hard-code 160Mhz. My wireless is interesting (I think). It's checking 36 for radar but 36 isn't a DFS channel, right?

Code: 
SSID: "Steverino 5G"
noise: -85 dBm    Channel: 36/160
BSSID: 7C:10:C9:B3:9B:94    Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
    Chanspec: 5GHz channel 50 160MHz (0xe832)
    Primary channel: 36
    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:
        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

Interference Level: Acceptable
Mode    : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 160800ms radar channel cleared by DFS channel 36/160 (0xE832)

Channel Information                    
----------------------------------------
Channel 36    A Band
Channel 40    A Band
Channel 44    A Band
Channel 48    A Band
Channel 52    A Band, RADAR Sensitive
Channel 56    A Band, RADAR Sensitive
Channel 60    A Band, RADAR Sensitive
Channel 64    A Band, RADAR Sensitive
Channel 100    A Band, RADAR Sensitive, Passive
Channel 104    A Band, RADAR Sensitive, Passive
Channel 108    A Band, RADAR Sensitive, Passive
Channel 112    A Band, RADAR Sensitive, Passive
Channel 116    A Band, RADAR Sensitive, Passive
Channel 120    A Band, RADAR Sensitive, Passive
Channel 124    A Band, RADAR Sensitive, Passive
Channel 128    A Band, RADAR Sensitive, Passive
Channel 132    A Band, RADAR Sensitive, Passive
Channel 136    A Band, RADAR Sensitive, Passive
Channel 140    A Band, RADAR Sensitive, Passive
Channel 144    A Band, RADAR Sensitive, Passive
Channel 149    A Band
Channel 153    A Band
Channel 157    A Band
Channel 161    A Band
Channel 165    A Band

Stations List                          
----------------------------------------
idx MAC               Associated Authorized   RSSI PHY PSM SGI STBC MUBF NSS   BW Tx rate Rx rate Connect Time
    :10:D9 Yes        Yes        -54dBm ac  No  Yes Yes  Yes    1  80M    390M  433.3M     09:35:55
    :41:31 Yes        Yes        -64dBm ac  Yes Yes Yes  No     1  80M  433.3M     24M     09:57:54
    :3C:CD Yes        Yes        -56dBm ac  Yes Yes Yes  Yes    1  80M  433.3M      6M     10:13:46
    :05:48 Yes        Yes        -47dBm ac  No  Yes Yes  No     1  80M  433.3M    325M     10:51:26
    :6C:6E Yes        Yes        -41dBm ac  Yes Yes Yes  No     2  80M    780M  433.3M     17:01:46
    :79:13 Yes        Yes        -54dBm ac  No  Yes Yes  No     2  80M  866.7M  175.5M     17:01:55
    :76:21 Yes        Yes        -69dBm ax  Yes Yes Yes  Yes    2 160M 2161.8M      6M     17:02:42
    :9D:0F Yes        Yes        -49dBm ax  Yes Yes Yes  Yes    2 160M 1921.5M      6M     17:03:29
    :A2:36 Yes        Yes        -51dBm ac  No  Yes Yes  Yes    1  80M    325M    390M     17:03:29
 
Last edited:
SteverinoLA said:
Well the AX55 (my mesh client) is at the bottom end of the Asus line. If I remove it as AIMesh client, then my 86U get DFS channels back including when I hard-code 160Mhz.
Click to expand...

Would you buy it again? :)

You should stick with 80MHz.

OE
 
SteverinoLA said:
Well the AX55 (my mesh client) is at the bottom end of the Asus line. If I remove it as AIMesh client, then my 86U get DFS channels back including when I hard-code 160Mhz. My wireless is interesting (I think). It's checking 36 for radar but 36 isn't a DFS channel, right?

Code: 
SSID: "Steverino 5G"
noise: -85 dBm    Channel: 36/160
BSSID: 7C:10:C9:B3:9B:94    Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
    Chanspec: 5GHz channel 50 160MHz (0xe832)
    Primary channel: 36
    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:
        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

Interference Level: Acceptable
Mode    : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 160800ms radar channel cleared by DFS channel 36/160 (0xE832)

Channel Information                   
----------------------------------------
Channel 36    A Band
Channel 40    A Band
Channel 44    A Band
Channel 48    A Band
Channel 52    A Band, RADAR Sensitive
Channel 56    A Band, RADAR Sensitive
Channel 60    A Band, RADAR Sensitive
Channel 64    A Band, RADAR Sensitive
Channel 100    A Band, RADAR Sensitive, Passive
Channel 104    A Band, RADAR Sensitive, Passive
Channel 108    A Band, RADAR Sensitive, Passive
Channel 112    A Band, RADAR Sensitive, Passive
Channel 116    A Band, RADAR Sensitive, Passive
Channel 120    A Band, RADAR Sensitive, Passive
Channel 124    A Band, RADAR Sensitive, Passive
Channel 128    A Band, RADAR Sensitive, Passive
Channel 132    A Band, RADAR Sensitive, Passive
Channel 136    A Band, RADAR Sensitive, Passive
Channel 140    A Band, RADAR Sensitive, Passive
Channel 144    A Band, RADAR Sensitive, Passive
Channel 149    A Band
Channel 153    A Band
Channel 157    A Band
Channel 161    A Band
Channel 165    A Band

Stations List                         
----------------------------------------
idx MAC               Associated Authorized   RSSI PHY PSM SGI STBC MUBF NSS   BW Tx rate Rx rate Connect Time
    :10:D9 Yes        Yes        -54dBm ac  No  Yes Yes  Yes    1  80M    390M  433.3M     09:35:55
    :41:31 Yes        Yes        -64dBm ac  Yes Yes Yes  No     1  80M  433.3M     24M     09:57:54
    :3C:CD Yes        Yes        -56dBm ac  Yes Yes Yes  Yes    1  80M  433.3M      6M     10:13:46
    :05:48 Yes        Yes        -47dBm ac  No  Yes Yes  No     1  80M  433.3M    325M     10:51:26
    :6C:6E Yes        Yes        -41dBm ac  Yes Yes Yes  No     2  80M    780M  433.3M     17:01:46
    :79:13 Yes        Yes        -54dBm ac  No  Yes Yes  No     2  80M  866.7M  175.5M     17:01:55
    :76:21 Yes        Yes        -69dBm ax  Yes Yes Yes  Yes    2 160M 2161.8M      6M     17:02:42
    :9D:0F Yes        Yes        -49dBm ax  Yes Yes Yes  Yes    2 160M 1921.5M      6M     17:03:29
    :A2:36 Yes        Yes        -51dBm ac  No  Yes Yes  Yes    1  80M    325M    390M     17:03:29
Click to expand...

Your WLog indicates cleared for 36/160 using DFS channels, and you have ax 160MHZ client connections. I guess your AX node is removed/not one of them.

OE
 
OzarkEdge said:
Would you buy it again? :)

You should stick with 80MHz.

OE
Click to expand...
Nope! and I didn't buy. We get them free from our internet provider as part of our service contract, so I got 3 of them. Tried it out as main router and immediately bumped it up to 86U (after reading up in this forum and site). AX55 and 256MB RAM is so under-spec'd. So many out of memory errors if I dared try anything like AIProtection., site history, etc.

My internet is 500/500 so you're probably right that 160Mhz isn't doing anything for me except make me happy when I look at the wireless log, lol.
 
SteverinoLA said:
With this firmware my 86U no longer shows or support any DFS channels... as soon as I add my AX55 as an AIMesh client. This wasn't the case in prior releases. Is it the same for everyone else? Surely, I'm not the only one w/an 86U and a lower-end AX AIMesh client. I can't remember, does the AX55 support DFS channels? And also, my log is filled completely with this set of errors repeating every half hour or so:

Jul 9 11:55:47 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe832 (36/160)
Jul 9 11:55:47 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
Jul 9 11:55:47 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe832 (36/160)
Jul 9 11:55:47 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xe932 (40/160)
Jul 9 11:55:47 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
Jul 9 11:55:47 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xe932 (40/160)
Jul 9 11:55:47 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xea32 (44/160)
Jul 9 11:55:47 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
Jul 9 11:55:47 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xea32 (44/160)
Jul 9 11:55:47 acsd: acs_candidate_score_intf(1108): eth7: intf check failed for chanspec: 0xeb32 (48/160)
Jul 9 11:55:47 acsd: acs_candidate_score_bgnoise(1573): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
Jul 9 11:55:47 acsd: acs_candidate_score_txop(1831): eth7: txop check failed for chanspec: 0xeb32 (48/160)
Click to expand...
Your AX55 does not do DFS channels. It only has 20/40/80 MHz bandwidth. Therefore when you add it as an AiMesh node the AX86U is restricted to the channels the node can do. At least that is my experience with adding an AC66U_B1 as a node.
 
SteverinoLA said:
Well the AX55 (my mesh client) is at the bottom end of the Asus line. If I remove it as AIMesh client, then my 86U get DFS channels back including when I hard-code 160Mhz. My wireless is interesting (I think). It's checking 36 for radar but 36 isn't a DFS channel, right?

Code: 
SSID: "Steverino 5G"
noise: -85 dBm    Channel: 36/160
BSSID: 7C:10:C9:B3:9B:94    Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
    Chanspec: 5GHz channel 50 160MHz (0xe832)
    Primary channel: 36
    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:
        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

Interference Level: Acceptable
Mode    : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 160800ms radar channel cleared by DFS channel 36/160 (0xE832)

Channel Information                   
----------------------------------------
Channel 36    A Band
Channel 40    A Band
Channel 44    A Band
Channel 48    A Band
Channel 52    A Band, RADAR Sensitive
Channel 56    A Band, RADAR Sensitive
Channel 60    A Band, RADAR Sensitive
Channel 64    A Band, RADAR Sensitive
Channel 100    A Band, RADAR Sensitive, Passive
Channel 104    A Band, RADAR Sensitive, Passive
Channel 108    A Band, RADAR Sensitive, Passive
Channel 112    A Band, RADAR Sensitive, Passive
Channel 116    A Band, RADAR Sensitive, Passive
Channel 120    A Band, RADAR Sensitive, Passive
Channel 124    A Band, RADAR Sensitive, Passive
Channel 128    A Band, RADAR Sensitive, Passive
Channel 132    A Band, RADAR Sensitive, Passive
Channel 136    A Band, RADAR Sensitive, Passive
Channel 140    A Band, RADAR Sensitive, Passive
Channel 144    A Band, RADAR Sensitive, Passive
Channel 149    A Band
Channel 153    A Band
Channel 157    A Band
Channel 161    A Band
Channel 165    A Band

Stations List                         
----------------------------------------
idx MAC               Associated Authorized   RSSI PHY PSM SGI STBC MUBF NSS   BW Tx rate Rx rate Connect Time
    :10:D9 Yes        Yes        -54dBm ac  No  Yes Yes  Yes    1  80M    390M  433.3M     09:35:55
    :41:31 Yes        Yes        -64dBm ac  Yes Yes Yes  No     1  80M  433.3M     24M     09:57:54
    :3C:CD Yes        Yes        -56dBm ac  Yes Yes Yes  Yes    1  80M  433.3M      6M     10:13:46
    :05:48 Yes        Yes        -47dBm ac  No  Yes Yes  No     1  80M  433.3M    325M     10:51:26
    :6C:6E Yes        Yes        -41dBm ac  Yes Yes Yes  No     2  80M    780M  433.3M     17:01:46
    :79:13 Yes        Yes        -54dBm ac  No  Yes Yes  No     2  80M  866.7M  175.5M     17:01:55
    :76:21 Yes        Yes        -69dBm ax  Yes Yes Yes  Yes    2 160M 2161.8M      6M     17:02:42
    :9D:0F Yes        Yes        -49dBm ax  Yes Yes Yes  Yes    2 160M 1921.5M      6M     17:03:29
    :A2:36 Yes        Yes        -51dBm ac  No  Yes Yes  Yes    1  80M    325M    390M     17:03:29
Click to expand...
Right, ch 36 is not DFS but with 160 MHz set the router still has to clear for RADAR as the 160 MHz pushes into the DFS channels. If you are in an area where there is RADAR traffic you are better off to use 20-40-80-160 MHz. Then when the router detects radar it can go back to 80 MHz which will not use DFS channels and keep working. With 160 MHz set the 5 GHz band will be off for a few minutes on router reboot until it clears for RADAR.
 
bbunge said:
Your AX55 does not do DFS channels. It only has 20/40/80 MHz bandwidth. Therefore when you add it as an AiMesh node the AX86U is restricted to the channels the node can do. At least that is my experience with adding an AC66U_B1 as a node.
Click to expand...

Understood, but this wasn't the case prior to the very recent firmware updates (both 86U and AX55 got them). Previously, I could see and set 86U DFS channels when AX55 is AIMesh client. Now no DFS allowed on 86U with AX55 AIMesh. I guess I could try setting AX55 to AP rather than AIMesh and see what happens.
 
bbunge said:
Right, ch 36 is not DFS but with 160 MHz set the router still has to clear for RADAR as the 160 MHz pushes into the DFS channels. If you are in an area where there is RADAR traffic you are better off to use 20-40-80-160 MHz. Then when the router detects radar it can go back to 80 MHz which will not use DFS channels and keep working. With 160 MHz set the 5 GHz band will be off for a few minutes on router reboot until it clears for RADAR.
Click to expand...

Ah, that explains my wireless log:

SSID: "Steverino 5G"
noise: -84 dBm Channel: 36/160
BSSID: 7C:10:C9:B3:9B:94 Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
Chanspec: 5GHz channel 50 160MHz (0xe832)
Primary channel: 36
HT Capabilities: 40Mhz SGI20 SGI40

Auto has select channel 36 but also using channel 50 (which is DFS, right?) due to my 2 AX clients. What is channel 50? It's not even listed as an available channel or DFS channel also in log:

DFS status: state In-Service Monitoring(ISM) time elapsed 126000ms radar channel cleared by DFS channel 36/160 (0xE832)

Channel Information
----------------------------------------
Channel 36 A Band
Channel 40 A Band
Channel 44 A Band
Channel 48 A Band
Channel 52 A Band, RADAR Sensitive
Channel 56 A Band, RADAR Sensitive
Channel 60 A Band, RADAR Sensitive
Channel 64 A Band, RADAR Sensitive
Channel 100 A Band, RADAR Sensitive, Passive
Channel 104 A Band, RADAR Sensitive, Passive
Channel 108 A Band, RADAR Sensitive, Passive
Channel 112 A Band, RADAR Sensitive, Passive
Channel 116 A Band, RADAR Sensitive, Passive
Channel 120 A Band, RADAR Sensitive, Passive
Channel 124 A Band, RADAR Sensitive, Passive
Channel 128 A Band, RADAR Sensitive, Passive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive
Channel 144 A Band, RADAR Sensitive, Passive
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band
 
SteverinoLA said:
Auto has select channel 36 but also using channel 50 (which is DFS, right?) due to my 2 AX clients. What is channel 50?
Click to expand...

These FCC-US Unlicensed Spectrum graphics show the center channel (radio frequency) for each bandwidth. Ch 50 is the center frequency (aka channel) for 160MHz bw across the N-NII-1,2a bands... half non-DFS channels, half-DFS channels... the only WiFi6 option for 160MHz bw using a non-DFS control channnel, 36-48.

Your log shows control channel 36 and bandwidth 160, 36/160. Your router should be broadcasting a 36/160 WLAN... presumably your AX55 node is broadcasting a 36/80 WLAN since it presumably can't do DFS channels 52-64.

OE
 
Last edited:
would everyone recommend adguard to block utube adds with the new Assign a DNS feature?
 
No, not everyone would. You do mean YouTube, correct?
 
I cannot select DFS control channels 120,124,128. This makes me wonder if this firmware permits a 160MHz bw connection in the U-NII-2c band, spanning channels 100-128(?).

OE
 
L&LD said:
No, not everyone would. You do mean YouTube, correct?
Click to expand...
Tech9 said:
You can't block YouTube ads with DNS-based ad-blockers. Use uBlock Origin browser extension.
Click to expand...

Yes youtube, and mainly for for the TV app. I thought that the global dns settings from the router would help.
 
SeriousFamily said:
would everyone recommend adguard to block utube adds with the new Assign a DNS feature?
Click to expand...

I had no idea about the free Adguard DNS servers until this firmware release added the list of DNS servers. For me, it's the greatest thing ever -- whole home ad blocking for every device. I've disabled AdBlock browser extensions and AdGuard app on Android devices. I pay for YouTube Premium/YT Music so no ads in those apps.
 
SteverinoLA said:
I had no idea about the free Adguard DNS servers until this firmware release added the list of DNS servers. For me, it's the greatest thing ever -- whole home ad blocking for every device.
Click to expand...

It was very good of ASUS to include/highlight these. I'm beyond content filtering, but many home networks will use it.

OE
 
You must log in or register to reply here.

Similar threads

D
Release Asus RT- AX58U Firmware 386.49674 (7-21-2022)
2
Replies
37
Views
7K
Stpa67
S
visortgw
Release ASUS RT-AX58U Firmware version 3.0.0.4.388_23556 (2023/06/20)
Replies
0
Views
2K
visortgw
visortgw
xander73
Release ASUS TUF-AX6000 Firmware version 3.0.0.4.388_32271 (2023/06/20)
Replies
0
Views
1K
xander73
xander73
bbunge
Release Asus RT-AX86U Pro Firmware version 3.0.0.4_388_23565 (2023-06-20)
Replies
16
Views
3K
full-duplex
full-duplex
E
Release ASUS RT-AX3000 Firmware version 3.0.0.4.388_23556 (2023/06/20)
Replies
9
Views
3K
piotreek
P
Similar threads
Thread starter Title Forum Replies Date
B Release ASUS RT-AX86U Pro Firmware version 3.0.0.4.388_24199 (2024-01-04) ASUSWRT - Official 5
bbunge Release ASUS RT-AX86U Pro Firmware version 3.0.0.4.388_24198 08NOV23 ASUSWRT - Official 10
K Asus AX86U Pro Firmware ASUSWRT - Official 17
Smokey613 ASUS RT-AX86U Pro Firmware version 9.0.0.6.102.4856 ASUSWRT - Official 6
bbunge Release Asus RT-AX86U Pro Firmware version 3.0.0.4_388_23565 (2023-06-20) ASUSWRT - Official 16
M how to know when beta firmware makes it into production firmware for example ASUS RT-AX86U Pro Firmware version 9.0.0.6.102.4856 ASUSWRT - Official 4
T Release ASUS RT-AX86 Series(RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388.23285 (15-05-2023) ASUSWRT - Official 218
bbunge Release ASUS RT-AX86U Pro Firmware version 3.0.0.4.388.23285 ASUSWRT - Official 13
A Asus RT-AX86U Pro ASUSWRT - Official 11
R Asus RT-AX86U error: acs_start eth7 cannot select chanspec with the wrong info ASUSWRT - Official 39

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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

Staff online

Members online

Total: 1,076 (members: 25, guests: 1,051)
Top