[damo2k]

Ok so I applied some settings or configuration changes as recommended in the thread linked below and it seems to have resolved the issue. At least the system didn’t have the permanent disconnects for over 10 days now where as before they were coming back every few days.

I’m still not sure why these settings fix the issue, and why the issue only started since putting the primary node into PPPoE mode.

Here is the thread, and I have copied below in case it goes down or disappears.

• set Backhaul Connection Priority to “5GHz-2 Wifi first” (probably not relevant for you since you’re wired)
• set 2.4GHz bandwidth to 20MHz
• fix control channels on 2.4GHz/5GHz-1/5GHz-2 bands to 1, 36, and 149, respectively
• disable Universal Beamforming on all bands
• disable Roaming Assistant on 5GHz-2 band (again, probably not relevant for you since you’re not using it as backhaul)

You need to login in order to vote

[damo2k]

Yeah I did a hard factory reset on both devices when changing over to PPPoE. I even swapped the devices around. I.e. node to primary and primary to node and factory reset.

The static IP suggestion on SNB Forums unfortunately hasn’t improved the situation.

• This reply was modified 1 year, 3 months ago by damo2k.

Liked by:

You need to login in order to vote

[damo2k]

Hmm not to long after firmware upgrade and rebooting, the issue came back! Trying the original setup will be the next step, i.e. switching back from wireless router mode to AP mode and bridging to the ISP router. Disappointing for such an expensive piece of kit.

• This reply was modified 1 year, 3 months ago by damo2k.

You need to login in order to vote

[damo2k]

I’m not feeling too optimistic about that, as I have experienced this issue across at least 2 previous firmware versions! I have a feeling the router is behaving unexpectedness since I started using it with PPPoE.

I will try using the original ISP modem/router for PPPoE at some stage and bridge to the Asus primary, should the problem return, to see if it makes any difference.

Liked by:

You need to login in order to vote

[damo2k]

Yeah its HW version 1.0.

The labels on the bottom of the devices show a date of 2022, but show HW Ver: 1.0. The box also shows HW Ver: 1.0 with a date of 2022.

Also on the router terminal, I see similar:

admin@ZenWiFi_XT8-42E0:/# nvram show | grep HwVer
HwVer=1.0

admin@ZenWiFi_XT8-42E0:/# nvram show | grep DCode
DCode=20220215

Note: I have since upgraded the firmware to version: 3.0.0.4.388_24688-gf94212b

• This reply was modified 1 year, 3 months ago by damo2k.

You need to login in order to vote

[damo2k]

On the bottom of both devices it shows HW Ver: 1 Is there anywhere else to check?

You need to login in order to vote

[damo2k]

Most are connected to the Node. The baby monitor was connected to the primary up till tonight, as I since moved the monitor.

Both XT8 devices are on FW: 3.0.0.4.388_24684. I seem to have the V1 hardware. This issue seems to have remained across the last 1 or 2 firmware versions.

• This reply was modified 1 year, 3 months ago by damo2k.

You need to login in order to vote

[damo2k]

Yup its full fiber via an ONT. Yup I have one set as the primary, and the other as a node. The backhauls are connected via the 2nd 5Ghz network.

The only thing that has changed is that the Primary is now using PPPoE to the ONT directly, where as before it was simply connected to the ethernet port of the Virgin Media router that was in bridged-mode. This is when it seems the problems started. Maybe the XT8 has issues with operation and PPPoE.

You need to login in order to vote

[damo2k]

UK Sentinel wrote:

Weekend, maybe no flights

The regional airport about 5km definately had small planes whizzing around yesterday and today. And Dublin international airport is about 23km away (as the crow flies). The international planes regularly fly overhead and quite low (not sure exactly how low), I guess they are coming in for landing or climbing over our neighbourhood a lot. No mention of ‘radar detected’ in the logs, so not sure if it’s just a case of lucky timing, regarding radar interferences so far, or if they are too high. No fallback to 2.4Ghz backhaul yet though.

You need to login in order to vote

[damo2k]

UK Sentinel wrote:

Did you use app or browser ? For your DFS issues, probable best just to disable the DFS option on your ASUS XT8 and see if this then stops any further disconnects

I used the browser this time. I don’t seem to have any DFS issues, at least not yet. But yes, I will try this option should it start acting up again. Still no mention of ‘radar’ in the logs, and stil on 5Ghz-2 backhaul. I will keep an eye on it and post again if there are any updates.

You need to login in order to vote

[damo2k]

Ok so this morning the node went “offline” again with the constant blinking blue LED. There was nothing in the logs showing “radar”.

Therefore I started the process of downgrading the firmware on the router and node to 386.49873 and do a factory reset on both.

I did the router first, downgrade, factory reset, then setup. I then unplugged it and moved onto the node. It was quite difficult to connect to the node, as the blue LED kept flashing after startup, even after factory resetting a few times. I eventually was able to connect over ethernet to flash the older firmware, let it reboot and did a factory reset. The blue led flashing came back (on the older firmware!), and seemed to periodically restart itself. I did another factory reset and turned on the primary router. Eventually the node started up connected up to the mesh network itself. I though I would have to trigger this or at least hint that this is how I wanted it to operate, but it just joined the mesh network itself which was a bit strange, no? Hopefully there is no underlying hardware issue with the node.

Anyway both have been running for a few hours. Router and node are still in same locations in the house. I haven’t moved them closer to each other yet. The are still connected via the 5GHZ-2 backhaul. The signal hovers between -62 to -69dBm (Great) and -70 to -72dBm (Good). I was able to achieve 501.87Mbps download and 51.22Mbps upload over wifi while connected to the node (verified I was connected to the node via the app). This is on a Virgin Media 500Mb/50Mb account. Hopefully the issues were only caused by the 388.21099 firmware. I guess time will tell.

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

[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

[damo2k]

Since upgrading the firmware to 3.0.0.4.388.21099 on my AX8 (2x). I am having issues where sometimes the AX8 node (not the one acting as a router), has a blue light flashing constantly. When I factory reset both the router and node, they will connect to each other again using the 5GHZ-2 back haul. However it will eventually go back and stick with using the 2.4ghz as the back haul. The routers are not a massive distance between each other. One down stairs, one upstairs in a wooden framed house. This issue only seems to have started happening after upgrading to 3.0.0.4.388.21099. Anyone else experiencing the same?

You need to login in order to vote

[Author]

Posts