-
Notifications
You must be signed in to change notification settings - Fork 2
fib p4
Pre-Alpha. This page describes behavior that may change. Experimental.
Experimental P4 dataplane backend. Installs routes into a P4 target instead of the Linux kernel.
Infrastructure.
plugin {
internal fib-p4 { use fib-p4 }
}
fib-p4 is an alternative FIB programming backend to fib-kernel. It consumes the same sysrib selection events but writes to a P4 target rather than the Linux kernel forwarding table. The target-specific details (which P4 target, which compiled pipeline, which tables) are configured outside Ze today.
The plugin exists as a proof of concept. It is not production-ready and the API is expected to change.
Do not deploy this in production. Use fib-kernel for any real deployment.
- Consumes
sysribselection events (same interface asfib-kernel). - Alternative to
fib-kernel. Loading both at the same time is not supported.
main/internal/plugins/fibp4/
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