Skip to main content
Cellular Gateway Network Settings

Learn about the required network settings for the Verkada Cellular Gateways

Updated over a week ago

This article outlines the required network settings that your VerkadaCellular Gateways need to communicate with Verkada Command. The gateways can connect to your network by utilizing the WAN Failover mode. For more information on the required network settings for other Verkada product lines see Required Network Settings.

Note: Verkada devices are incompatible with LANs that require proxy servers or Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either is in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Verkada Command.

Status LED

A flashing blue status LED on the gateway indicates the device is not communicating with Command. Check thestatus LED doc for explanations of each LED pattern. If you see this behavior, check that the network is set up with the gateway’s requirements. If the problem persists, contact Verkada Support.

Note: When gateways are offline, alerts/events do not trigger. They continue to record data and sync with Command once they reconnect.

IP address

Verkada gateways must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Gateways use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations.

Domain Name System

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

Note: DNS over HTTPS (DoH) is currently not supported.

Power

Verkada GC31-Es are powered through Power over Ethernet (PoE). This means the network switch needs to provide power to the GC31-E, or a PoE injector needs to be utilized. A GC31 is powered through a barrel-jack adapter. For specifics on power requirements, see the gateway’s datasheet.

Firewall settings

Gateways 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 gateways to communicate with the general required endpoints.

These are the general domains to allow, applicable for all organization-regions:

  • 34.216.15.26 - UDP/123

  • *.verkada.com - UDP/123 + TCP+UDP/443

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 based on the region your devices are in.

Note: Your region is selected when you create an organization in Command.

Region: United States

  • 34.216.15.26 - UDP/123

  • api.control.verkada.com - TCP+UDP/443

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • device-nlb.verkada.com - TCP+UDP/443

  • firmware.control.verkada.com - TCP+UDP/443

  • index.control.verkada.com - TCP+UDP/443

  • nlb.verkada.com - TCP+UDP/443

  • relay.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • update.control.verkada.com - TCP+UDP/443

  • vconductor.command.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

  • vnet.command.verkada.com - TCP+UDP/443

Region: Europe

  • api.global-prod.control.verkada.com - TCP+UDP/443

  • api.prod2.control.verkada.com - TCP+UDP/443

  • index.prod2.control.verkada.com - TCP+UDP/443

  • relay.global-prod.control.verkada.com - TCP+UDP/443

  • relay.prod2.control.verkada.com - TCP+UDP/443

  • time.control.verkada.com - UDP/123

  • update.control.verkada.com - TCP+UDP/443

  • vconductor.global-prod.command.verkada.com - TCP+UDP/443

  • vconductor.prod2.command.verkada.com - TCP+UDP/443

  • vnet.prod2.command.verkada.com - TCP+UDP/443


Need more help? Contact Verkada Support.

Did this answer your question?