> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/transportation/getting-started/transportation-gateways-network-settings.md).

# Transportation Gateways Network Settings

Learn about the required network settings for the Verkada's KGX61 Ruggedized Transportation Gateway

{% hint style="warning" %}
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 %}

## Status LED

A flashing blue status LED on the gateway indicates the device is not communicating with Command. Check the status 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.

## Connectivity

The KGX61 contains an embedded eSIM. You can optionally insert your own SIM card into one or both of the upper nano-SIM card slots.

The gateway also includes a WAN RJ45 port and Wi-Fi.

## 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.

{% hint style="warning" %}
DNS over HTTPS (DoH) is currently not supported.
{% endhint %}

## Power

The KGX61 is powered by the vehicle electrical system through a terminal block and does not accept Power over Ethernet input. The terminal block accepts 10–20V DC up to 150W, or 20–30V DC up to 300W. The gateway also uses a separate ignition sensing wire.

For specifics on power requirements, see the [KGX61 datasheet](https://docs.verkada.com/docs/kgx61-ruggedized-transportation-gateway-datasheet.pdf).

## 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:**

| Domain/IP      | Protocol/Port         |
| -------------- | --------------------- |
| 34.216.15.26   | UDP:123               |
| \*.verkada.com | UDP:123 + TCP/UDP:443 |

If you prefer a more granular allowlist, you can add both IP addresses and full FQDNs 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 in Command.
{% endhint %}

{% tabs %}
{% tab title="United States" %}

| Domain/IP                                  | Protocol/Port |
| ------------------------------------------ | ------------- |
| 34.216.15.26                               | UDP:123       |
| api.control.verkada.com                    | TCP/UDP:443   |
| api.global-prod.control.verkada.com        | TCP/UDP:443   |
| api.prod-us-ohio.control.verkada.com       | TCP/UDP:443   |
| firmware.control.verkada.com               | TCP/UDP:443   |
| index.control.verkada.com                  | TCP/UDP:443   |
| relay.control.verkada.com                  | TCP/UDP:443   |
| relay.global-prod.control.verkada.com      | TCP/UDP:443   |
| relay.prod-us-ohio.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   |
| vnet.prod-us-ohio.command.verkada.com      | TCP/UDP:443   |
| {% endtab %}                               |               |

{% tab title="Europe" %}

| Domain/IP                                  | Protocol/Port |
| ------------------------------------------ | ------------- |
| 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   |
| {% endtab %}                               |               |

{% tab title="Australia" %}

| Domain/IP                                  | Protocol/Port |
| ------------------------------------------ | ------------- |
| api.global-prod.control.verkada.com        | TCP/UDP:443   |
| api.prod-ap-syd.control.verkada.com        | TCP/UDP:443   |
| index.prod-ap-syd.control.verkada.com      | TCP/UDP:443   |
| relay.global-prod.control.verkada.com      | TCP/UDP:443   |
| relay.prod-ap-syd.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.prod-ap-syd.command.verkada.com | TCP/UDP:443   |
| vnet.prod-ap-syd.command.verkada.com       | TCP/UDP:443   |
| {% endtab %}                               |               |
| {% endtabs %}                              |               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/transportation/getting-started/transportation-gateways-network-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.