[155407] in North American Network Operators' Group
Re: Trouble with IPv6 setup on Quagga
daemon@ATHENA.MIT.EDU (Stefan Neufeind)
Wed Aug 8 07:30:41 2012
Date: Wed, 08 Aug 2012 13:29:18 +0200
From: Stefan Neufeind <nanog@stefan-neufeind.de>
To: nanog@nanog.org
In-Reply-To: <1876003.nJFbuIMgX6@gentoovm>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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 199.116.78.28
>> 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 :-)
Regards,
Stefan
