This article outlines the required network settings for your Command Connector to communicate with non-Verkada cameras and Verkada Command. For more information on the required network settings for other Verkada product lines, see Required Network Settings.

The Command Connector must be assigned an IPv4 address to communicate on the LAN and with Verkada Command. The Command Connector obtains its IP address and network configurations using Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP).

Command Connectors use a DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the Command Connector where the DNS server is on the network, and it communicates using UDP port 53.

Verify the Command Connector and non-Verkada camera are on the same Local Area Network (LAN). Dynamic NAT or L3 translation is not supported between the devices.

The Command Connector and non-Verkada cameras need bidirectional traffic to communicate. The non-Verkada cameras must be online and discoverable over the network to establish a connection.

The Command Connector connects to non-Verkada cameras over the LAN using port 4100. Non-Verkada cameras use port 554 to serve RTSP streams and port 80, 8080, or 443 to serve ONVIF.

Verify these ports are allowed on the network:

Command Connectors require access to many endpoints to ensure they can communicate with Command and all features will be accessible. Many customers may want to allow the Command Connector to communicate with the general required endpoints.

These are the general domains to allow, applicable for all organizations:

If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, you can add the domains to your allowlist.

Need more help? Contact Verkada Support.