Asus DFS algorithm

[OzarkEdge]

No dice, tried multiple ways / intermediate saves etc all end up with the DFS control preselected if channel width selection is only 160mhz.

Anyway I'm moving on for now with leaving it auto and let it drop to 80 and stay there. In the past week DFS hits almost every other day.

Would have looked similar to this:

OE

 

[fast08]

Would have looked similar to this:
View attachment 64224

OE

Oh, I was able to get to that. Just not "Auto" next to "Control Channel".
FWIW, I tried setting it to the same channel as my neighbor and it does result in neighbor's AP moving away from my fixed channel. But it doesn't resolve my DFS problems. Just a few hours ago my router went back to 80MHz.

 

[OzarkEdge]

Oh, I was able to get to that. Just not "Auto" next to "Control Channel".
FWIW, I tried setting it to the same channel as my neighbor and it does result in neighbor's AP moving away from my fixed channel. But it doesn't resolve my DFS problems. Just a few hours ago my router went back to 80MHz.

This is as close as I can get:

Setting the router max bandwidth to 20/40/80/160MHz ('auto') allows setting the control channel to Auto non-DFS. This would ensure that clients that do not support UNII-2a DFS frequencies can still connect to a non-DFS control channel at 80MHz max bandwidth, while clients that support UNII-2a DFS frequencies can connect at 160MHz bandwidth for as long as RADAR/DFS permits... apparently not very long at your location.

Auto control channel permits the router to find the least congested control channel... and play musical chairs with your neighbor.

20/40/80/160MHz ('auto') max bandwidth permits the router to also reduce the max bandwidth to avoid radio interference (for better connection performance), similar to what DFS does to avoid RADAR.

I'd try fixing a control channel in UNII-1 non-DFS and 160MHz max bandwidth (post #21). All clients will connect at their max bandwidth (mostly 80MHz or less) and those that support UNII-2a will connect at 160MHz bandwidth until RADAR/DFS forces them to drop back to 80MHz non-DFS. The fixed control channel will stay put and eventually force your neigbor to move away from it, avoiding Auto disruption of client connections. And the fixed 160MHz max bandwidth will drop to 80MHz max bandwidth per DFS regulation, but it will not drop further to avoid non-DFS radio interference... likely not a problem... and clients will still connect at their max bandwidth.

Conventional wisdom is to set 80MHz max for better range/Tx power and no DFS disruption... although you may not need better range there.

That is how I see it and simplify it!

OE

 

[fast08]

Auto control channel permits the router to find the least congested control channel... and play musical chairs with your neighbor.

20/40/80/160MHz ('auto') max bandwidth permits the router to also reduce the max bandwidth to avoid radio interference (for better connection performance), similar to what DFS does to avoid RADAR.

Thanks OE ! That's what I'm settling on for now

I'd try fixing a control channel in UNII-1 non-DFS and 160MHz max bandwidth (post #21). All clients will connect at their max bandwidth (mostly 80MHz or less) and those that support UNII-2a will connect at 160MHz bandwidth until RADAR/DFS forces them to drop back to 80MHz non-DFS. The fixed control channel will stay put and eventually force your neigbor to move away from it, avoiding Auto disruption of client connections. And the fixed 160MHz max bandwidth will drop to 80MHz max bandwidth per DFS regulation, but it will not drop further to avoid non-DFS radio interference... likely not a problem... and clients will still connect at their max bandwidth.

Conventional wisdom is to set 80MHz max for better range/Tx power and no DFS disruption... although you may not need better range there.

That is how I see it and simplify it!

OE

Planning to keep it auto for a few days and try the fixed non-dfs control channel.