-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BGP add path support #247
Comments
Please use per-family config style like
|
The latest code explicitly returns an error for global add path config. |
Thanks - that config works great on gobgp but not rustybgp. Here's my new full config, which works great and receives additional paths under gobgp, but the same config under rustybgp is stuck in Idle with the peer reporting "required capability missing". global:
config:
as: 34553
router-id: 192.168.90.4
port: 179
apply-policy:
config:
default-import-policy: accept-route
default-export-policy: reject-route
neighbors:
- config:
peer-as: 34553
neighbor-address: 192.168.90.1
afi-safis:
- config:
afi-safi-name: ipv4-unicast
add-paths:
config:
receive: true |
Can you share the pcap file? I need open messages from both (one is rustybgp, and another is what?) |
The remote side is BIRD 2.0.7; admittedly an older version of BIRD, but given GoBGP works correctly I suspect an issue on the rustybgp side. See attached pcap |
Thanks! |
Fantastic, works great now. Thanks for the quick fix! |
With add-path receive enabled, rustybgp correctly detects that a peer is advertising the ADD-PATH capability, but doesn't import multiple routes:
Steps to reproduce
bgp.yml
:git clone https://github.com/osrg/rustybgp cd rustybgp git reset --hard 9a94087b81679af2304d1523c1bbde822be7010b cargo build --release ./target/release/rustybgpd -f bgp.yml
gobgp neigh
and confirm only ~900k routes receivedUsing gobgp with the same config works correctly.
The text was updated successfully, but these errors were encountered: