Orbit Security Group

Guest Wi-Fi is not a camera backbone

Consumer mesh and a shared SSID will record right up until they do not. Cameras and door hardware belong on a path someone designed.

Jul 21, 2026 · Networking

Vehicle inventory lined up on a dealership lot at dusk, where lot cameras need a designed path rather than shared Wi-Fi

We still walk into sites where the recorder is hanging off the same network the office uses for streaming, phones, and a guest SSID printed on a chalkboard. It works. It keeps working until a mesh node re-parents itself, the SSID gets renamed, or someone spends a Saturday "fixing the Wi-Fi."

Why it fails in ways nobody attributes to Wi-Fi

The failure is rarely dramatic. It shows up as gaps.

A mesh node picks a different uplink and the camera on that node loses two hours of recording. An ISP router reboots after a firmware push and hands out new addresses, so the recorder can no longer reach half its cameras by IP. A guest device saturates the uplink and remote viewing stops, which the owner reports as "the app is broken."

Then an incident happens, someone pulls the footage, and the clip that mattered is in one of the gaps. Nobody connects that to a network change three weeks earlier.

What a designed path looks like

Cameras and access control get their own segment — a VLAN if the switching supports it, or at minimum a dedicated switch with a static addressing plan and documented ports. Recorders and door hubs get wired connections. Not "wired eventually," wired at commissioning.

Guest Wi-Fi is fine, and most of our sites need it. It sits on its own VLAN with client isolation and a rate limit, and it carries nothing that produces evidence. On a Meraki or UniFi head-end that separation is configuration work measured in minutes, which is the frustrating part: the fix is cheap and the failure is expensive.

Cambium cnWave V2000 client node used for a designed link to an outbuilding or gate

When wireless is the only option

Sometimes there is no path to the barn, the gate, or the far corner of a lot. That is a point-to-point link with a written design — line of sight, fade margin, mounts, power, and the VLAN it lands on — using purpose-built radios such as Cambium cnWave or ePMP. It is not another node added to the building's mesh and pointed hopefully outward.

The difference is not brand loyalty. It is that a designed link has a documented margin and a known failure mode, and a mesh node in a window has neither.

The short version

If the video matters enough to install cameras, it matters enough to keep them off the network that changes every time someone buys a new router. Segment the cameras, wire the recorder, and write down the path. Then the guest network can be as chaotic as it likes.

All insights · Request a consultation