Self-hosted controller firewall issue
I run my own Omada SDN Controller v5.12.7 in a Linode VPS, with a firewall configured on the VPS to allow only the ports needed per TP-Link's documentation, and only from the IPs of the networks managed by the controller. I've noticed when rebooting the Omada routers at the sites, they are not able to reconnect to the controller unless I temporarily disable the firewall on the server. I do have the SDN instance linked to a TP-Link Cloud account for cloud management, so I'm thinking that the router's initial connection to my controller is being routed through the TP-Link Cloud, and therefore blocked by the firewall on the VPS. Once the router connects, I can re-enable the VPS firewall, and everything works fine, until the next reboot.
I need to keep the TP-Link Cloud association for the purpose of sharing admin access to the controller, so un-linking is not an option. Is it possible to get a list of IPs from the TP-Link cloud that need to have access to the controller so they can be added to the firewall?