-
Notifications
You must be signed in to change notification settings - Fork 2
bgp llnh
Pre-Alpha. This page describes behavior that may change.
Link-Local Next Hop for IPv6 (RFC 2545). Advertises a link-local IPv6 address as the next hop alongside the global next hop.
Capabilities.
plugin {
internal llnh { use bgp-llnh }
}
bgp {
peer upstream {
capability {
llnh;
}
}
}
The plugin registers the LLNH capability (code 77) and the wire encoding rules for carrying a link-local IPv6 next hop in MP_REACH_NLRI. When enabled, IPv6 routes advertised to the peer carry both the global and link-local addresses, as expected by peers on a shared link.
The plugin is usually necessary for iBGP or eBGP peering over an IPv6 shared link where the remote next hop must be the link-local address for forwarding to work correctly.
- Works with
bgp-nlri-*family plugins that carry IPv6 NLRIs.
main/internal/component/bgp/plugins/llnh/
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