iCSee camera architecture is fundamentally different from traditional RTSP cameras. There is no externally-exposed port. The camera does not listen for incoming connections. Instead, it initiates outbound connections to Tencent's cloud relay infrastructure, establishing a tunnel through which the iCSee app on your phone receives the video stream. Understanding this architecture changes how you write firewall rules for these cameras.
The Cloud Relay Model#
iCSee and Eye4 cameras running the same firmware architecture send all remote viewing traffic through cloud relay servers operated by Tencent. The camera initiates a persistent outbound connection to a relay endpoint. The iCSee app, whether it's on your phone or in a web browser, also connects to the same relay infrastructure. The relay bridges the two connections and streams video in both directions.
The camera does not expose TCP 34567 or any other port to the internet. It does not listen for inbound connections. The connection model is entirely outbound-initiated.
api.eye4.cn: The Handshake Endpoint You Cannot Block#
api.eye4.cn is the cloud relay API endpoint that handles the handshake and session negotiation. When a camera boots or needs to re-establish its relay tunnel, it first queries DNS for api.eye4.cn, then makes an HTTP or HTTPS connection to negotiate the relay parameters.
If you block this domain — either at the DNS level by returning 127.0.0.1 or via firewall rules by dropping connections to its IP — the camera cannot establish a relay session. The iCSee app will show the camera offline. Remote viewing goes completely dark. This is not an assumption. This was discovered by blocking the domain in Technitium DNS and watching the camera status change to offline in the iCSee app within seconds.
You can unblock the domain and the camera comes back online just as quickly.
Relay Ports Are Randomized Per Session#
The relay ports themselves are not fixed. Each time a camera establishes a new relay session, it connects to a different port. Port-based firewall rules cannot work because you'd need to anticipate every possible relay port, which is infeasible.
The only viable approach is to assign the camera's IP address (or the IP group containing all cameras) to an allow rule with ANY destination port on the External zone. Allow the camera IP group to reach External on any port, TCP and UDP both. This trusts that the camera will only establish legitimate relay connections, and that you're validating the destination DNS names (which you are, through the firewall's DNS security features).
CAM-Doorway: Tencent COS for Video Clips#
The Doorway camera uses a different cloud service for a different purpose. Tencent COS (myqcloud.com) is the Tencent Cloud Object Storage service. The camera uploads video clips to COS when motion is detected and you enable cloud recording. If this domain is blocked or unreachable, clip uploads fail silently — you won't see the clips in the iCSee timeline, but you won't get an error either.
qiniup.com: Excessive Telemetry#
qiniup.com is Qiniu cloud storage, a separate Chinese CDN provider. CAM-C3 was observed making 5,500+ upload attempts per day to Qiniu. This is not required for camera function. It's telemetry, likely analytics data and usage metrics sent to the manufacturer. Blocking qiniup.com removes excessive cloud calls without affecting the camera's core operation.
Doorway Relay Ports: A Growing List#
Because the relay ports cluster but are not entirely predictable, a custom port group named Doorway Relay Ports is maintained. It started with a handful of common relay ports and has grown to 16 as firewall block logs surface new ones. It's expected to keep growing.
Monitor the firewall logs for rules named Block Skynet → External. When you see drops on unusual ports, add them to the Doorway Relay Ports group. This provides visibility into the camera's behavior and keeps the group current without over-permitting everything.
Update: The Live-View Failure That Wasn't the Firewall#
Months later, an Eye4 camera stopped delivering live view. The app connected, spun, and gave up. With a camera inside a DEFAULT DROP zone, the firewall is the obvious suspect. I had a rule change half-drafted before I'd looked at a single packet.
It wasn't the firewall. The camera's Power Saving Mode was putting its MQTT connection into a reconnect loop — the session to the cloud kept dropping and re-establishing, so the app never held a stream long enough to play. No rule was blocking anything. Loosening the firewall would have changed nothing except my security posture.
The lesson is the same one this post ends on, from the other direction. Capture first. Blaming the firewall is just another assumption.
The Root Principle: Packet Capture First, Rules Second#
For iCSee cameras and any new IoT device, the discipline is: capture first, then rule. Use tcpdump on the gateway's Skynet VLAN interface to see exactly what DNS lookups and IP destinations the device actually uses. Build allow rules around the verified traffic — not assumptions from documentation or marketing claims. Documentation is written by marketing. Your network is written by you.