Open Stack

On Fri, 2021-07-02 at 06:24 +0000, Manu B wrote:
> Hi everyone,
>  
> This is a doubt regarding existing IPv6 advertisement support for BGP
> in the current n-d-r repo.
> From the documentation, it is mentioned that to enable advertising
> IPv6 prefixes,
> create an address scope with ip_version=6 and a BGP speaker with
> ip_version=6.
>  
> We have a use case where v4 and v6 routes must be advertised using a
> single v4 peer.
>    1. How can we advertise both v4 and v6 routes using single v4
> peer?
you cant as far as i am aware.
i dont have  neutron-dynamic-routing enabled in my home setup anymore
but when i did i found you need 2 speakers.
> Do we have to create 2 BGP speakers ( one for v4 and another for v6)
yes although the issue i had with that was  that you can only schdule
one speaker to given host so on my singel node deployment i could only
have one of the two speakser running.
> Then create a single BGP v4 peer and add the same peer to both the
> speakers?
to get this working i had to assing two different asn to the two
differen speaker and create two peering session to my home router.
one for the ipv4 speaker and one for the ipv6 speaker.

as i said above i could only have one of the two schdeld to the singe
dragent i had running at a time but if i swapped between which one was
runing i got either the ipv4 routes or ipv6 routes advertised.

> Is this the correct approach or any other way?
i have no idea what the correct approch is but that is why i foudn
worked. if i had a second dragent runnign i coudl have had the cloud
advertise both in parallel this way its a shame that it can just
advertise ipv4 and ipv6 in the same speaker with one peering session.
the limitation seams to be on the neutron-dynamic-routing side not the
bgp protocol in this case.
>    1. Is there any other significance of version field in current BGP
> speaker model?
>  
> Thanks,
> Manu