Trouble with IPv6 setup on Quagga

Stefan Neufeind nanog at
Wed Aug 8 11:29:18 UTC 2012

On 08/08/2012 09:37 AM, Oliver wrote:
> On Tuesday 07 August 2012 01:08:24 Anurag Bhatia wrote:
>> router bgp 54456
>>  bgp router-id
>>  redistribute connected metric 1
>>  redistribute static metric 1
>>  neighbor 2607:1b00:10:a::1 remote-as 54456
>>  neighbor 2607:1b00:10:a::1 next-hop-self
>>  address-family ipv6
>>  network 2607:1b00:d1::/48
>>  network 2607:1b00:d2::/48
>>  neighbor 2607:1b00:10:a::1 activate
>>  exit-address-family
> Specifying "next-hop-self" in the general BGP router config section is 
> equivalent to specifying it purely for IPv4 routes; you need to specify next-
> hop-self in the IPv6 address-family section.

And you might want to disable ("no neighbor ... activate") for the
default-protocol (IPv4) as otherwise Quagga tries to advertise IPv4 over
the same session as well - which you usually wouldn't want to.
I've seen cases where both sides ran Quagga and wondered where all the
(unfiltered) IPv4-routes came from :-)


More information about the NANOG mailing list