03-26-2025 02:55 PM
Unleashed Version: 200.17.7.0.152
AP used: Only one R650
I have a strange new error. I upgraded from a R710 AP on Unleashed 200.15 to an R650 AP on Unleashed 200.15 --> 200.16 --> 200.17, and this error started happening. I am in US country code and have always had the System set to "Optimize for Performance," which unlocks all channels, including all DFS channels.
I've been using Channel 52 with 80 MHz channel width for years with no problem. The R650 is working now on Channel 52, but whenever I try to make any other change to the R650 AP config, it gives me this error, and my changes are not saved.
Thanks for any help!
Solved! Go to Solution.
03-29-2025 06:49 PM
I tried to fix this tonight because I was frustrated that I couldn't make any changes or settings to individual AP, so I tried something:
1. Go to "Admin & Services" --> System --> Country Code.
2. Change from "Optimize for Performance" to "Optimize for Interoperability" (this is temporary)
Unleashed will require a full system reboot. When it comes back up, many/most of the DFS channels will be disabled.
3. Change it back to "Optimize for Performance" and reboot the Unleashed system again.
When it comes back up, you should be able to make changes to the individual AP now without getting the strange "Group channel setting is not in available channel range" error in the OP.
I also had to SSH back into the CLI and change the 80211-pmf settings for my WPA2-Enterprise WLAN back to "Required" instead of "Disabled" (default), and for my WPA2-Personal WLAN for IoT devices change the 80211-pmf to "Optional" instead of "Disabled" (default). But even after Unleashed restarts, those PMF settings stuck just how I want them, so that is good.
This is a strange bug/error, but my workaround works, so I hope this helps others who experience this.
03-29-2025 06:49 PM
I tried to fix this tonight because I was frustrated that I couldn't make any changes or settings to individual AP, so I tried something:
1. Go to "Admin & Services" --> System --> Country Code.
2. Change from "Optimize for Performance" to "Optimize for Interoperability" (this is temporary)
Unleashed will require a full system reboot. When it comes back up, many/most of the DFS channels will be disabled.
3. Change it back to "Optimize for Performance" and reboot the Unleashed system again.
When it comes back up, you should be able to make changes to the individual AP now without getting the strange "Group channel setting is not in available channel range" error in the OP.
I also had to SSH back into the CLI and change the 80211-pmf settings for my WPA2-Enterprise WLAN back to "Required" instead of "Disabled" (default), and for my WPA2-Personal WLAN for IoT devices change the 80211-pmf to "Optional" instead of "Disabled" (default). But even after Unleashed restarts, those PMF settings stuck just how I want them, so that is good.
This is a strange bug/error, but my workaround works, so I hope this helps others who experience this.