All 14 articles in this series are now available in our free eBook ‘Understanding IP Production Networks - 2026 Edition’ – download it HERE.

All articles are also available individually:

IT convention refers to user equipment connected to routers and switches as hosts. This could be a desktop computer, laptop, camera, production switcher or sound console for example. All these devices share similar configuration in the way they are connected to IP/Ethernet networks.

There are two ways to set up a computer on a network, either manually, or using automatic configurations. The two key parameters that need to be configured are the IP address details, and the details of domain name system (DNS). DNS is a server service to associate web names with IP addresses and is not entirely relevant to cameras or production switchers.

IP configuration can be automated by using Dynamic Host Configuration Protocol (DHCP). This is a service running on a network server which automatically provides an IP address for a host when it boots up. This is generally not used for broadcast kit as we want to be able to identify cameras and production switchers through their IP addresses. It’s possible for a host to change its IP address when using DHCP without warning. For these reasons, we tend to use static, manually configured IP addresses.

Config Parameters

The three key parameters that will need configuration are the IP address, subnet mask, and default gateway. When setting the IP address care must be taken not to use an address which has already been used, as doing so will result in IP ghosting and provides some very interesting results as other hosts may try to send and receive packets to a camera without realizing they’re addressing the wrong or same device.

Two conventions of subnet are in use: classful and classless. Classful is an older rarely used system often referring to class A, B, C and D subnets using discontinuous address ranges. This was considered too complicated and restrictive in normal use and has largely been dropped in favor of the classless system. Classless uses a sequence of bits to define an address range. For example, 10.0.1.1/24 refers to the range 10.0.1.0 to 10.0.1.255. Host configuration of the subnet value tends to still use the dot notation. As an example, 10.0.1.1/24 would give a subnet of 255.255.255.0, and 10.0.1.1/20 would give a subnet of 255.255.240.0, that is the first 20 bits of the IP address.

The combination of the IP address and the subnet is often referred to as the network ID. In address 10.0.1.0/24, the part 10.0.1.nnn is the value of the subnet the camera is connected to. The camera will be able to send and receive packets to all devices in the range 10.0.1.0 to 10.0.1.255.

Default Gateways

Default gateways are used by the host to work out what to do if they need to send data to a host outside of its subnet. For example, if we have a camera with address 10.0.1.0/24 and production switcher with address 10.0.2.0/24, the camera would not be able to send its packets directly to the production switcher as they are on different networks. The camera is on network 10.0.1.nnn and the production switcher is on network 10.0.2.nnn. In effect, they are physically separated.

Each host, whether it’s a camera, sound console or desktop computer, will have its own routing table. This consists of a series of networks the host can see, and how it routes to the ones it can’t.

When the camera needs to send its packets to the production switcher, it will look up the production switcher’s network ID in its own routing table and realize it doesn’t have a listing for network 10.0.2.0/24. The default gateway is then used to resolve this.

When routing an IP packet, the source and destination IP addresses are kept intact throughout its whole journey from source to destination (unless Network Address Translation is used). However, the source and destination Ethernet MAC addresses do change at each node.

When the camera realizes it cannot send its packets directly to the production switcher, it will send it to the default gateway instead. It does this by finding the Ethernet MAC address of the default gateway, then setting the destination MAC address of the packets to be that of the default gateway’s MAC address.

It’s important to note, that the source and destination IP addresses do not change.

The default gateway address must be accessible by the host so will always be within the subnet of the hosts IP address.

Configuring cameras and sound desks can be frustrating for broadcast engineers due to the lack of available tools within the equipment. For example, a PC will have command line programs such as IPCONFIG to show the connectivity of the network interface card, ARP to show the resolution of IP addresses and MAC addresses, and ROUTE PRINT to show the hosts routing table configuration. IP interfacing in broadcast kit sometimes appears to be a bit of an add-on, and the tools taken for granted in the IT world are generally not available.

The Application Of Static Addresses

Although DHCP is rarely used in broadcast applications, understanding how it operates helps explain why static IP addressing remains essential in these systems.

DHCP is a network management protocol that automatically assigns IP addresses and other network configuration parameters to devices, allowing them to communicate without manual setup. It is particularly useful in Wi-Fi environments where users move between access points and require seamless network connectivity.

When a device such as a laptop or mobile phone first connects to a network, it has no IP address of its own. If it were to choose an address at random, there is a risk of duplication, sometimes referred to as IP ghosting. This can lead to unpredictable device behavior and widespread disruption across the network, as routers and switches would be unable to determine which MAC address should receive the data. The result is Transmission Control Protocol (TCP) timeouts, retransmissions, congestion, and packet loss. Configuring every device manually to avoid these conflicts would be inefficient and time consuming for any IT department.

With DHCP, the process is automated. When a device joins the network, it sends a broadcast message to 255.255.255.255 to announce that it needs an IP address. The DHCP server, located on the same network, listens for this message and responds by selecting and allocating a unique address from its available pool. The server keeps a record of both the free and assigned addresses to ensure that no duplicates and ghosting occur.

This system works extremely well in enterprise, office, and home networks where users expect plug and play connectivity and do not want to be involved in IP management. However, in broadcast networks the dynamic nature of DHCP introduces several challenges.

Consistency Is King

Each IP address assigned through DHCP is leased for a limited period. When the lease expires or the device reboots, the address can be reassigned. Although this behavior improves security by making it harder for external actors to exploit known devices, it creates instability for broadcast equipment. Devices such as cameras, microphones, and production servers rely on consistent IP addresses for routing and multicast connections. If an address changes during operation, a signal path may be lost until the system is manually updated.

Larger enterprise networks often deploy redundant DHCP servers for resilience, ensuring that service continues if one server fails. Even so, the presence of a DHCP infrastructure adds complexity to a broadcast IP network and introduces another possible point of failure.

Broadcast systems make extensive use of IP multicasting to distribute audio and video streams. Dynamic address allocation complicates multicast configuration and can lead to reliability issues, especially when devices are frequently rebooted or reconnected.

Using static IP addresses avoids these problems, though it requires maintaining accurate records of all devices, their IP addresses, and corresponding MAC addresses. In the past, this was often managed through large spreadsheets maintained by engineering teams. With the adoption of standards such as AMWA’s NMOS, much of this manual work is being replaced by automated discovery and registration systems that perform a similar function to DHCP but are designed specifically for broadcast operations and overcome many of the downsides of DHCP.

Until such systems are universally implemented, broadcast engineers must continue to work closely with IT departments to ensure that IP configurations remain stable, predictable, and suitable for the unique requirements of professional media networks.