Cameras not found across VLANs
Cameras not found across VLANs
Symptom
The gateway is online. The cameras are online, reachable from a laptop on their VLAN. But Discover cameras on the Gateways page returns an empty list or only finds devices on the gateway’s own VLAN.
Likely causes
- Gateway VLAN and camera VLAN are isolated — the expected, standard network behaviour.
- A router between VLANs does not forward IGMP or PIM multicast.
- No mDNS or WS-Discovery repeater is installed between the VLANs.
Fix
You have three viable paths. Pick the one that matches your network policy.
Option 1 — Put the gateway in the camera VLAN (simplest)
- Assign the gateway’s network interface an address in the camera VLAN.
- If the gateway has two NICs, use one for cameras (trunked into the camera VLAN) and one for uplink to the cloud.
- Re-run Discover cameras. The gateway and cameras now share a broadcast domain.
Option 2 — Add a multicast relay between VLANs
- On the router between VLANs, enable a WS-Discovery or mDNS relay (often called “PIM”, “IGMP proxy”, or “Avahi reflector” depending on the platform).
- Confirm UDP 3702 multicast is permitted in both directions.
- Re-run Discover cameras.
Option 3 — Add cameras by static IP (no discovery needed)
- On the Cameras page, click Add camera → By IP.
- Enter each camera’s IP address, ONVIF port, and credentials.
- NovaVMS connects directly over unicast; VLAN routing alone is enough.
This is the right choice when security policy forbids multicast across VLANs.
Verify
- Option 1 / 2: Discover cameras now returns the camera list within 60 seconds.
- Option 3: Each manually added camera shows a green dot and a live frame.
- Cameras stay online for 15 minutes with no red-dot flaps.
If none of this worked
- From the gateway host, run
ping <camera-ip>to confirm unicast routing works. - Capture a packet trace on the gateway filtered for port 3702 during a discovery run. Attach to the ticket.
- See also: Camera does not appear in ONVIF discovery.