How to monitor auto channel selection over time

[MKLBNS]

My Asus devices (RT-AX88U & RT-AX82U) are using auto control channel settings, including the DFS channels.

I would like to see over a longer period of time (e.g. 2 weeks) which channels are used before the Automatic Channel Selection Daemon (acsd) decides it needs to move to another channel.

What is the easiest way to accomplish this? The content of /tmp/syslog.log or /tmp/syslog.log-1 only captures approximately 48h of logging.

 

[JGrana]

Yes, what we need is ChannelMon! Email/Alert/Log when the acsd decides to move to a different channel.
Or maybe an addition to rtrmon.

@Viktor Jaep ?

 

[Viktor Jaep]

Yes, what we need is ChannelMon! Email/Alert/Log when the acsd decides to move to a different channel.
Or maybe an addition to rtrmon.

@Viktor Jaep ?

Something like this might be a good start?

RT-AX86U doesn't switch back to DFS channel

So I use a DFS channel with my RT-AX86U. Every few months, the router switches to a non-DFS channel, I guess it detected radar. But then it doesn't switch back, and I have to manually switch it back (by resetting it) after noticing the lower quality of the non-DFS channel, which where I am is...

www.snbforums.com

 

[MKLBNS]

Ok... that channel_check.sh script could work, I would need to try it out if it also correctly handles "auto" control channel settings.

But too be honest... I am surprised, so not many people have ever wondered how Automatic Channel Selection Daemon (acsd) is doing its work? I want to know how often acsd is changing control channel but also how often it changes bandwidth (as that is also set to auto). Obviously directly related is the question: how often am I affected by DFS channel change.

 

[ColinTaylor]

Ok... that channel_check.sh script could work, I would need to try it out if it also correctly handles "auto" control channel settings.

I wrote that script. It writes its channel changes to syslog. But you said your syslog only holds about 48 hours of information. So you'd need to modify it so that it logs the information to somewhere else.

However, the purpose of the script is to move the channel back to what you have set in the webUI if it changes. Obviously it can't do that if the channel is set to "Auto". So you'd need to further modify the script. You'd probably be better off by just scraping the syslog for the relevant messages put out by the wireless driver and acsd.