> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/self-hosted/enterprise/deployment-manager/making-changes/configure-device-network.md).

# Configure Device Network

Set device IP addressing, gateway, DNS, and hostname from the cloud in the Networking tab.

You can set a device's IP addressing, gateway, DNS, and hostname from the cloud in the device's "Networking" tab, instead of editing config files on the device.

{% hint style="info" %}
Network configuration requires a current device agent and network telemetry. Ubuntu hosts also need active NetworkManager and `nmcli`; hostname changes and "DHCP Server" are supported only on Roboflow OS.
{% endhint %}

By default a device manages its own network (DHCP defaults or USB provisioning) and the cloud leaves it alone. To take over, open "Networking", enable "Extended network diagnostics", save, and wait for the next device heartbeat. Then click "Manage network from cloud". To hand control back, click "Stop managing from cloud".

## Configure a Port

Click "Add Port", or one of the detected-interface shortcuts next to it, to add a port. For each port:

* "Port": choose a detected interface or enter an interface name or MAC address. Ports are keyed by MAC address so configurations survive interface renames.
* Mode: "Static IP", "DHCP", "DHCP Server", or "Disabled".
* For "Static IP", set "Address (ip/prefix)" (ex: 192.168.1.50/24), "Gateway", and "DNS servers". Set "Gateway" on only one port.

A green dot next to an interface means a cable is connected, gray means no link.

On Roboflow OS, ports you do not configure stay on DHCP, and saving with no ports resets all ports to DHCP. Selecting "Static IP" replaces DHCP on that port, and "Disabled" takes the port down. On Ubuntu, other NetworkManager profiles stay in place; removing a managed port restores autoconnect on profiles Roboflow had suppressed.

Use "Hostname" to set the device hostname and "Fallback DNS servers (all ports)" to set DNS servers used across every port.

## Dedicated Camera Port

Turn on "Dedicated camera port" to let Edge manage Basler GigE networking on that interface, so you only need a serial number to [add a stream](/deployment/self-hosted/enterprise/deployment-manager/setting-up/add-a-stream.md).

Use it for a direct camera connection or an isolated camera network, never an uplink or shared production network. Ubuntu requires a static address on the port. Roboflow OS can choose a camera subnet when no address is set. A configured subnet cannot overlap another port's; saving with an overlap is rejected.

## Serve DHCP to a Camera Switch

On Roboflow OS, set a port to "DHCP Server" to have the device hand out addresses on that port. Use this for an isolated switch behind the device, such as a camera network with no router of its own. Set:

* "Address (server ip/prefix)": the device's own address on that network (ex: 192.168.10.1/24).
* "DHCP range (start–end)": the pool to hand out (ex: 192.168.10.100-192.168.10.200). The range must sit inside the port's subnet and cannot include the device's own address.
* "DHCP DNS servers (optional)": DNS servers to give clients.

Once the device serves leases, the "Network Interfaces" panel in the [Resource Monitor](/deployment/self-hosted/enterprise/deployment-manager/monitoring/view-the-resource-monitor.md) lists them under that port with each client's IP, MAC, hostname, lease expiry, and whether the device can reach it. GigE cameras are labeled in the "Identity" column, either matched to a camera the device already enumerated or identified by the MAC address vendor.

When you save, the device applies the configuration and attempts to restore the previous settings if application fails or the Roboflow API becomes unreachable afterward. Check [Activity](/deployment/self-hosted/enterprise/deployment-manager/monitoring/view-device-activity.md) for the result and confirm that the device reconnects.

## Test Connectivity

On supported firmware, open the device's "Networking" tab and use "Test connectivity" to run a ping, DNS lookup, TCP port check, or HTTP request from the device. The queued command is not a completed test: read its result in that panel. If no result arrives, report it as unverified and check that the device is online and supports connectivity tests.

## Extended Network Diagnostics

Enable the "Extended network diagnostics" toggle to have the device report deeper diagnostics in its healthcheck, including switch LLDP neighbors, DHCP leases, ARP table, and listening ports. Enable it before adopting cloud network management or when troubleshooting a network issue.