P2P Port Information

In most networks, no port forwarding is required for P2P connections to work. Our devices and clients establish outbound connections automatically, and the router handles the return traffic.

For the majority of users, whitelisting myeasyip.com is enough to allow connections.

However, on networks with strict firewall rules or outbound restrictions, you may need to reference the port list below to ensure the necessary traffic is allowed. If whitelisting myeasyip.com does not resolve the issue, confirm that these ports are open for outbound connections and that responses are allowed back in.

Client Side

• TCP 9116, 9118 – P2P signaling and data transmission

• TCP 80, 443 – Standard HTTP/HTTPS access to services

• UDP 0–65535 – Used for NAT return traffic (see note below)*

Device Side

• TCP 9116, 9118 – P2P signaling and data transmission

• TCP 12366 (HTTP) – Device reporting

• TCP 12367, 12337 (HTTPS) – Device reporting over HTTPS

• UDP 0–65535 – Used for NAT return traffic (see note below)*

Public Service Ports

• UDP 53 – DNS resolution

P2P-Specific Ports

• UDP 8800 – Device login & hole punching

• UDP 8802 – Device login

• UDP 8803, 8900 – Client-side hole punching

• UDP 8810–8815 – STUN protocol for NAT traversal

Note on UDP 0–65535

Our software uses outbound UDP for P2P setup. Because routers performing NAT assign random “ephemeral” ports for return traffic, responses may arrive tagged with any UDP port number.

• This does NOT mean the software listens on all UDP ports.

• Firewalls should allow responses to outbound traffic. You do not need to open all UDP ports for unsolicited inbound traffic.