> For the complete documentation index, see [llms.txt](https://kb.motion.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.motion.cloud/motion-hub-hardware/networking/motion-hub-networking.md).

# Motion Hub Networking

## Overview <a href="#overview" id="overview"></a>

In this article, we'll talk about some of the basics of ensuring your Motion Hub can talk to the various devices that are connected to the same network.

## Firewalls <a href="#firewalls" id="firewalls"></a>

This part should be simple, as Motion Hub is designed to easily connect itself to the cloud once it is provided internet access.&#x20;

### Inbound Rules <a href="#inbound_rules" id="inbound_rules"></a>

Motion Hub does *not* require any **inbound** ports to be opened to connect to the cloud. For security, never deliberately route any public internet-facing traffic/ports to Motion Hub.

### Outbound Rules <a href="#outbound_rules" id="outbound_rules"></a>

Outbound communication to the cloud typically "just works", but networks with stricter policies may need to be configured to allow these **outbound** traffic rules.

#### Ports

| Port  | Protocol | Direction     |
| ----- | -------- | ------------- |
| `80`  | UDP      | Outbound only |
| `443` | TCP      | Outbound only |

#### Hosts <a href="#local_network" id="local_network"></a>

Motion Hub must be able to talk to these hosts:

| Host             | Required For                                                                                                                                                |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `*.motion.cloud` | <ul><li><p>Motion Cloud services, such as:</p><ul><li>Live data</li><li>Alarms</li><li>Software updates</li></ul></li><li>Remote support services</li></ul> |
| `*.nr-data.net`  | <ul><li>Remote support services</li></ul>                                                                                                                   |
| `*.newrelic.com` | <ul><li>Remote support services</li></ul>                                                                                                                   |

### MTU <a href="#local_network" id="local_network"></a>

By default, Motion Hub is configured for an MTU value of `1380`.

## Local Network <a href="#local_network" id="local_network"></a>

### Physical Ports <a href="#physical_ports" id="physical_ports"></a>

Motion Hubs with two networking ports are shipped with both ports enabled and configured for DHCP address assignment. Either port can be used.

### IP Address Assignment <a href="#ip_address_assignment" id="ip_address_assignment"></a>

By default, Motion Hub will receive its local IP address from a local DHCP server.

One static IP address per hub can be configured by submitting a support ticket at this time.

### Routing Considerations <a href="#routing_considerations" id="routing_considerations"></a>

Your Motion Hub must be able to communicate with relevant devices on your network, such as those communicating over Modbus TCP or BACnet/IP.&#x20;

Basic networks will often be small enough and lack routing restrictions, enabling communication right out of the box.

For more advanced network configurations that are more restrictive by default (e.g. larger enterprise environments), you (or your IT/networking engineers) must ensure any given Motion Hub has a route to communicate with the devices the Motion Hub needs to reach.

Special consideration may be needed for BACnet devices. [Learn more here](/motion-hub-hardware/networking/bacnet-ip-networking.md).

### IPv4 vs. IPv6

Motion Hub is tested on IPv4 and dual-stack (IPv4 + IPv6) networks only. IPv6-only networks are not officially supported, although Motion Hub may work without issue on IPv6-only networks.


---

# 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 current page URL with the `ask` query parameter:

```
GET https://kb.motion.cloud/motion-hub-hardware/networking/motion-hub-networking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.