Mailing List Archive

IPv6 BGP routes from a directly connected peer are not accepted in the routing table
Hello,

I'm restoring this topic I've found on "quagga-users 14807".

Regarding IPv6 ...
Our setup is using two quagga routers.
The routers run OSPF6d for internal routing
They have a iBGP session between them and each has a eBGP peering
(direct) with our provider.
The provider only announces the default route ::/0 to both routers for
high availability.
We mark the routes received in one router as localpref=201 and in the
other localpref=302
I can ping 2001:690:810:5::1 in the router configured to be the active
one (LP=302) but the route isn't placed in the routing table reporting
"inaccessible" (see show command).

Running:
> Quagga 1.2.2-gentoo ().
> Copyright 1996-2005 Kunihiro Ishiguro, et al.
> configured with:
> --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --docdir=/usr/share/doc/quagga-1.2.2 --htmldir=/usr/share/doc/quagga-1.2.2/html --libdir=/usr/lib64 --enable-exampledir=/usr/share/doc/quagga-1.2.2/samples --enable-irdp --enable-isisd --enable-isis-topology --enable-pimd --enable-user=quagga --enable-group=quagga --enable-vty-group=quagga --with-cflags=-O2 -pipe -march=native -mtune=native -fno-strict-aliasing --with-pkg-extra-version=-gentoo --sysconfdir=/etc/quagga --localstatedir=/run/quagga --disable-static --disable-capabilities --disable-pcreposix --disable-fpm --disable-tcp-zebra --disable-doc --enable-multipath=0 --enable-vtysh --without-libpam --disable-nhrpd --disable-protobuf --enable-ripngd --enable-ospf6d --enable-rtadv
> scratchy# sh ipv6 bgp ::/0
> BGP routing table entry for ::/0
> Paths: (2 available, best #1, table Default-IP-Routing-Table, not advertised to EBGP peer)
> Not advertised to any peer
> 1930
> 2001:690:810:6::1 from 2001:690:2008::100e (193.137.220.218)
> Origin IGP, localpref 201, valid, internal, best
> Community: no-export
> Last update: Wed Dec 13 18:28:45 2017
>
> 1930
> 2001:690:810:5::1 (inaccessible) from 2001:690:810:5::1 (193.136.5.13)
> (fe80::12f3:11ff:fe47:afa9)
> Origin IGP, localpref 302, tag 1930, invalid, external
> Community: no-export
> Last update: Wed Dec 13 18:28:48 2017

Is this expected?
I'm receving the route in the outbound interface and the address is
acessible via ND/ping
Any soluting via reconfiguration or official software update (excluding
personal patch)

TIA.

--
Best regards,

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Pedro Ribeiro
Politécnico de Lisboa, Serviços da Presidência
Departamento de Sistemas de Informação e Comunicações
Phone: +351 210 464 700 (general) / VoIP: 80100
Helpdesk: helpdesk@net.ipl.pt / https://www.net.ipl.pt
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users
Re: IPv6 BGP routes from a directly connected peer are not accepted in the routing table [ In reply to ]
Hi!

> I can ping 2001:690:810:5::1 in the router configured to be the active
> one (LP=302) but the route isn't placed in the routing table reporting
> "inaccessible" (see show command).

I have no idea if that fits your problem, but

https://bugzilla.quagga.net/show_bug.cgi?id=870

has something similar, and it is unsolved.

--
pi@opsec.eu +49 171 3101372 3 years to go !
_______________________________________________
Quagga-users mailing list
Quagga-users@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users