Ruckus Unleashed - Mesh - Root AP Election Optimization
I think there is an issue with the Root-AP Election within a Unleashed Mesh-Network.
I checked how a AP decides if he is a Root-AP or a Mesh-AP.
From my observations i saw the AP tries to reach the Default Gateway over his Ethernet Interface. If the GW is reachable it will act as a Root-AP. If not, Mesh Role will be choosen.
If the Default Gateway is not accessable, the Master-AP changes his Role to Mesh-AP and reboots (Mesh-AP cannot be a Master). This can result in a complete Network Outage because all Root-APs thinking they are Mesh-APs now.
I had issues on a customer site where the Gateway was rebooted each night.
On another Installation i started the Root-APs while the Default Gateway was not reachable. In that case, the Ruckus Unleashed Network was not able to form.
I think its important to be able to set a second IP and make it clear for Users which IPs are used to decide the Roles. Maybe list as first IP the Default Gateway as a greyed out field and a second field where a User can set a second custom IP.