Closed githubpol closed 7 years ago
brijohn
commented
7 years ago Looking at your configuration it seems you are using an ipv6 address for the router id. This is actually an invalid configuration since in BGP the router-id is a 32 bit number.
Try setting it to the same ip address used for your v4 peer and see if that works any better for you.
githubpol
commented
7 years ago Thanks! I had tried that before, but at that time I hadn't realized that I needed ebgp-multihop at the Quagga end. After your comment I tried changing router-id again, and now everything works fine in both IPv4 and IPv6. Thanks very much!
thomas-mangin
commented
7 years ago @brijohn Thank you very much for helping ! Much appreciated. I assume the error messages went to syslog ...
ISSUE TYPE
OS
FreeBSD 10.3-RELEASE-p19
VERSION
exabgp --version doesn't output anything at all, but the exabgp version is 3.4.18, installed with "pkg install exabgp"
ENVIRONMENT
exabgp --di also outputs nothing
CONFIGURATION
Quagga: router bgp x neighbor y.y.y.y remote-as y neighbor y:y:y:y::y remote-as y no neighbor y:y:y:y::y activate address-family ipv6 neighbor y:y:y:y::y activate
ExaBGP: (I have tried several different variations, but this is the one that seems most logical to me.) group IPv4 { neighbor x.x.x.x { router-id y.y.y.y; local-as y; peer-as x; family { ipv4 unicast; } static { route z.z.z.0/24 next-hop y.y.y.y; } } } group IPv6 { neighbor x:x:x::x { router-id y:y:y:y::y; local-as y; peer-as x; family { ipv6 unicast; } static { route z:z:z::/48 next-hop y:y:y:y::y; } } }
SUMMARY
The IPv4 peering works fine, and the IPv4 route is announced from ExaBGP to Quagga. But the IPv6 peering never comes up.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
IMPORTANCE
Medium. (This is not a critical issue at the moment, but if there doesn't seem to be a solution I will have to change from ExaBGP to Quagga, which would be unnecessary as I don't need to receive routes, I just need to announce one IPv4 route and one IPv6 route.)
Thanks!