I am so new to hAP ax3 and 5G in particular that I have no idea what changed intended channel to 5805/ax/eeeC means:
/interface/wifiwave2/print
Flags: M - MASTER; B - BOUND; R - RUNNING
Columns: NAME, MASTER-INTERFACE, CONFIGURATION.MODE, CONFIGURATION.SSID
# NAME MASTER-INTERFACE CONFIGURATION.MODE CONFIGURATION.SSID
;;; changed intended channel to 5805/ax/eeeC
0 MBR wifi1 ap Bird-Fake
1 B wifi1g wifi1 ap Bird-Real
2 MB wifi2 ap Fowl-Love
3 B wifi2g wifi2 ap Fowl-Hate
The two devices on the network have long running connections:
/interface/wifiwave2/registration-table/print
Flags: A - AUTHORIZED
Columns: INTERFACE, SSID, MAC-ADDRESS, UPTIME, SIGNAL
# INTERFACE SSID MAC-ADDRESS UPTIME SIGNAL
0 A wifi1 Bird-Fake A4:77:33:FA:4B:BE 9h10m26s -59
1 A wifi1 Bird-Fake A4:77:33:3C:8A:28 4h25m39s -49
I’m seeing my share of these on my Audience (ac device). My observation so far is that this happens if you manually confiugre frequency and channel layout (e.g. 5120 & Ceee) but ROS somehow decides this is not OK (perhaps due to radar detection). Sometimes I see only change in channel layout, but sometimes I see changed frequency as well.
I would expect ROS to obey maual setup and if it sees any critical problem with it, it should disable wireless interface … not simply change running value to something not confiugred.
You’re using automatic frequency selection, so the message is showing you what it selected in comment. What odd is it uses the word “changed”. Also seems to appear only when someone connects, which MAY effect channel width based on client & thus “changed”, dunno.
Also, if you don’t have a lot other Wi-Fi around, might consider using skip-dfs-channels=all.
Neighborhood is California suburban small single family homes.
SSID smart phone shows is around 25 plus or minus a few.
Chromecast and Chromecast Audio both very stable.
Google Nexus 6 phone is a horror show.
I once get that message when I had manually selected channel in DFS range. After 2 or 3 days I noticed radar detected in logs and this message was displayed.
If you don’t care about seeing top speed in a speed test, might just want to set the channel size to 20Mhz for both. At least to see if that make your Android phone happy. That limit a selection process getting involved. For AX, I’d leave auto – that is something it should do better with than 802.11ac, theoretically.
Google Nexus 6 still flaky on both radios.
What’s interesting is the occasional times it “locks in” at 5GHz and is solid for hours but it doesn’t happen often.
Hot summer weather has wide temperature swings which is a common electronics failure mode.
What I don’t know are tools to examine what is happening over the radio links.