Hi all,
I’d like to suggest a feature improvement for CAPsMAN to increase Wi-Fi reliability in case the controller goes offline.
Problem:
Currently, if a CAP reboots and CAPsMAN is unavailable (e.g., the controller device is down), the CAP doesn’t receive any configuration and Wi-Fi becomes completely non-functional.
This behavior is problematic especially in smaller networks, where CAPsMAN is running on the same router that provides internet access. A simple router reboot or connectivity issue can break the whole wireless setup.
Suggested solution:
Add an option for the CAP to retain the last known good configuration even if the controller is temporarily unavailable.
Expected behavior:
When CAP connects to CAPsMAN and receives configuration, it saves it locally.
If CAPsMAN becomes unavailable (e.g., during reboot), the CAP reuses the last configuration.
Once CAPsMAN is reachable again, it re-applies the most up-to-date config from the controller
Benefits:
Keeps Wi-Fi operational even during CAPsMAN outages or reboots.
More resilient design for home setups and small networks.
More consistent with systems like UniFi, where APs can continue running even if the controller is down.
No loss of service after power outages or CAP reboots.
Thanks for considering! I believe this would greatly improve CAPsMAN usability and fault tolerance.
