Interfaces#
Network → Interfaces, at /interfaces. Each row is one interface as the configuration
declares it — Ethernet ports, VLANs, bridges, bonds, tunnels, WireGuard — joined with what
the router reports about it right now: link state, addresses, MAC address, MTU and
traffic. Clicking a row opens the interface panel, where everything about the
interface is edited; Add interface makes a new one, see Adding an
interface. Nothing is applied until the Commit Bar applies it.
Internal interfaces — the loopback, the device ingress shaping runs through, the wiring apps and containers use — are never listed. The agent decides which those are, for every page at once.
The table#
One row per interface, sorted by name, eth2 before eth10.
| Column | Where the value comes from |
|---|---|
| Interface | its name, with a drift badge when the router has it and the configuration does not |
| Type | Ethernet, VLAN, Bridge, Bond, WireGuard, Tunnel and the rest |
| Status | Up, Down or Unknown, as the router reports the link |
| Addresses | the addresses the router holds, or the configured ones when it has not been read; link-local addresses are left out |
| MAC address | the address the port uses now |
| MTU | the MTU in force now |
| Received, Sent | bytes since the interface came up — totals, not a rate |
| Description | the configured description |
A VLAN is a row of its own, eth0.20, like any other interface. VLANs that are networks —
with their own DHCP, DNS and access policy — are also listed, with those, on
Networks.
For a rate, the agent samples the counters every five seconds; the Overview shows the current rate of each uplink, and the History view keeps 24 hours of minutes and 31 days of hours per interface on the router.
Filtering and sorting#
The Filter box above the table matches across the row and shows a count; it filters in the browser and costs the router nothing. Every column heading sorts.
Present but not configured#
An interface the router reports that the configuration does not declare — a port that was hot-plugged, renamed by a new kernel, or never set up — is listed with a drift badge and the type Not configured. Opening it and saving configures it.
What the table does not show#
Internal interfaces: the loopback, the device ingress shaping runs through, container and app wiring, and the tunnel devices the kernel makes by itself. Nothing else is left out. Since 0.9.1 a VLAN is a row of its own, and every interface picker in the product — DHCP relay, IPv6, the mDNS repeater, conntrack sync — offers VLANs the same way, from the one list the agent serves.
The views#
The control in the header switches between them.
- Interfaces is the table above.
- Neighbours is the router's address resolution table: Neighbours.
- History is the traffic archive: Traffic history.
- CLI, in Advanced mode only, is the router's own text for the whole
interfacessubtree and its interface summary.
What the page costs the router#
Live interface detail is one read per configured interface, and every call into the router's API starts a process there. The agent caches each interface's answer for 20 seconds, longer than the page refreshes, so leaving the page open costs one round of reads every 20 seconds. An interface's offload state is read only when its panel is open, never on a timer.
If the router cannot be reached, the page shows the error and a Retry button rather than an empty table.
See also#
- The interface panel — every setting of an interface.
- Adding an interface — VLAN, bridge, bond, tunnel, VXLAN and dummy.
- Networks — VLANs with their own DHCP, DNS and access policy.
- Addressing — address values, DHCP on an interface, and MTU.
- Uplinks (multi-WAN) — the interfaces that carry a default route.
- QoS — shaping on an interface.