|
|
| Line 4: |
Line 4: |
| | | | |
| | == Firewall info == | | == Firewall info == |
| − | '''Best Practices, on how to secure CoolMasterNet in the Firewall'''<br>
| + | [https://support.coolautomation.com/hc/en-us/articles/4403741653265-What-are-the-firewall-requirements-internet-ports-to-enable-proper-connection-of-the-device-to-our-cloud-services]<br> |
| − | As the Cloud IPs can change without any notice, as it’s an automatic service based on device geo-location, load balance and other parameters,
| |
| − | we strongly suggest not to lock the CoolRemote cloud IP in the firewall.<br>
| |
| − | What we do suggest is the following:<br>
| |
| − | Lock the CoolMasterNet IP by MAC address in the Firewall/Router (also called DHCP Reservation, or Network Object).<br>
| |
| − | Create FW Rules, via Ports only and lock it to the CoolMasterNet network object.<br>
| |
| − | Source/Destination:<br>
| |
| − | CoolMasterNet IP to/from Destination ANY ports:<br>
| |
| − | 10101 TCP/UDP<br>
| |
| − | 443 TCP/UDP<br>
| |
| − | 10101 TCP - outbound.<br>
| |
| − | 10101 UDP - if your equipment is configured for pinholing then just outgoing otherwise both inbound and outbound.<br>
| |
| − | If your Firewall allows rule creation by FQDN host (DNS (port 53)) it can also be done but due to DNS propagation delays connectivity may occur.<br>
| |
| − | The DNS to be set is [http://app.coolremote.net app.coolremote.net]
| |
Revision as of 01:52, 2 June 2024
