Help with IPv6 peer configuration in ExaBGP 3.4.18

[Peter]

Hello!

I'm tearing my hair out not getting IPv6 peering to work.

I have an IPv4 peer from exabgp to quagga working fine.

Now I want to setup an IPv6 peer from exabgp to quagga.

In the quagga end I configure this the same way I configure
all my other IPv6 peers, but how do I configure this in exabgp?

I find very few sample IPv6 configs by googling, and all my
attempts at config either silently (nothing at all in the
log file) fail starting exabgp, or don't succeed in connecting
to the quagga IPv6 peer. I have confirmed that the exabgp server
can connect to port 179 on the quagga servers IPv6 address, so
this all seems to be a config problem.

This is my working IPv4 config, with everything interesting x:ed out:
group x {
static {
route x next-hop x;
}
neighbor x {
router-id x;
local-address x;
local-as x;
peer-as x;
}
}

I have tried adding the IPv6 peer in the same group, in a group
of its own, tried removing group and putting both peers at the
global level, and tried lots of other things. Nothing works.

Thanks for any ideas!
A working sample IPv6 config for exabgp 3.4.18 would be great.

Peter

[Thomas Mangin]

You should look at : 

https://github.com/Exa-Networks/exabgp/blob/3.4/qa/conf/ipv6grouping.conf

Just copy the family section.

Just noticed the the simple v6 configuration is buggy as not used for testing ..

Thomas

--
You received this message because you are subscribed to the Google Groups "exabgp-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exabgp-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter]

I tried that, in several different variations. But it doesn't work.

This is my quagga configuration:

router bgp x
neighbor x.x.x.x remote-as x
neighbor x:x:x:x::x remote-as x
no neighbor x:x:x:x::x activate
address-family ipv6
neighbor x:x:x:x::x activate

This is what I use for all other peers that run both IPv4 and IPv6.
So I think that I need to have two peers in exabgp, one connecting
to the IPv4 address in the quagga, and one connecting to the IPv6
address in the quagga. But I tried also this in several different
variations, and with/without "family", and didn't get it to work.

The IPv4 peer connects fine, and announces the IPv4 route.
But it doesn't announce the IPv6 route.

Thanks!

Peter

[Thomas Mangin]

Please create an issue on GitHub and provide the information requested.

Thomas

Sent from my iPad

[Peter]

Problem solved, thanks Brian!
It was a combination of missing ebgp-multihop at the Quagga end,
and using a bad (ie IPv6) router-id in ExaBGP.

Peter