-
Notifications
You must be signed in to change notification settings - Fork 2
iface netlink
Pre-Alpha. This page describes behavior that may change.
Netlink backend for the iface component. Default on Linux. Handles interface lifecycle, address management, bridges, VLANs, sysctl tuning, and traffic mirroring through pure netlink (no iproute2 shell-outs).
Infrastructure.
Selected implicitly as the default backend on Linux. No explicit configuration is needed unless you want to override the backend selection.
interface {
backend netlink; # Default
}
The plugin implements the 34-method Backend interface that iface uses to manipulate interfaces: create, delete, bring up, bring down, add address, remove address, configure a sysctl, enable STP, add a bridge member, set up traffic mirroring, and so on. Every operation goes through the Go vishvananda/netlink library and talks to the kernel directly.
It also runs the netlink multicast monitor that publishes bus events for every interface and address change, which is how the BGP reactor, the DHCP plugin, and the rest of the system react to link and address transitions.
- Loaded by the
ifacecomponent when thebackendleaf isnetlink(the default on Linux). -
iface-dhcpuses this plugin's address operations to install DHCP leases. - The BGP reactor subscribes to the monitor's bus events.
main/internal/plugins/ifacenetlink/
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
- VRRP
- BFD
- FIB
- OSPF
- IS-IS
- MPLS / LDP / RSVP-TE
- RSVP-TE
- SRv6
- Static Routes
- Policy Routing
- Firewall
- Traffic Control
- Class of Service
- L2TP/PPP
- PPPoE
- VPP Data Plane
- RPKI
- IPsec VPN
- TACACS+ AAA
- RADIUS AAA
- AS112 DNS
- Authorization
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Flow Export
- DDoS Mitigation
- Anomaly Detection
- Health Checks
- Audit Trail
- Production Diagnostics
- Logging
- Operational Reports
- Healthcheck
- Self-Update
- Zero-Touch Provisioning
- 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