Networking basics for CCTV installers and network contractors: IP addresses, VLANs and bandwidth
CamVerion team · 19 November 2026 · 7 min read
Quick answer
IP CCTV is a network project. Plan an IP address scheme, keep cameras on their own subnet or VLAN, size switch uplinks for total camera bandwidth, set time synchronisation, and document every device. Installers who learn these basics can take on network and cabling work as well as cameras.
Modern CCTV is networking. An IP camera system is a small computer network, and most of the hard problems on IP jobs are network problems, not camera problems: IP conflicts, overloaded links, cameras that drop out, remote viewing that won't connect, or an IT department that won't let you on their network.
You don't need to be a network engineer to install IP cameras well. But you do need a solid grasp of a few basics. This guide covers the ones that matter most.
IP addresses
Every device on the network has an IP address, such as 192.168.1.64. Cameras, the recorder, switches, the router and the customer's computers all need unique addresses on the same network to talk to each other directly.
Static or dynamic?
- Dynamic (DHCP): the router hands out addresses automatically. Convenient, but an address can change after a restart, which breaks recorder connections.
- Static: you set a fixed address on each device. More work, but predictable.
For CCTV, fixed addresses are usually best. Either set static addresses on each camera, or reserve addresses for them in the router's DHCP settings. Many NVRs with built-in PoE ports assign addresses to cameras on their own internal network, which avoids the problem for those cameras.
Avoiding conflicts
Two devices with the same address cause both to misbehave. Many cameras ship with the same default address. Before connecting cameras to a shared network:
- Plan an address range for CCTV, away from the range the router hands out automatically.
- Change each camera's address before adding the next one, or use the manufacturer's tool to set addresses in bulk.
- Record every address.
Subnets and gateways
A subnet defines which addresses are on the same local network. The common setting 255.255.255.0 means devices with addresses from 192.168.1.1 to 192.168.1.254 can talk to each other directly. A device on 192.168.2.x can't, unless traffic goes through a router.
The gateway is the router's address. Cameras and the recorder need the correct gateway if they must reach the internet, for example for time synchronisation or remote viewing. Cameras that only talk to a local NVR may not need internet access at all, which is often more secure.
Switches
Unmanaged switches
Simple and cheap. Plug in and go. Fine for small, standalone CCTV networks.
Managed switches
Allow configuration such as VLANs, port settings, monitoring and PoE control. Useful on larger systems and when sharing a network with other traffic.
PoE
Power over Ethernet powers cameras through the network cable. Check the switch's total PoE budget and the standard each port supports. Our PoE switch power budget guide explains how to size it.
Uplinks
The link from a camera switch to the recorder or core switch carries all the cameras' traffic. Make sure it has enough capacity. A gigabit uplink is standard for most systems. Large systems may need faster links.
Bandwidth
Each camera sends a continuous video stream. The bitrate depends on resolution, frame rate, compression and scene activity.
| Example stream | Typical bitrate range |
|---|---|
| 2MP, H.265 | about 1 to 4 Mbps |
| 4MP, H.265 | about 2 to 6 Mbps |
| 8MP (4K), H.265 | about 4 to 12 Mbps |
These are rough ranges. Check the camera's actual settings and measured bitrates. Multiply by the number of cameras, and add sub-streams if the recorder or viewing clients use them.
A common rule of thumb is to keep sustained traffic well below the link's capacity, for example under 50% to 70%, to allow for peaks and other traffic. Our storage calculation guide uses the same bitrate figures to estimate recording space.
Remote viewing bandwidth
Remote viewing uses the customer's internet upload speed. Many connections have much lower upload than download speed. Use sub-streams for mobile viewing, and don't promise smooth multi-camera live view over a slow upload.
A separate network or a shared one?
Separate network
Cameras and the recorder on their own switches, not connected to the office network except through the recorder or a controlled link. Simpler, more secure and easier to support.
Shared network with VLANs
On larger sites, CCTV often shares switches with other systems. A VLAN (virtual LAN) separates CCTV traffic logically, even on shared switches. This:
- Keeps camera traffic from slowing the office network.
- Stops office computers from reaching cameras directly.
- Makes troubleshooting easier.
VLANs need managed switches and usually the customer's IT team's agreement.
Multicast and unicast
By default, each viewer requests its own video stream (unicast). On systems with many simultaneous viewers, multicast can send one stream to several viewers. Multicast needs switches configured to handle it properly. Most small and medium systems don't need it.
Security basics
An insecure camera network is a risk to the customer. At minimum:
- Change all default passwords.
- Update firmware.
- Disable services you don't need.
- Avoid opening ports on the router for remote access. Use the manufacturer's secure service or a VPN.
- Keep cameras off the internet where they don't need it.
Our cyber security guide covers this in more detail.
Time synchronisation
Recordings are only useful as evidence if the time is right. Set the recorder to synchronise with a reliable time server, and make cameras take their time from the recorder or the same server. Check the time zone and daylight saving settings.
ONVIF and compatibility
When mixing camera and recorder brands, ONVIF profiles help them work together. Check which profiles each device supports, and test before committing to a mixed system. Our ONVIF guide explains the profiles.
Working with IT departments
On commercial jobs, the customer's IT team often controls the network. Engage them early:
- Ask for their network policies and any restrictions.
- Agree on address ranges, VLANs and how the CCTV system will connect.
- Explain your bandwidth needs.
- Agree who is responsible for switches, firewalls and remote access.
- Put agreements in writing.
IT teams are usually much easier to work with when you bring a clear plan and respect their rules. Our guide on CCTV for offices covers working in shared buildings.
Testing tools
A few tools make network work easier:
- A laptop with the manufacturer's device search and configuration tools.
- A network cable tester, and ideally a tester that checks PoE.
- An IP scanner to find devices on the network.
- Ping, to check whether a device is reachable.
Our installer tools list covers what to carry.
Documenting the network
Document every system:
- Device names, models and serial numbers.
- IP addresses, subnet and gateway.
- Switch ports for each camera.
- VLANs, if used.
- Usernames for admin accounts, stored securely.
- A simple diagram.
Good documentation turns a two-hour fault-finding visit into a twenty-minute one. Store it with the job record in your network contractor software. In CamVerion, notes and attachments on each job keep this with the customer's history.
Common mistakes
- Leaving cameras on default addresses, causing conflicts.
- Using DHCP without reservations, so addresses change.
- Overloading uplinks on larger systems.
- Putting cameras on the office network without separation.
- Opening router ports for remote viewing.
- Not documenting addresses and switch ports.
A quick checklist
- Plan an address range for CCTV.
- Use static or reserved addresses.
- Check subnet and gateway settings.
- Size PoE budgets and uplinks.
- Estimate bandwidth from real bitrates.
- Separate CCTV traffic, physically or with VLANs.
- Secure devices and avoid open ports.
- Synchronise time.
- Agree plans with the customer's IT team.
- Document everything.
Networking skills separate installers who can handle modern IP systems confidently from those who struggle with every larger job. A few basics, applied consistently, go a long way.
Frequently asked questions
Do CCTV cameras need their own network?
It is good practice. A separate VLAN or switch keeps camera traffic and security risks away from business computers and makes faults easier to find.
How much bandwidth does an IP camera use?
Typically 2 to 8 Mbps per camera for the main stream at common settings, more at high resolution or frame rate. Add up all cameras to size switch uplinks.
What network skills do CCTV installers need?
IP addressing and subnets, VLANs, PoE switches, port forwarding alternatives, time synchronisation and basic troubleshooting with ping and cable testers.