[ixpmanager] IPv4 & IPv6 peering but no routes being learned by IPv6
Barry O'Donovan
barry.odonovan at inex.ie
Mon Feb 12 19:36:49 GMT 2018
Diarmuid O Briain wrote:
> I did a bit of debugging and the problem appears to be related to the
> import filter.
>
> I stopped the automatic updating of the bird conf files from IXP Manager
> and edited the last one where I hashed out the "import filter" lines in
> the protocol configurations. I bounced the bird6 process and hey presto
> the routes came in. So what is it about the filter that is causing this
> problem ?
So filtering doesn't happen until routes are piped to the master table.
If you look at routes received by a protocol you'd probably see your
per-client missing routes. E.g.
show route protocol pb_00xx_asyyyy
>From the below, it looks like you're advertising /64's and we recently
updated the router templates to (more correctly) filter anything >/48
for IPv6 (IPv4 already had a filter for >/24).
This isn't officially released yet but it is configurable by adding the
following to .env (show here with default values):
IXP_IRRDB_MIN_V4_SUBNET_SIZE=24
IXP_IRRDB_MIN_V6_SUBNET_SIZE=48
The line that controls this in the filter is (near the top of the config
file):
prefix set martians;
{
martians = [
...
::/0{49,128} # Filter small prefixes
];
- Barry
> ubuntu at rs1:/etc/bird$ *cat bird-rs1-lan1-ipv6.conf | grep '#
> import filter'*
> # import filter f_import_0001_as5111;
> # import filter f_import_0002_as5222;
> # import filter f_import_0003_as5333;
>
> ubuntu at rs1:/run/bird$ *sudo birdc6 -s bird-rs1-lan1-ipv6.ctl *
> BIRD 1.6.3 ready.
> bird> show route
> 2a99:3:3::/64 via 2a99:9:9::33 on ens4 [pb_0003_as5333 17:36:52] *
> (100) [AS5333i]
> 2a99:2:2::/64 via 2a99:9:9::22 on ens4 [pb_0002_as5222 17:36:53] *
> (100) [AS5222i]
> 2a99:1:1::/64 via 2a99:9:9::11 on ens4 [pb_0001_as5111 17:36:52] *
> (100) [AS5111i]
> bird> exit
>
> regards,
>
> Diarmuid
>
> --
>
> */Irish by birth, located in Uganda but Munster by the grace of God./*
>
>
>
> On 12 February 2018 at 19:56, Diarmuid O Briain <diarmuid at obriain.com
> <mailto:diarmuid at obriain.com>> wrote:
>
> Hi,
>
> I tested the configuration with a simple bird and bird6 setup first
> to ensure it was working.
>
> ubuntu at rs1:~$* cat /etc/bird/bird6.conf*
> log syslog all;
>
> router id 199.9.9.1;
> define LOCAL_AS = 5999;
>
> template bgp PEERS {
> rs client;
> local as LOCAL_AS;
> import all;
> export all;
> }
>
> protocol device {
> scan time 10;
> }
>
> protocol kernel {
> export all;
> scan time 15;
> }
>
> protocol bgp AS5111 from PEERS {
> neighbor 2a99:9:9::11 as 5111;
> }
>
> protocol bgp AS5222 from PEERS {
> neighbor 2a99:9:9::22 as 5222;
> }
>
> protocol bgp AS5222 from PEERS {
> neighbor 2a99:9:9::33 as 5333;
> }
>
> pretty much the same for the bird.conf file except for the neighbour
> addresses.
>
> After setting up the IXP Manager scripts on the rs1 the
> bird-rs1-lan1-ipv{4|6}.ctl and the bird-rs1-lan1-ipv{4|6}.conf files
> are now generated by IXP Manager.
>
> BGP peers are establishing for both birdc and birdc6 daemons but
> under the birdc6 no routes are being learnt. They were fine with the
> simple configuration above.
>
> ubuntu at rs1:~$ sudo birdc
> BIRD 1.6.3 ready.
> bird> *show protocol*
> name proto table state since info
> device1 Device master up 15:24:54
> pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111
> pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established
> pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222
> pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established
> pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333
> pb_0003_as5333 BGP t_0003_as5333 up 15:24:58 Established
>
> bird> *show route*
> 199.1.1.0/24 <http://199.1.1.0/24> via 199.9.9.11 on ens4
> [pb_0001_as5111 15:24:58] * (100) [AS5111i]
> 199.3.3.0/24 <http://199.3.3.0/24> via 199.9.9.33 on ens4
> [pb_0003_as5333 15:24:58] * (100) [AS5333i]
> 199.2.2.0/24 <http://199.2.2.0/24> via 199.9.9.22 on ens4
> [pb_0002_as5222 15:24:58] * (100) [AS5222i]
> bird> exit
>
> ubuntu at rs1:~$* sudo birdc6*
> BIRD 1.6.3 ready.
> bird> show protocol
> name proto table state since info
> device1 Device master up 15:24:54
> pp_0001_as5111 Pipe master up 15:24:54 => t_0001_as5111
> pb_0001_as5111 BGP t_0001_as5111 up 15:24:58 Established
> pp_0002_as5222 Pipe master up 15:24:54 => t_0002_as5222
> pb_0002_as5222 BGP t_0002_as5222 up 15:24:58 Established
> pp_0003_as5333 Pipe master up 15:24:54 => t_0003_as5333
> pb_0003_as5333 BGP t_0003_as5333 up 15:24:55 Established
>
> bird> *show route*
> bird>
>
> regards,
>
> Diarmuid
> --
>
> */Irish by birth, located in Uganda but Munster by the grace of God./*
>
>
>
> _______________________________________________
> INEX IXP Manager mailing list
> ixpmanager at inex.ie
> https://www.inex.ie/mailman/listinfo/ixpmanager
--
Kind regards,
Barry O'Donovan
INEX Operations
https://www.inex.ie/support/
+353 1 531 3339
More information about the ixpmanager
mailing list