Raspberry Pi Connect • Port requirements for Raspberry PI Connect?

Please help me verify the flow as described below.

Q1: Are the flow as described correct?
Q2: Are the servers and ports complete?
Q3: Can I expect the IP addresses to be static?

Registration and connection phase

The connect server is used for both device registration and initial connect. As far as I can see, no persistent connection is established when "connected". Instead I am seeing a continuous heart-beat.
Requirements for peer-to-peer connection

The STUN server is used by both peers in order to discover their own public facing IP-address and exposed ports.
The two peers now exchange ICE candidates (IP/port pairs). This is done via the connect server on port 443:
Once ICE candidates are exchanged a peer-to-peer connection is established based on available port-ranges. If possible.

Requirements for relay mode

If a peer-to-peer connection can not be established, Raspberry PI Connect will fall back to relay mode. In WebRTC this is typically the responsibility of the TURN server. For Raspberry PI connect the STUN server address is used also for the TURN server, but on a different port (443 instead of 3478).

Statistics: Posted by sunefred — Mon Mar 31, 2025 3:30 pm

---