TCP vs UDP: Choosing the Right Protocol for Your Use Case

Network transport protocol selection has a direct impact on stream stability, latency, and viewer compatibility. OpticLink Pro supports both TCP and UDP on a per-channel basis, so you can match the protocol to the network environment without being locked into one approach for all cameras.

TCP

Reliable Ordered Delivery

Best for: LAN streaming to browsers, local recording verification, or any scenario where every frame must arrive in sequence.

Characteristics: Guarantees packet delivery and ordering. Retransmits dropped packets automatically. Slightly higher latency than UDP due to acknowledgment overhead, but eliminates frame artifacts caused by packet loss. Works reliably through most firewalls and NAT routers with a simple port-forward rule.

UDP

Low-Latency Lossy Delivery

Best for: Real-time monitoring over congested LANs, low-latency live preview tiles, or WAN streams where sub-second latency matters more than perfect frame delivery.

Characteristics: Sends packets without acknowledgment overhead, achieving the lowest possible latency. Dropped packets produce brief visual glitches rather than stalling the stream. Ideal for monitoring contexts where human eyes tolerate occasional dropped frames better than a freeze caused by TCP retransmission delays.

Port Routing Modes: Private, Local, and Online

OpticLink Pro's port routing system operates at three distinct network scopes. Each camera channel's port can be configured independently, allowing some cameras to remain completely private while others serve the full LAN or the open internet simultaneously.

Mode Bound Interface Who Can Access Authentication Required
Private 127.0.0.1 (loopback) This machine only Optional
Local (LAN) Local IP (e.g. 192.168.x.x) All devices on your home/office network Optional
Online (WAN) 0.0.0.0 + router port forward Any device on the internet Mandatory (enforced)

Multi-Port Stream Serving Architecture

OpticLink Pro transforms the host Windows machine into a high-performance streaming server. Every connected camera feed—USB or IP—can be mapped to a dedicated, user-configurable local port. The software processes the primary hardware feed once, distributing network requests efficiently via an isolated memory buffer shared between the capture pipeline, the disk recorder, and all active serving daemons.

Serving external streams does not impact individual camera recording or local capture performance. Incoming viewer requests for a given camera port are handled by that camera's isolated streaming daemon, which reads frames from the in-memory buffer without competing for hardware capture resources. You can saturate a camera's WAN port with hundreds of concurrent viewers without causing a single dropped recording frame.

Direct Port Forwarding: Cloud-Free WAN Streaming

OpticLink Pro supports pure, cloud-free remote access through standard router port forwarding. When a camera channel is switched to Online mode, the software opens the specified TCP or UDP port on all network interfaces and registers an inbound Windows Firewall rule automatically.

On your router, you simply create one port-forward rule: forward the external port (e.g. 8101) to the host PC's LAN IP on the same port. From that point, any internet-connected device can reach your camera stream by connecting to your public IP (or DDNS hostname) on that port. There is no third-party middleware, no relay server, no ad tracking, and no mandatory cloud account—the stream travels directly from your machine to the viewer's device.

Step 1

Assign Port & Protocol in OpticLink Pro

Action: Open the channel settings for the camera. Set a port number (e.g. 8101), choose TCP or UDP, and switch the streaming mode to Online.

Result: OpticLink Pro binds the daemon to 0.0.0.0:8101 and automatically adds a Windows Defender Firewall inbound allow rule for that port and protocol.

Step 2

Configure Router Port Forward

Action: Log into your router's admin panel. Add a port-forward rule: external port 8101 → internal IP of your PC → internal port 8101, protocol TCP (or UDP if selected).

Result: Inbound connections from the internet on port 8101 are routed directly to OpticLink Pro. The stream is now reachable from any device in the world using your public IP or DDNS hostname.

Step 3

Authenticate & Stream

Action: Open the stream URL in any compatible browser or RTSP player on a remote device. Enter the password configured in OpticLink Pro's channel settings when prompted.

Result: The live camera feed streams directly from your machine to the remote viewer. Zero ads, zero analytics, zero data passing through third-party servers. The connection is purely between the viewer and your network.

Protocol Comparison for Camera Streaming

Attribute TCP Mode UDP Mode Recommendation
Latency Low–Medium (ACK overhead) Lowest (fire-and-forget) UDP for live monitoring; TCP for recording verification
Packet Loss Behavior Stream stalls, retransmits Brief visual glitch, no stall UDP more resilient on congested LANs
Firewall Traversal Excellent — standard port-forward Good — requires UDP rule at router TCP for most WAN deployments
Viewer Compatibility Universal — all browsers & players Requires UDP-capable player TCP for maximum compatibility

Frequently Asked Questions

Can I run some cameras on TCP and others on UDP simultaneously?

Yes. Protocol selection is per-channel in OpticLink Pro. You can run indoor cameras on UDP for minimal latency on your LAN, while simultaneously running a WAN-exposed exterior camera on TCP for reliable delivery through NAT and firewall traversal.

Does OpticLink Pro support RTSP over TCP and UDP?

Yes. OpticLink Pro ingests RTSP camera feeds and can serve the resulting stream output over TCP or UDP depending on your per-channel configuration. RTSP interleaved (TCP) mode is the default for maximum compatibility with consumer routers and devices.

What happens if my public IP address changes?

Your router's port-forward rules remain intact regardless of public IP changes. To maintain a stable external stream URL, configure a free DDNS hostname on your router (most modern routers include this feature natively). Your DDNS hostname stays constant while automatically tracking your current public IP.

Is UPnP automatic port mapping supported?

OpticLink Pro can optionally request UPnP port mappings from compatible routers when Online mode is enabled, automating the port-forward step. For security-conscious deployments, UPnP can be disabled in settings in favor of manual router configuration, which provides explicit control over which ports are exposed.