What Is Per-Channel Port Allocation?

Traditional video management software routes all camera feeds through a single shared application port. This means a single port conflict, bandwidth spike, or software crash can disrupt every connected camera simultaneously.

OpticLink Pro takes a fundamentally different approach. Each camera channel is assigned its own dedicated, user-configurable network port. The software binds an isolated streaming daemon to that port, serving the audio and video feed for that specific camera only. One port per camera, one daemon per stream—completely independent.

Three Streaming Modes Explained

Every camera port in OpticLink Pro can operate in one of three distinct access modes, giving you granular control over where your stream is visible and who can reach it.

Mode 1

Private (Device Only)

Bound to: 127.0.0.1 (localhost loopback interface only)

Use case: The stream is accessible exclusively within the Windows machine running OpticLink Pro. No other device on the network—and certainly nothing on the internet—can reach the port. Ideal for single-workstation monitoring setups where security is paramount.

Mode 2

Local Network (LAN)

Bound to: The machine's local IP address (e.g. 192.168.1.x)

Use case: The stream is reachable by any trusted device sharing the same local network—mobile phones, tablets, other PCs, smart TVs—using the host machine's LAN IP and the assigned port. The stream never leaves your local network, eliminating cloud exposure entirely.

Mode 3

Online / WAN (Remote Access)

Bound to: 0.0.0.0 (all interfaces), forwarded at the router level

Use case: The stream is accessible from anywhere on the internet by forwarding the dedicated camera port through your router. OpticLink Pro enforces password protection on all WAN-exposed streams, with zero ads, zero analytics, and zero third-party servers in the path. You own the connection end-to-end.

Why Dedicated Ports Matter for Performance

Sharing a single application port across all cameras creates a serialization bottleneck. Every request—whether for a recording segment, a live preview frame, or a remote stream—competes for the same I/O queue. Under load this manifests as stuttering, dropped frames, and delayed local recordings.

With independent port allocation, each camera's network requests are handled entirely by its own daemon in a separate memory-isolated context. Heavy WAN traffic on Camera 3's port cannot degrade the recording throughput of Camera 1. The primary hardware capture pipeline is processed once and distributed internally via a shared memory buffer, keeping CPU overhead minimal regardless of the number of active external viewers.

Port Allocation Architecture Comparison

Understanding the architectural difference between shared-port and per-channel-port designs highlights why independent allocation is the professional standard for high-uptime surveillance.

Attribute Shared Port VMS Consumer NVR Appliance OpticLink Pro (Per-Channel Port)
Stream Isolation None — all cameras share one port Partial — proprietary protocol Full — dedicated port per camera
Port Conflict Risk High — one conflict kills all streams Medium — fixed manufacturer ports Low — user-configurable, isolated
Remote Access Method Cloud relay (third-party server) Vendor cloud or DDNS Direct port forward — no cloud
LAN Stream Access App-specific client required Proprietary viewer app Any browser or media player

Common Challenges & Solutions

Configuring per-camera port routing on a live Windows machine surfaces a predictable set of networking edge cases. Here are the most common issues and how OpticLink Pro resolves them.

Challenge 1

Port Already In Use (EADDRINUSE)

The Cause: Another application or a previous daemon instance has claimed the target port, preventing the camera stream from binding.

The Solution: OpticLink Pro's Self-Healing Dynamic Port Allocation automatically detects EADDRINUSE errors and selects the next available port in the configured range, restoring the stream without user intervention.

Challenge 2

Windows Firewall Blocking LAN Access

The Cause: The Windows Defender Firewall blocking inbound connections on the camera port from LAN devices after a mode switch from Private to Local.

The Solution: OpticLink Pro automatically adds a Windows Firewall inbound rule for each active camera port when LAN or WAN mode is enabled, removing it when the stream reverts to Private mode.

Frequently Asked Questions

Can I change which port a camera uses after initial setup?

Yes. OpticLink Pro lets you reassign any camera's port at any time from the channel settings panel. The daemon restarts on the new port automatically, and your saved port-forward rules simply need to be updated in your router.

How many ports does OpticLink Pro use simultaneously?

One port per active camera channel. If you have eight cameras configured with streaming enabled, eight daemon processes each bind one port. Cameras in Private mode bind only to the local loopback and do not consume any exposed port on the LAN interface.

Is password protection required for WAN-exposed ports?

Yes. OpticLink Pro enforces mandatory password authentication on any stream port switched to Online / WAN mode. Unauthenticated requests receive a 401 response and the stream is never served. There is no way to disable this protection for internet-exposed ports.

Do I need a static public IP for WAN streaming?

A static public IP is recommended for reliable remote access. If your ISP assigns dynamic IPs, configure a DDNS (Dynamic DNS) service on your router—most modern routers support free DDNS providers—so your stream URL remains stable even when your public IP changes.