Network Settings
3 minute read
The Network panel lets you view and configure your board’s network interfaces from the dashboard - IP addresses, DHCP or static addressing, gateway, and DNS resolvers - without touching the command line.
Open it by clicking Network in the header toolbar.
Works on Any Supported OS
The dashboard reads and applies network configuration using whichever stack your board runs, so the same panel works everywhere:
| Board OS | Network stack the dashboard drives |
|---|---|
| Raspberry Pi OS / Debian | NetworkManager |
| Ubuntu | systemd-networkd + netplan |
The platform detects the active network manager at runtime and uses the matching backend. You do not choose a backend or configure anything OS-specific - the panel looks and behaves the same on a Debian Cruiser and an Ubuntu Cruiser.
Viewing Interfaces
The panel lists every interface on the board with:
- Name (for example
eth0,wlan0, or the management uplink) - State - up, down, or dormant
- Method - DHCP or static
- IP address and subnet
- Gateway and DNS resolvers
- MAC address
The interface carrying the dashboard you are connected through is marked as the management uplink (protected). Changes to it follow the extra safety flow described below.
Switching Between DHCP and Static
- Click an interface to open its edit form.
- Choose DHCP to obtain an address automatically, or Static to set one yourself.
- For a static interface, enter the IP address with prefix (for example
10.0.1.41/24), an optional gateway, and optional DNS resolvers. - Click Apply.
DNS resolvers accept IPv4 addresses separated by commas or spaces. Leaving the DNS field empty clears the resolvers. On a DHCP interface, DNS is supplied automatically by the DHCP server - switch the interface to Static if you need to set specific resolvers.
Every interface change is recorded in the audit log with its before and after values.
Changing the Management Uplink (Protected)
The management uplink is the interface carrying the dashboard you are using right now. A bad change here could cut you off from the board, so the platform protects it with an explicit confirmation and a timed automatic rollback.
When you apply a change to the uplink:
- A confirmation prompt first tells you where to reconnect if the connection drops - the new
static address, or the board’s
hostname.localif you switched it to DHCP. (You may need to log in again and accept the certificate warning at the new address.) - After you confirm, the change is applied on a 90-second trial. A countdown banner appears at the top of the dashboard with a Confirm connectivity button.
- Click Confirm connectivity while you can still reach the dashboard to keep the change.
- If the timer runs out without confirmation, the board automatically reverts to the previous configuration, so a wrong address cannot lock you out.
The countdown banner survives a page reload - if your browser reconnects at the new address, the banner is still there with the remaining time. If the automatic revert itself fails, the banner shows a prominent revert FAILED warning telling you to reconnect via console or SSH and fix the configuration manually.
Non-uplink interfaces (a spare port, a static address on a secondary NIC) apply immediately with no countdown, because changing them cannot disconnect the dashboard.
Changing the Hostname
The Network panel also sets the board’s hostname. The hostname is used for hostname.local
discovery on the network and appears in the dashboard header and in the fleet view.
Related
- System Health - switch port link state and traffic
- Security and TLS - the audit log records every change
- Troubleshooting - what to do if you lose access
Last modified October 18, 2026