-
Notifications
You must be signed in to change notification settings - Fork 2
bgp filter prefix
Thomas Mangin edited this page May 14, 2026
·
2 revisions
Pre-Alpha. This page describes behavior that may change.
Named prefix-list filter (CIDR + ge/le + accept/reject). Matches routes by prefix with optional length constraints.
Policy.
Defined under bgp { policy { } } and referenced by name in peer filter chains:
bgp {
policy {
prefix-list customers {
entry 10.0.0.0/8 {
le 24;
action accept;
}
entry 172.16.0.0/12 {
ge 16;
le 28;
action accept;
}
}
}
filter {
import [ customers ];
}
}
Each entry is keyed by prefix. ge and le constrain the prefix length. action is accept (default) or reject. Entries are evaluated in order; first match wins.
internal/component/bgp/plugins/filter_prefix/
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