Updating Firmware on devices remote site
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I discovered to my great surprise that tp-link has started using ports 8043 and 443 to update devices instead of 29813, this is the same port used to manage the Omada SDN V5 controller,
For security reasons I have always had these ports closed, but I suddenly had problems updating devices on the remote site and had to open 8043, now my controller is open to everyone and in my opinion a big security problem, many of my remote site have dynamic ip and therefore must open up to everything. it is also not possible to approve on FQDN. so my question is, is it possible to block controller management or do you have to have a controller for each site to solve this.
It's a little scary that something so simple is so poorly thought out.
You can create rules from LAN to WAN but not from WAN to LAN, but anyway such rules will not work when the remote site has dynamic IP. What's the point of making a NAT rule that allow all ip and then blocking the whole world afterwards 
I have solved it for now with deactivating NAT rule, now I know about the new port so then I activate it when a remote device ned Firmware update..