Mailing List Archive: NANOG: users

Trouble with IPv6 setup on Quagga

Index | Next | Previous | View Threaded

me at anuragbhatia

Aug 6, 2012, 10:08 PM

Post #1 of 8 (436 views)
Permalink

Trouble with IPv6 setup on Quagga

Hello everyone

I am having trouble with Quagga in setting up IPv6 BGP. So far it was
failing with external providers. Just now I gave it a try to setup BGP
session (IPv6 only) within our ASN between two routers.

From our other end router I see there is no acconcement, while I see blocks
being announced via Quagga. Also strange enough is that the number of
blocks I account - they all come as "withdrawl routes" on other router as
soon as Quagga is turned on.

E.g this is what I see on Quagga:

node4# show bgp ipv6 summary
BGP router identifier 199.116.78.28, local AS number 54456
RIB entries 18741, using 1757 KiB of memory
Peers 1, using 4560 bytes of memory

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
2607:1b00:10:a::1
4 54456 6865 5 0 0 0 00:00:05 9798

Total number of neighbors 1
node4#

So BGP session is up. Next if I check advertised routes, it goes like:

node4# show bgp ipv6 neighbors 2607:1b00:10:a::1 advertised-routes
BGP table version is 0, local router ID is 199.116.78.28
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 2607:1b00:d1::/48
:: 0 100 32768 i
*> 2607:1b00:d2::/48
:: 0 100 32768 i

Total number of prefixes 2
node4#

I don't see these routes in other router at all.

Here's what my Quagga bgpd.conf looks like:

hostname node4
timers bgp 4 16

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

Was wondering if someone can point in me right direction since both of
these prefixes are (annnounced and ?) withdrawn as soon as I restart Quagga.

Thanks.

--

Anurag Bhatia
Web: anuragbhatia.com
Skype: anuragbhatia.com

Linkedin <http://in.linkedin.com/in/anuragbhatia21> |
Twitter<https://twitter.com/anurag_bhatia>|
Google+ <https://plus.google.com/118280168625121532854>

mch-nanog at xs4all

Aug 7, 2012, 1:51 AM

Post #2 of 8 (424 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

> I am having trouble with Quagga in setting up IPv6 BGP. So far it was
> failing with external providers. Just now I gave it a try to setup BGP
> session (IPv6 only) within our ASN between two routers.
>
> From our other end router I see there is no acconcement, while I see blocks
> being announced via Quagga. Also strange enough is that the number of
> blocks I account - they all come as "withdrawl routes" on other router as
> soon as Quagga is turned on.

I recall some issues with the value of the next-hop in the BGP messages in the past. Haven't been around Quagga in recent times, don't know if this is still the case. If possible you might want to catch a BGP packet with tcpdump and verify the value in there makes sense to the other side.

Got bitten by this before and took me ages to figure out the other side was dropping my updates because the next-hop couldn't be resolved.

Marco

tom at ninjabadger

Aug 7, 2012, 2:35 AM

Post #3 of 8 (422 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

Hi Anurag,

> node4# show bgp ipv6 neighbors 2607:1b00:10:a::1 advertised-routes
> BGP table version is 0, local router ID is 199.116.78.28
> Status codes: s suppressed, d damped, h history, * valid, > best, i -
> internal,
> r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 2607:1b00:d1::/48
> :: 0 100 32768 i
> *> 2607:1b00:d2::/48
> :: 0 100 32768 i
>
> Total number of prefixes 2

TH: That next-hop does look suspect. If they're on the same subnet, try
disabling next-hop-self. It will just use link-local addressing on the
foreign side, should the next hop be unreachable.

It could be that with next-hop-self configured and no IPv6 address on lo,
this isn't working correctly. Do you have a global address on lo?

> Here's what my Quagga bgpd.conf looks like:
>
> hostname node4
> timers bgp 4 16
>
> router bgp 54456
> bgp router-id 199.116.78.28
> redistribute connected metric 1
> redistribute static metric 1

TH: One thing you should add for sanity:

no bgp default ipv4-unicast

Otherwise Quagga will default to advertising IPv4 address family via IPv6
neighbors.

'bgp network import-check' is also useful to ensure Quagga behaves in the
same way as a Cisco/Juniper router when it comes to advertisements (this
goes for both address families).

> 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

TH: This looks fine otherwise.

Tom

olipro at 8

Aug 8, 2012, 12:37 AM

Post #4 of 8 (418 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

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.

Regards,
Oliver

nanog at stefan-neufeind

Aug 8, 2012, 4:29 AM

Post #5 of 8 (417 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

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

james at towardex

Aug 9, 2012, 12:46 PM

Post #6 of 8 (418 views)
Permalink

RE: Trouble with IPv6 setup on Quagga [In reply to]

Most likely the trouble you're having is bgpd being unable to reference
zebra RIB via socket.

Make sure zebra is running and that your next-hop is visible as directly
connected when doing 'sh ipv6 route' under zebra vty.

James

-----Original Message-----
From: Anurag Bhatia [mailto:me [at] anuragbhatia]
Sent: Tuesday, August 07, 2012 1:08 AM
To: NANOG Mailing List
Subject: Trouble with IPv6 setup on Quagga

Hello everyone

I am having trouble with Quagga in setting up IPv6 BGP. So far it was
failing with external providers. Just now I gave it a try to setup BGP
session (IPv6 only) within our ASN between two routers.

>From our other end router I see there is no acconcement, while I see
>blocks
being announced via Quagga. Also strange enough is that the number of blocks
I account - they all come as "withdrawl routes" on other router as soon as
Quagga is turned on.

E.g this is what I see on Quagga:

node4# show bgp ipv6 summary
BGP router identifier 199.116.78.28, local AS number 54456 RIB entries
18741, using 1757 KiB of memory Peers 1, using 4560 bytes of memory

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
2607:1b00:10:a::1
4 54456 6865 5 0 0 0 00:00:05 9798

Total number of neighbors 1
node4#

So BGP session is up. Next if I check advertised routes, it goes like:

node4# show bgp ipv6 neighbors 2607:1b00:10:a::1 advertised-routes BGP
table version is 0, local router ID is 199.116.78.28 Status codes: s
suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, R Removed Origin codes: i - IGP, e -
EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 2607:1b00:d1::/48
:: 0 100 32768 i
*> 2607:1b00:d2::/48
:: 0 100 32768 i

Total number of prefixes 2
node4#

I don't see these routes in other router at all.

Here's what my Quagga bgpd.conf looks like:

hostname node4
timers bgp 4 16

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

Was wondering if someone can point in me right direction since both of these
prefixes are (annnounced and ?) withdrawn as soon as I restart Quagga.

Thanks.

--

Anurag Bhatia
Web: anuragbhatia.com
Skype: anuragbhatia.com

Linkedin <http://in.linkedin.com/in/anuragbhatia21> |
Twitter<https://twitter.com/anurag_bhatia>|
Google+ <https://plus.google.com/118280168625121532854>

vicky at geeks

Aug 9, 2012, 12:55 PM

Post #7 of 8 (412 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Aug 7, 2012, at 1:51 AM, Marco Hogewoning wrote:

>> I am having trouble with Quagga in setting up IPv6 BGP. So far it was
>> failing with external providers. Just now I gave it a try to setup BGP
>> session (IPv6 only) within our ASN between two routers.
>>
>> From our other end router I see there is no acconcement, while I see blocks
>> being announced via Quagga. Also strange enough is that the number of
>> blocks I account - they all come as "withdrawl routes" on other router as
>> soon as Quagga is turned on.
>
> I recall some issues with the value of the next-hop in the BGP messages in the past. Haven't been around Quagga in recent times, don't know if this is still the case. If possible you might want to catch a BGP packet with tcpdump and verify the value in there makes sense to the other side.
>

We were having those issue with quagga-0.99.15 and cisco routers; haven't tested recent versions.

We used a route map to fix the ipv6 next hop for outbound announcements in quagga.

> Got bitten by this before and took me ages to figure out the other side was dropping my updates because the next-hop couldn't be resolved.
>
> Marco

Regards,

Vicky Shrestha

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iQEcBAEBAgAGBQJQJBWuAAoJEGi4SIJCvhMLKhQH/i7dWdxBRh/2JyR0C/lWppq7
/y67GAUJo6Bc68Hpyma8BzNeYo/+YRarDbpz07dCFbzEHMiTrSLdN/CMVUWAkYxF
YBRXIIQuTRx8X+JYCx+egi7WDDHreIljE39OUmNtSZR0NVf3Ygot5qKXbDSqzFgJ
4RuxnYgI2ZBNN3X9up+PWJNdYI/49KanDl3RX62cGjQLQSqQRQWiwMWCXK0ufF2E
+xCZeUvkiqXnKWlF030ypHorGZoKX4JyuAj6SeS9yP1NTHgP6E57Xa0lvZ+v61Gx
Dml0o9JptNTctJ1cDeeWahRlgJx4yjfyUe0ZyIZAz9drZ4tgb3trC9cCHMNVV7Y=
=jFdq
-----END PGP SIGNATURE-----

me at anuragbhatia

Aug 14, 2012, 11:01 AM

Post #8 of 8 (380 views)
Permalink

Re: Trouble with IPv6 setup on Quagga [In reply to]

Hello everyone

Just quick update - Yes it was issue with older version of Quagga + for
some strange reason things don't work unless I restart zebra after
restarting bgpd.

Thanks for help everyone. Really appreciate it.

On Thu, Aug 9, 2012 at 3:55 PM, Vicky Shrestha <vicky [at] geeks> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Aug 7, 2012, at 1:51 AM, Marco Hogewoning wrote:
>
> >> I am having trouble with Quagga in setting up IPv6 BGP. So far it was
> >> failing with external providers. Just now I gave it a try to setup BGP
> >> session (IPv6 only) within our ASN between two routers.
> >>
> >> From our other end router I see there is no acconcement, while I see
> blocks
> >> being announced via Quagga. Also strange enough is that the number of
> >> blocks I account - they all come as "withdrawl routes" on other router
> as
> >> soon as Quagga is turned on.
> >
> > I recall some issues with the value of the next-hop in the BGP messages
> in the past. Haven't been around Quagga in recent times, don't know if this
> is still the case. If possible you might want to catch a BGP packet with
> tcpdump and verify the value in there makes sense to the other side.
> >
>
> We were having those issue with quagga-0.99.15 and cisco routers; haven't
> tested recent versions.
>
> We used a route map to fix the ipv6 next hop for outbound announcements in
> quagga.
>
>
> > Got bitten by this before and took me ages to figure out the other side
> was dropping my updates because the next-hop couldn't be resolved.
> >
> > Marco
>
> Regards,
>
>
> Vicky Shrestha
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
>
> iQEcBAEBAgAGBQJQJBWuAAoJEGi4SIJCvhMLKhQH/i7dWdxBRh/2JyR0C/lWppq7
> /y67GAUJo6Bc68Hpyma8BzNeYo/+YRarDbpz07dCFbzEHMiTrSLdN/CMVUWAkYxF
> YBRXIIQuTRx8X+JYCx+egi7WDDHreIljE39OUmNtSZR0NVf3Ygot5qKXbDSqzFgJ
> 4RuxnYgI2ZBNN3X9up+PWJNdYI/49KanDl3RX62cGjQLQSqQRQWiwMWCXK0ufF2E
> +xCZeUvkiqXnKWlF030ypHorGZoKX4JyuAj6SeS9yP1NTHgP6E57Xa0lvZ+v61Gx
> Dml0o9JptNTctJ1cDeeWahRlgJx4yjfyUe0ZyIZAz9drZ4tgb3trC9cCHMNVV7Y=
> =jFdq
> -----END PGP SIGNATURE-----
>
>

--

Anurag Bhatia
Web: anuragbhatia.com
Skype: anuragbhatia.com

Linkedin <http://in.linkedin.com/in/anuragbhatia21> |
Twitter<https://twitter.com/anurag_bhatia>|
Google+ <https://plus.google.com/118280168625121532854>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads