Connecting Devices to InControl Through a Firewall


#1

In a situation where you have a firewall between you device and the Internet, you might not be able to access InControl. Get through this, you need to create an outbound rule for InControl 2 traffic. There are 2 options for doing this:

Option 1: Simply define a rule for the domain “peplink.com

Option 2: If the router/firewall does not support domain-based rules, then configure your firewall to permit the following IC2 server IP addresses:

54.201.63.99
54.69.133.25
54.218.62.163
54.213.17.185
54.68.148.178
54.218.73.43
54.213.230.221
54.213.108.78
54.213.245.97
54.218.3.77
52.37.112.82
52.33.148.23
54.148.216.73
54.186.87.252
35.167.224.48
35.166.227.55
54.200.27.33
54.200.29.147
34.209.167.139 (added on 2017-09-14)
52.13.179.234 (added on 2018-09-04)
52.88.12.218 (added on 2018-11-19)

Outgoing ports:
UDP port 5246 and
TCP port 443 and 5246

Last updated: November 19th, 2018


InControl Access Behind Nat
Incontrol source interface
Hosted InControl2 IP addresses?
HA Slave visible in InControl2
Incontrol2 ~ When Subscription Expires
FAQ: Why does my device appear "offline" on InControl 2 even though the device has an internet connection?
What port is being used for incontrol and incontrol2?
InControl Public IP Addresses
Activating Fusion Hub behind firewall
Dynamic DNS on surf soho for webserver & VNC behind ISP router