# Guest Network Settings This article outlines the required network settings that your [Verkada Guest](https://docs.verkada.com/docs/verkada-guest-quick-start-guide.pdf) tablets and phones need to be able to communicate with the printer through the LAN and speak with [Verkada Command](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/getting-started/get-started-with-verkada-command). For more information on the required network settings for other Verkada product lines see [Required Network Settings](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/need-help/required-network-settings). {% hint style="warning" %} **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. {% endhint %} ## IP address Guest tablets and phones must be assigned an IPv4 address to communicate on the LAN and to Verkada Command. Guest devices use Dynamic Host Configuration Protocol (DHCP) and User Datagram Protocol (UDP) to obtain their IP addresses and network configurations. If you require your Guest device to have a specific IP address, create a DHCP reservation using the device’s Media Access Control (MAC) address (found on the device’s label). ## Domain Name System Guest tablets and phones 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 Guest device where the DNS server is on the network and the Guest device communicates using UDP port 53. {% hint style="warning" %} **Note**: DNS over HTTPS (DoH) is currently not supported. {% endhint %} ## Firewall settings Guest tablets and phones 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 Guest devices to communicate with the general required endpoints. These are the general domains to allow, **applicable for all organization-regions**: | Domain/IP | Protocol/Port | | ----------------- | --------------------- | | 34.216.15.26 | UDP:123 | | 34.203.250.0/23 | UDP:10000-20000 | | 35.156.191.128/25 | UDP:10000-20000 | | 52.215.127.0/24 | UDP:10000-20000 | | 54.65.63.192/26 | UDP:10000-20000 | | 54.169.127.128/26 | UDP:10000-20000 | | 54.171.127.192/26 | UDP:10000-20000 | | 54.172.60.0/23 | UDP:10000-20000 | | 54.244.51.0/24 | UDP:1024-65535 | | 168.86.128.0/18 | UDP:10000 - 60000 | | 54.252.254.64/26 | UDP:10000-20000 | | 177.71.206.192/26 | UDP:10000-20000 | | \*.verkada.com | UDP:123 + TCP/UDP:443 | If you prefer a more granular allowlist, you can add IP addresses, full FQDNs, and wildcard domains to your firewall rules based on the region where your devices are located. {% hint style="warning" %} Your region is selected when you [create an organization](https://app.gitbook.com/s/NRq5qDDjsYNxwNzF1bcB/getting-started/get-started-with-verkada-command) in Command. {% endhint %} {% tabs %} {% tab title="United States" %} | Domain/IP | Protocol/Port | | ------------------------------------------------------------------------------- | ---------------------------------------- | | 34.216.15.26 | UDP:123 | | 3.235.111.128/25 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 34.203.250.0/23 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 34.203.254.0/24 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 34.216.110.128/27 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 35.156.191.128/25 | UDP:10000-20000 | | 44.234.69.0/25 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 52.215.127.0/24 | UDP:10000-20000 | | 54.65.63.192/26 | UDP:10000-20000 | | 54.169.127.128/26 | UDP:10000-20000 | | 54.171.127.192/26 | UDP:10000-20000 | | 54.172.60.0/23 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 54.244.51.0/24 | UDP:10000-60000 + TCP/UDP:443 + UDP:3478 | | 168.86.128.0/18 | UDP:10000 - 60000 | | 54.252.254.64/26 | UDP:10000-20000 | | 177.71.206.192/26 | UDP:10000-20000 | | vdoorman.command.verkada.com | TCP:443 | | vdoormansocket.command.verkada.com | TCP:443 | | vdoorman.prod1.command.verkada.com | TCP:443 | | verkada-guest-management-public-us-west-2-prod1.s3.amazonaws.com | TCP:443 | | verkada-guest-management-us-west-2-prod1.s3.amazonaws.com | TCP:443 | | verkada-guest-management-customer-upload-files-us-west-2-prod1.s3.amazonaws.com | TCP:443 | | baltazar.microblink.com | TCP:443 | | ping.microblink.com | TCP:443 | | us1.vss.twilio.com | TCP:443 | | us2.vss.twilio.com | TCP:443 | | \*.twilio.com | TCP/UDP:443 + UDP:3478 | | \*.twiliocdn.com | TCP/UDP:443 + UDP:3478 | | sdkgw\.us1.twilio.com | TCP:443 | | {% endtab %} | | {% tab title="Europe" %} | Domain/IP | Protocol/Port | | ------------------------------------------------------------------------------- | --------------- | | 34.216.15.26 | UDP:123 | | 34.203.250.0/23 | UDP:10000-20000 | | 35.156.191.128/25 | UDP:10000-20000 | | 52.215.127.0/24 | UDP:10000-20000 | | 54.65.63.192/26 | UDP:10000-20000 | | 54.169.127.128/26 | UDP:10000-20000 | | 54.171.127.192/26 | UDP:10000-20000 | | 54.172.60.0/23 | UDP:10000-20000 | | 54.244.51.0/24 | UDP:1024-65535 | | 54.252.254.64/26 | UDP:10000-20000 | | 177.71.206.192/26 | UDP:10000-20000 | | vdoorman.command.verkada.com | TCP:443 | | vdoormansocket.command.verkada.com | TCP:443 | | vdoorman.prod2.command.verkada.com | TCP:443 | | verkada-guest-management-public-us-west-2-prod2.s3.amazonaws.com | TCP:443 | | verkada-guest-management-us-west-2-prod2.s3.amazonaws.com | TCP:443 | | verkada-guest-management-customer-upload-files-us-west-2-prod2.s3.amazonaws.com | TCP:443 | | {% endtab %} | | {% tab title="Australia" %} | Domain/IP | Protocol/Port | | ------------------------------------------------------------------------------------- | ----------------- | | 34.216.15.26 | UDP:123 | | 34.203.250.0/23 | UDP:10000-20000 | | 35.156.191.128/25 | UDP:10000-20000 | | 52.215.127.0/24 | UDP:10000-20000 | | 54.65.63.192/26 | UDP:10000-20000 | | 54.169.127.128/26 | UDP:10000-20000 | | 54.171.127.192/26 | UDP:10000-20000 | | 54.172.60.0/23 | UDP:10000-20000 | | 54.244.51.0/24 | UDP:1024-65535 | | 168.86.128.0/18 | UDP:10000 - 60000 | | 54.252.254.64/26 | UDP:10000-20000 | | 177.71.206.192/26 | UDP:10000-20000 | | vdoormansocket.command.verkada.com | TCP:443 | | vdoorman.command.verkada.com | TCP:443 | | vdoorman.prod-ap-syd.command.verkada.com | TCP:443 | | verkada-guest-management-public-us-west-2-prod-ap-syd.s3.amazonaws.com | TCP:443 | | verkada-guest-management-us-west-2-prod-ap-syd.s3.amazonaws.com | TCP:443 | | verkada-guest-management-customer-upload-files-us-west-2-prod-ap-syd.s3.amazonaws.com | TCP:443 | | {% endtab %} | | | {% endtabs %} | | {% hint style="info" %} Use the [Verkada Network Tester](https://network-tester.support.verkada.com/) to verify your devices can connect to Verkada Command. Select your region and the **Guest** product type to run the check. The following endpoints must be allowed on your network for the test to work: * speed.cloudflare.com * network-tester.support.verkada.com {% endhint %}