3dEYE supports cameras located on different IP ranges, subnets, and network segments through 3dEYE Gateway. This capability is especially valuable in enterprise, campus, and multi‑site deployments where cameras are distributed across multiple network segments but must be connected to the 3dEYE cloud through a centralized Gateway.
Support for Multiple IP Ranges and Subnets
A single 3dEYE Gateway can be configured to communicate with cameras across multiple IP ranges, provided the Gateway has network reachability to those networks. For example, a customer may have cameras distributed across several subnets:
- 192.168.1.x
- 192.168.2.x
- 192.168.3.x
- 10.10.10.x
If the Gateway can route to these networks, it can discover and connect cameras across all of them.
When multiple camera subnets need to be accessed through the same Gateway network interface, the required network ranges can be configured on the Gateway.
Additional network ranges are not intended to be added independently by the customer through the standard Gateway interface. If a deployment requires this type of configuration, the customer should provide 3dEYE with the required IP ranges and network details so that the Gateway can be configured appropriately.
Multi-site and enterprise network environments
This architecture also supports more complex network topologies, including:
Private corporate WANs
VPN tunnels
VLAN‑segmented networks
Routed enterprise networks
Dedicated fiber links
Other private network infrastructures
Cameras do not need direct internet access. As long as the Gateway can reach them through the customer’s private network, they can be connected to the 3dEYE cloud.
Example multi‑site workflow
Camera Site A → Private WAN → Gateway → 3dEYE Cloud
Camera Site B → Private WAN → Gateway → 3dEYE Cloud
Camera Site C → VPN / Routed Network → Gateway → 3dEYE Cloud
The exact architecture depends on the customer’s network design.
Network reachability is the key requirement
The Gateway and cameras do not need to be on the same subnet. The critical requirement is network reachability.
A camera can be connected through the Gateway if:
There is a valid routing path
Required ports and protocols are accessible
Firewall rules allow communication
If the Gateway can route to the camera, the camera’s physical location or subnet is not a limitation.
Cameras can be connected even when they are:
On different subnets
On different IP ranges
Behind VLANs
At remote sites
Connected through private WANs or VPNs
The Gateway only requires reliable network access to the camera.
Customer Requirements for Multi‑Subnet Deployments
For deployments involving multiple IP ranges or routed networks, customers should provide 3dEYE with:
Camera IP ranges / subnets
Gateway network information
Routing details
VLAN or VPN information
Firewall rules
Required ports and protocols
3dEYE will determine the correct Gateway configuration based on this information.