Skip to main content

IP Primer (Networking Basics)

Source
This content is based on Cyanview's official manuals. Always check the official page for the latest information and precise specifications.
https://support.cyanview.com/docs/troubleshooting/ip-primer

This guide is aimed at broadcast professionals who are new to IP networking. It covers local network fundamentals — IP addressing, subnet masks, DHCP, and static IP configuration — as well as gateways and routing as they relate to internet access, REMI production, cellular control, and remote support.

Overview of IP addresses and subnet masks​

Every device on a network needs a unique IP address, which functions like a street address, so that routers and switches can deliver packets to the intended device. An IP address (e.g. 192.168.10.24) is 32 bits long, made up of four octets (each ranging from 0–255).

caution

Two or more devices on the same network cannot share the same IP address. Duplicate IP addresses cause unexpected behavior, communication errors, and devices becoming unreachable, and are one of the most common causes of on-site remote troubleshooting issues.

A subnet mask defines which part of an IP address represents the network and which part represents the individual device. For example, 255.255.255.0 means the first three octets represent the network and the last octet represents the individual device.

CIDR notation is a shorthand for expressing the number of network bits as a slash followed by a number. For example, 192.168.1.2/24 means the first 24 bits represent the network and the remaining 8 bits are the host address (equivalent to 255.255.255.0).

A network (IP range) refers to the full range of IP addresses reachable from a given IP address and subnet mask. 192.168.1.0/24 spans from 192.168.1.0 to 192.168.1.255.

Example: a /24 network​

A /24 (equivalent to 255.255.255.0) allows 254 usable IP addresses within a single network segment. Devices that share the same first three octets can communicate directly.

On a 192.168.1.0/24 network:

  • Any IP starting with 192.168.1 belongs to this network
  • An RCP assigned 192.168.1.2/24 uses IP 192.168.1.2 with netmask 255.255.255.0
  • Every device that needs to communicate must have an IP address within this range

Example: a /16 network​

Cyanview products ship with a factory-default IP address on the 10.192.0.0/16 network. The last two octets are generated from the device's serial number, guaranteeing uniqueness.

  • Any IP starting with 10.192 belongs to the 10.192.0.0/16 network
  • If you assign your computer 10.192.1.1 (netmask 255.255.0.0), you can reach devices anywhere from 10.192.0.0 to 10.192.255.255
  • Every device must have an address within this range

:::caution Common mistake A common mistake is setting the RCP to 10.192.46.2 and the computer to 10.192.46.1 (netmask /24). This limits communication to the 10.192.46.0/24 subnet, preventing communication with other devices on the wider 10.192.0.0/16 network. :::

IP gateways​

A gateway routes traffic from the local network to external networks (typically the internet or other subnets). As a postal analogy: mail to your neighborhood is delivered directly, but mail to distant places is routed through the post office (the gateway).

A gateway acts as a router that knows how to forward data toward its final destination. Devices use the gateway's IP address when communicating outside their own subnet. A home router acts as a gateway, forwarding non-local traffic to the internet. Gateways can also be used to route to a single subnet, such as a VPN or data tunnel, and multiple gateways can be used to route to different subnets.

DNS servers​

A DNS server (Domain Name System) translates human-readable domain names such as example.com into the IP addresses computers use to communicate. DNS acts as "the internet's phone book," letting you access services by name instead of needing to remember IP addresses.

DNS is important for any network connected to the internet. Devices can still communicate by IP address without DNS, but they can't access services or websites by name. Cyanview systems require a DNS server for cloud relay services such as REMI and for remote support connections.

DHCP vs. static IP configuration​

A static IP is a value that is set manually and does not change unless edited by hand. DHCP (Dynamic Host Configuration Protocol) automatically assigns network configuration without manual setup. DHCP is common on home network internet routers and similar devices, ensuring unique IP addresses and preventing conflicts from manual configuration.

LAN (local area network) configuration​

On location, static IP addresses are typically used for communication between local devices, especially those deliberately isolated from external networks such as the internet. Network isolation is the simplest and most effective way to minimize security risk.

For local-only communication, such as between an RCP and a camera, it's usually enough to set just the IP address and subnet mask. Since no external routing is needed, the gateway field can be left blank.

Example configuration:

  • Device IP address: 192.168.1.2
  • Subnet mask: 255.255.255.0 (/24)

:::note Exception Some Sony cinema cameras and camcorders require a valid gateway IP address to be configured in order to enable the network interface, even when no external communication is needed. "Valid" here means the gateway address must fall within the device's own subnet — the gateway device itself doesn't need to physically exist or respond; it's only used for configuration validation. This isn't functionally required for local communication, but it's a firmware limitation that's unlikely to be resolved by a future update. In some cases, the Sony camera may also need to be restarted for the interface to become active, though no explicit prompt is shown for this. :::

WAN static IP configuration​

On a typical home network, you configure an IP, mask, gateway, and DNS server to get internet access.

Example configuration:

  • Computer IP address: 192.168.1.25
  • Subnet mask: 255.255.255.0 (/24)
  • Default gateway: 192.168.1.1 (the home router's IP)
  • DNS server: address of a domain name resolution service

This configuration isn't common for local production setups, but it's frequently used when controlling cameras over cellular via a RIO. In addition to the LAN settings, the gateway IP establishes a default route for reaching computers outside the local subnet. When a device communicates with an IP address outside its subnet (as defined by the netmask), traffic is automatically forwarded to the gateway, which handles routing to the final destination — whether another network, a remote site over VPN, or the public internet. If the gateway isn't configured correctly, the device can only communicate within its immediate local network.

Resolving domain names such as remi.cyanview.com or support.cyanview.com requires at least one DNS server to be specified. Communication by IP address still works without DNS, but named services become unreachable. This affects the REMI service and remote support functionality.

If there's no local DNS server but internet access is available, you can also use a public DNS such as Google's 8.8.8.8 or 8.8.4.4.

DHCP​

DHCP (Dynamic Host Configuration Protocol) automatically provides the same network information as a static IP configuration, without needing manual setup on the device.

When a device connects to a DHCP-enabled network, it sends a request asking, "Can you assign me a network address?" The DHCP server (typically a router or dedicated appliance) automatically assigns:

  • IP address: a unique address from the available pool
  • Subnet mask: defines the network segment it belongs to
  • Default gateway: the route to other networks/the internet
  • DNS server: address of a domain name resolution service

On home networks, the router automatically assigns an IP address whenever a device appears. DHCP leases are typically short-lived and subject to renewal/reassignment, so there's no guarantee the same device will receive the same IP address on reconnection.

A managed DHCP server can be configured to assign a specific IP address to a specific device, which is useful in broadcast environments that need stable, predictable addresses. Configuration is centralized on the DHCP server rather than on each individual device.

Key benefits of DHCP:

  • No IP conflicts (the DHCP server tracks addresses in use)
  • Simple device setup (devices can connect without manual configuration)
  • Centralized management (a single configuration change is applied automatically everywhere)

Initial IP configuration of Cyanview devices​

Cyanview devices such as the RCP and RIO ship with a factory-default static IP address on the 10.192.0.0/16 network. This address is generated from the device's serial number, using the last two bytes as the host portion, which guarantees uniqueness, predictable local communication, and a reliable recovery IP. An RCP with serial number CY-RCP-18-123 has a factory-default IP of 10.192.18.123.

DHCP is enabled by default alongside the static IP. If a DHCP server (such as a typical router) is present on the network, the device automatically obtains an IP address for internet access. This makes cloud connectivity for REMI production and remote support available out of the box, with no manual configuration required.

The default 10.192.0.0/16 static IP cannot be removed, but it doesn't conflict with other settings. If you need a static IP for a different network, simply add a new static IP. If you want it to persist across reboots or resets, be sure to check "Persistent" when saving.

It's a common misconception, but a single network interface can support multiple IP addresses simultaneously, allowing simultaneous communication with different subnets.

note

The factory-default IP cannot currently be removed, though this may change in the future. Since many users aren't familiar with IP configuration, keeping the factory-default IP ensures a reliable recovery path even without an easy factory-reset option.

Troubleshooting​

Checking connectivity with ping​

ping is a command-line tool (Command Prompt on Windows, Terminal on Mac) that sends an ICMP echo request to a specified IP address and waits for a response, letting you quickly check whether a device is reachable. A successful ping requires two-way communication to be confirmed.

Video tutorials are available for both Windows and Mac (Windows / Mac).

Identifying duplicate IPs​

Trial-and-error entry of a camera's IP address into various RCP settings fields until something works often ends up assigning the same IP address to both the camera and the RCP. This address conflict prevents normal communication and can make the device's configuration screen inaccessible. Checking for duplicate IPs should be one of the first steps when investigating a communication issue. If the root cause can't be identified, resetting the device configuration back to factory defaults is often the most efficient fix.

Windows tool: Advanced IP Scanner scans the network and reports duplicate IPs.

Mac/Linux tools: The arping and arp-scan command-line tools can be used to identify duplicate IPs (on Mac, they can be installed via Homebrew).

Detecting duplicate IPs on Linux with arping​

arping is a command-line tool that checks whether a given IP address is already in use, or duplicated, on the local network — useful for troubleshooting IP conflicts.

Basic usage:

arping <IP_ADDRESS>

Replace <IP_ADDRESS> with the address you want to check.

Interpreting the results:

  • Responses from multiple MAC addresses indicate a duplicate IP
  • A response from a single MAC address indicates the address is in use by one device
  • No response likely means the IP is unused

Example output showing a duplicate IP:

Unicast reply from 192.168.1.100 [AA:BB:CC:DD:EE:01]  1.123ms
Unicast reply from 192.168.1.100 [AA:BB:CC:DD:EE:02]  1.456ms
Sent 2 probes (1 broadcast(s))
Received 2 response(s)

Two distinct MAC addresses are visible here, indicating a duplicate IP.

Note:

Use the -D flag to perform Duplicate Address Detection (DAD), the same check a DHCP client would perform.

sudo arping -D -I <interface> <IP_ADDRESS>

Replace <interface> with your network interface name (e.g. eth0).

To explicitly specify the interface:

sudo arping -I eth0 192.168.1.100

Summary:

  • Use arping <IP> to check for a response
  • Multiple MAC addresses in the output indicate a duplicate IP
  • No response likely means the IP is free

Scanning an entire IP range for duplicates with arp-scan​

arp-scan scans an entire local network or a specific IP range and detects all devices currently responding — useful for getting a full picture of active devices and finding duplicate IPs.

Basic usage:

To scan a local subnet (e.g. 192.168.1.0/24):

sudo arp-scan 192.168.1.0/24

Replace 192.168.1.0/24 with your actual network range.

Interpreting the results:

  • A list of all responding IP addresses and their MAC addresses is printed
  • If the same IP address appears multiple times with different MAC addresses, that's a duplicate IP
  • Normally, each IP address should correspond to only one MAC address

Example output showing a duplicate IP:

192.168.1.100  AA:BB:CC:DD:EE:01  SomeVendor
192.168.1.100  AA:BB:CC:DD:EE:02  AnotherVendor

192.168.1.100 is being used by two different devices, indicating a duplicate.

Note:

You can specify the network interface with the -I flag.

sudo arp-scan -I eth0 192.168.1.0/24

On Mac, arp-scan can be installed via Homebrew (brew install arp-scan); on Linux, use your distribution's package manager.

Summary:

  • Use arp-scan <network> to list devices on a subnet
  • An IP address that repeats with different MAC addresses is a sign of a duplicate

All devices must be on the same network​

Most IP communication is bidirectional, requiring data to flow both ways between devices. Direct communication requires both devices to be on the same network (same netmask), with the correct IP address and subnet mask configured.

A common mistake is setting a camera to 10.192.0.0/16 with a netmask of 255.255.255.0, which places the camera on a different network from the RCP and prevents direct communication. TCP communication requires a two-way handshake, so it fails outright. With UDP communication, the camera may still receive packets from the RCP and respond to panel operations, but the RCP won't be able to receive the reply packets from the camera.

Frequently asked questions​

How do I change my computer's IP address?​

The first time you connect to a Cyanview device, you need to set your computer's IP address within the factory-default range 10.192.0.0/16. This lets you access the RCP/RIO configuration screen and assign the device a new IP. Afterward, restore your computer's normal network settings and access the device at its new IP.

Windows resources:

Mac resources: