[155459] in North American Network Operators' Group
Re: Trouble with IPv6 setup on Quagga
daemon@ATHENA.MIT.EDU (Vicky Shrestha)
Thu Aug 9 15:55:55 2012
From: Vicky Shrestha <vicky@geeks.net.np>
In-Reply-To: <EA4EA1D8-2611-4B5F-9644-92726D9F57E3@xs4all.nl>
Date: Thu, 9 Aug 2012 12:55:26 -0700
To: Nanog <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
-----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.
>>=20
>> =46rom 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.
>=20
> 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.
>=20
We were having those issue with quagga-0.99.15 and cisco routers; =
haven't tested recent versions. =20
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.
>=20
> 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=3D
=3DjFdq
-----END PGP SIGNATURE-----
