ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above. Has anyone used this and does it...

[UK Sentinel]

dodgydrains wrote:

I have gone ahead and updated the router as well now .

Brave, 4+ days and we should know 

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[dodgydrains]

dodgydrains wrote:

Everything seems fine for now, but obviously there probably will be no Parental Controls as it is beta.

Looks like Parental Control is activated on the beta.  If there are no lock ups, I will stay on this beta FW.

Liked by:

You need to login in order to vote

[TomThumb]

After a positive start running 21268,

I’m back to the general release fw 21099 on both my router & node.

Trying to access web history is still crashing the router after a a couple of days, so being no better off I’ve rolled the fw back.

Tom…

 

Liked by:

You need to login in order to vote

[UK Sentinel]

dodgydrains wrote:

Looks like Parental Control is activated on the beta. If there are no lock ups, I will stay on this beta FW.

That is reassuring, by Monday we should know if stability is good also 👌

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[UK Sentinel]

TomThumb wrote:

I’m back to the general release fw 21099 on both my router & node.

may need to go back to Version 3.0.0.4.386.49873 to see if that works better ?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[damo2k]

I haven’t rolled back yet, as working from home during the day. Will be a weekend job!

However I have the following entries are in the general log matching “Radar” in the logs around the 19th, but nothing from the 20th, or 21st (so far). However the issue seems to be persistent. Nothing matching “DFS”.

Oct 19 14:12:05 amas_adtbw: [ADTBW]Radar detected, wait for radar timeout
Oct 19 14:37:05 amas_adtbw: [ADTBW]Radar timeout
Oct 19 14:37:05 amas_adtbw: [ADTBW]Try to extend bw to 160
Oct 19 14:37:05 amas_adtbw: [ADTBW]ret 0
Oct 19 21:51:19 wlceventd: wlceventd_proc_event(657): eth6: Radar detected
Oct 19 21:58:12 amas_adtbw: [ADTBW]Radar detected, wait for radar timeout
Oct 19 22:23:12 amas_adtbw: [ADTBW]Radar timeout
Oct 19 22:23:12 amas_adtbw: [ADTBW]Try to extend bw to 160
Oct 19 22:23:12 amas_adtbw: [ADTBW]ret 1

 

And the Wireless log:

SSID: “(truncated)”
noise: -93 dBm Channel: 5
BSSID: 04:42:1A:72:45:30 Capability: ESS ShortSlot RRM
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
HE Capable:
Chanspec: 2.4GHz channel 5 20MHz (0x1005)
Primary channel: 5
HT Capabilities: 40Mhz SGI20 SGI40
Supported HT MCS : 0-15
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 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

Interference Level: Acceptable
Mode : AP Only

Stations List
—————————————-
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS BW Tx rate Rx rate Connect Time
(truncated) Yes Yes -58dBm ax No Yes Yes No 2 20M 286.8M 258.1M 35:03:26

SSID: “(truncated)”
noise: -88 dBm Channel: 60/80
BSSID: 04:42:1A:72:45:34 Capability: ESS RRM
Supported Rates: [ 6(b) 9 12 18 24(b) 36 48 54 ]
HE Capable:
Chanspec: 5GHz channel 58 80MHz (0xe23a)
Primary channel: 60
HT Capabilities: 40Mhz SGI20 SGI40
Supported HT MCS : 0-15
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 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

Interference Level: Acceptable
Mode : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 124154700ms radar channel cleared by DFS channel 60/80 (0xE23A)

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

Stations List
—————————————-
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS BW Tx rate Rx rate Connect Time
(truncated) Yes Yes -66dBm ac No Yes Yes No 1 80M 292.5M 325M 06:05:07

SSID: “(truncated)_dwb”
noise: -87 dBm Channel: 116/80
BSSID: (truncated) Capability: ESS RRM
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
HE Capable:
Chanspec: 5GHz channel 122 80MHz (0xe07a)
Primary channel: 116
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 124414200ms radar channel cleared by DFS channel 116/80 (0xE07A)

Channel Information
—————————————-
Channel 100 A Band, RADAR Sensitive
Channel 104 A Band, RADAR Sensitive
Channel 108 A Band, RADAR Sensitive
Channel 112 A Band, RADAR Sensitive
Channel 116 A Band, RADAR Sensitive
Channel 120 A Band, RADAR Sensitive
Channel 124 A Band, RADAR Sensitive
Channel 128 A Band, RADAR Sensitive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive

Stations List
—————————————-
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS BW Tx rate Rx rate Connect Time

You need to login in order to vote

[UK Sentinel]

2 Part response I think,

R1 – when you set up your XT8, do you use app or browser ?

There was reports a while back that using app to configure ASUS XT8 and other kit caused the blue blinking light problem with disconnects etc.

R2 – DFS is a more interesting subject, unless you live near an airport or MoD facility etc, should not be a concern, but your logs do suggest otherwise.

FYI – When a router is started, for DFS it chooses a default Channel Bandwidth and Control Channel, then after a certain time (15 – 60 minuites) , if no DFS interference used by Military etc. is detected, then the ASUS router will increase Channel Bandwidth to a higher frequency which increases bandwidth etc. good for backhaul etc.

(it could be the other way around – I cannot recall)

Unless you experience regular wifi disconnects (wireless backhaul) I would not worry

 

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[damo2k]

UK Sentinel wrote:

R1 – when you set up your XT8, do you use app or browser ?

I used the app.

UK Sentinel wrote:

R2 – DFS is a more interesting subject, unless you live near an airport or MoD facility etc, should not be a concern, but your logs do suggest otherwise.

Hmm I have a small regional airport about 5km away from me, I wonder if this is causing me grief. Stranely I haven’t noticed this causing me issues until recently, and I have the router/nodes almost 6-7 weeks.

UK Sentinel wrote:

Unless you experience regular wifi disconnects (wireless backhaul) I would not worry

No disconnects, but there is a noticable bandwidth reduction when using the node thats connected to the main router using the backhaul on 2.4ghz. I’m typically getting around 400Mbps when connected to the main router, where as I am only getting around 100Mbps when connected to the node. When it uses the 5Ghz-2 backhaul, the speeds are negligible

 

 

 

You need to login in order to vote

[UK Sentinel]

damo2k wrote:

I used the app.

When you get a chance – try using a browser (Windows – Mac) on both XT8 units, factory reset and configure from scratch, just incase this helps (do not use any backups etc.)?

All in the name of science

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[UK Sentinel]

For you wireless backhaul, I assume it is defaulting to 2.4GHz as distance between main router (primary) and node is  to far or obstructed for 5GHz to work well, but we can tweak with wifi settings once you have factory reset over weekend  .

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[xt8user]

I have 3 XT8s (1 router, 2 nodes) currently on 388.21099. They are Ethernet connected. I would like to go back to 386.49873. I have a backup of the 386.49873 configuration. What is the best sequence of downgrading the units, reloading the saved database etc?

Thanks in advance.

You need to login in order to vote

[UK Sentinel]

xt8user wrote:

I have 3 XT8s (1 router, 2 nodes) currently on 388.21099

There are two approaches I feel, the quick and dirty method and the more involved factory reset approach.

1. Load 386.49873 to Nodes and reboot and then load 386.49873 to Primary and reboot. This should work but if you notice any issues, then option 2 will be required. This should not break mesh as you are using ethernet
2. Load 386.49873 to the Primary Router and then factory reset and configure from scratch, ‘not use backup’ and then perform same sequence on the 2 x nodes and also configure from scratch.

Note: Option 1. is quicker and simpler and usually works, but if you want to do the job correctly, full factory reset on Primary and Nodes is the best option.

(my view and I am sure others will have their own views)

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[xt8user]

UK Sentinel wrote:

Load 386.49873 to Nodes and reboot and then load 386.49873 to Primary and reboot. This should work but if you notice any issues, then option 2 will be required. This should not break mesh as you are using ethernet

I notice you don’t mention loading the 386.49873 backup in option 1.  Do you feel that is not useful?

Thanks for your help.

Liked by:

You need to login in order to vote

[UK Sentinel]

xt8user wrote:

I notice you don’t mention loading the 386.49873 backup in option 1.  Do you feel that is not useful?

Not really necessary unless you have issues  ?

In a completely sane world, madness is the only freedom (J.G.Ballard).

You need to login in order to vote

[Nicky]

Why are they still pushing “FW_ZENWIFI_XT8_300438821099” out via the router’s firmware upgrade option when they know there are issues with it?

I upgraded to “FW_ZENWIFI_XT8_300438821099” last week and had all kinds of stability issues, including devises no being able to connect to the router via wifi, so I regressed back to “FW_ZENWIFI_XT8_300438649873”. Now everything is back normal.

Liked by:

You need to login in order to vote

[Author]

Posts