-
Notifications
You must be signed in to change notification settings - Fork 2
interface
Pre-Alpha. This page describes behavior that may change.
OS network interface monitoring and management. Discovers interfaces, manages units, addresses, bridges, VLANs, and sysctl settings, and publishes interface and address events to the bus.
Core.
Loaded automatically when an interface configuration block is present. The config root is interface.
interface {
ethernet eth0 {
mtu 9000;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
dummy lo1 {
unit 0 {
family inet {
address 10.255.0.1/32;
}
}
}
}
The YANG schema supports ethernet, dummy, veth, bridge, and loopback interface types. Each interface carries physical properties (MTU, MAC address, disable) and a list of logical units with addresses, VLAN IDs, sysctl overrides, and traffic mirroring configuration.
On startup the plugin loads a backend (netlink on Linux by default), applies the declared interface configuration, and starts a monitor that watches for OS-level interface changes. The monitor publishes events to the bus:
-
interface/createdandinterface/deletedfor link lifecycle. -
interface/upandinterface/downfor link state transitions. -
interface/addr/addedandinterface/addr/removedfor IP address changes. -
interface/dhcp/lease-acquired,interface/dhcp/lease-renewed, andinterface/dhcp/lease-expiredfor DHCP events.
Configuration reloads use a journaled transaction. The apply phase records a rollback closure that re-applies the previous config, and emits an interface-rollback event if the transaction is rolled back.
The interface model follows a JunOS-style two-layer design: physical interface plus logical units.
- The BGP reactor subscribes to interface events to react to link-state changes.
-
iface-netlinkis the default Linux backend that performs the actual netlink operations. -
iface-dhcpis a separate plugin for DHCP client behaviour on managed interfaces. -
fib-kernelconsumes interface events to keep the Linux FIB consistent.
main/internal/component/iface/
Unreviewed draft. This wiki was authored in bulk and has not been reviewed. File corrections on the issue tracker.
- Overview
- YANG Model
- Editor Workflow
- Archive and Rollback
- System
- Interfaces
- BFD
- FIB
- Firewall
- Traffic Control
- L2TP/PPP
- VPP Data Plane
- RPKI
- TACACS+ AAA
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Logging
- Operational Reports
- Healthcheck
- MRT Analysis
- Upgrade and Restart
- Storage
- Policy
- Core
- Resilience
- Validation
- Capabilities
- Address Families
- Protocol
- Subsystems
- Infrastructure
- Route Server at an IXP
- Transit Edge with RPKI
- Public Looking Glass
- ExaBGP Migration Walkthrough
- FlowSpec Injection
- Chaos-Tested Peering
- AS Path Topology