Interfaces
lan Device: br-lan Connected: yes MAC: 52:54:00:12:34:56 RX: 2.03 MB (22369 Pkts.) TX: 21.67 MB (21289 Pkts.) ( Device: eth0 Connected: yes MAC: 52:54:00:12:34:56 RX: 2.35 MB (22394 Pkts.) TX: 21.67 MB (21303 Pkts.)) br-lan | Protocol: Static address Carrier: Present Uptime: 9h 27m 36s MAC: 52:54:00:12:34:56 RX: 2.03 MB (22369 Pkts.) TX: 21.67 MB (21289 Pkts.) IPv4: 192.168.1.1/24 IPv6: fdc2:994b:c053::1/60 |
Devices
| Device | Type | MAC Address | MTU | |
|---|---|---|---|---|
Device: br-lan Connected: yes MAC: 52:54:00:12:34:56 RX: 2.03 MB (22369 Pkts.) TX: 21.67 MB (21289 Pkts.)br-lan | Bridge device | 52:54:00:12:34:56 | 1500 | |
Device: eth0 Connected: yes MAC: 52:54:00:12:34:56 RX: 2.35 MB (22394 Pkts.) TX: 21.67 MB (21303 Pkts.)eth0 | Network device | 52:54:00:12:34:56 | 1500 |
Global network options
Unique Local Address (RFC4193) - prefix
fd00::/8 (the L bit is always 1). ULA for IPv6 is analogous to IPv4 private network addressing. This prefix is randomly generated at first install.The default DUID for this device, used when acting as a DHCP server or client. The client identifier can be overridden on a per-interface basis.
This identifier is randomly generated the first time the device is booted.
This identifier is randomly generated the first time the device is booted.
For packets originating from this device, e.g. VPN.
TCP services running on this device in the default VRF context (ie., not bound to any VRF device) shall work across all VRF domains.
Off means VRF traffic will be handled exclusively by sockets bound to VRFs.
Off means VRF traffic will be handled exclusively by sockets bound to VRFs.
UDP services running on this device in the default VRF context (ie., not bound to any VRF device) shall work across all VRF domains.
Off means VRF traffic will be handled exclusively by sockets bound to VRFs.
Off means VRF traffic will be handled exclusively by sockets bound to VRFs.
Enable packet steering across CPUs. May help or hinder network speed.
- Standard: none
- Suggested: 128
- 256
Directs packet flows to specific CPUs where the local socket owner listens (the local service). Note: this setting is for local services on the device only (not for forwarding).