- Bird-users - Mailing Lists

How to make BIRD use the kernel routing metric?
by Lukas Liebig 14 Nov '18

14 Nov '18

Hello, I use BIRD 2.0.2 and want the OSPF daemon to announce the Linux kernel routing metric. For instance, if I run "ip route add table 44 to 10.2.3.0/24 metric 1234 dev eth0", I want this route to propagate into BIRD. Therefore I use the kernel protocol configured like this: protocol kernel { ipv4 { export all; import all; }; learn; kernel table 44; scan time 10; } My OSPF instance reads data from table master4. "show ospf state" displays my kernel route as "external", but with "metric2 10000". According to the documentation https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.6 I tried to use metric 0; but without any effect. Do I overlook something essential? Best regards Lukas Liebig

4 5

How to announce OSPF host route for unnumbered interfaces?
by Kenth Eriksson 14 Nov '18

14 Nov '18

Hi! How can I announce one OSPF host route for all my unnumbered interfaces? I don't want to inject it as a static route and export it as such. Thanks, Kenth

2 2

Quick yes / no question about BGP in Bird 1.x.
by Grant Taylor 08 Nov '18

08 Nov '18

Does Bird 1.x support both IPv4 and IPv6 prefixes being advertised over the same BGP neighbor session, which happens to be IPv4 connected? I've not done any research about this specific question yet and I'm just hoping for a "yes it does" or "no it does not" answer. Thank you in advance. Now to go find some coffee and start my day. - I'll do more research this afternoon. -- Grant. . . . unix || die

3 3

[PATCH] Fix Bird/Bird6 wrong LSA collisions detection
by Mikkelsen, Asbjorn 08 Nov '18

08 Nov '18

Bird/Bird6 can wrongly report wrong LSA collisions and stop working. A route fib can in certain cases be released (believing nobody are using them) and still be used (but not dereferenced). A PR can be found here: https://github.com/BIRD/bird/pull/3

2 4

redesigned version of bgp in bird2 changes the rs client behaviour
by Alexander Zubkov 06 Nov '18

06 Nov '18

Hello, I found out that bird version 2 prepends its ASN when exporting to eBGP peer and "rs client" option enabled. I made some investigation and found out that bgp code was hardly redesigned and the logic of "rs client" was changed. Here is v1. https://gitlab.labs.nic.cz/labs/bird/blob/fff79b1c1e0577f487b4fb67f79a74b05… if (!p->is_internal && !p->rs_client) { bgp_path_prepend(e, attrs, pool, p->local_as); And this is in v2 now. https://gitlab.labs.nic.cz/labs/bird/blob/e19d08055a4614f03e51ee72617be1094… if (p->is_internal || (p->rs_client && src && src->rs_client)) { If I get it right, it does not prepend its ASN only in the case when route was received from BGP session too and that session is marked "rs client". So only prefixes from one "rs client" to another is not prepended. It looks like it is impossible now to skip prepend for eBGP for some local routes, for example. I wish it was made an old style way - when "rs client" skips prepend unconditionally.

2 4

change routing while exporting to kernel
by Michael Schwartzkopff 06 Nov '18

06 Nov '18

hi, I want to export a route learned from BGP to the kernel. but I want to modify the route while exporting because I want to use a VTI instead of the next hop route. So instead of 192.168.0.0/24 via 10.0.0.1 I want to export 192.168.0.0/24 dev vti0 to the kernel. Is this possible with bird? If yes, how can I acchieve this? Mit freundlichen Grüßen, -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 12

Re: BIRD 2.0.2 segfaulting
by Ondrej Zajicek 06 Nov '18

06 Nov '18

On Tue, Nov 06, 2018 at 01:56:29PM +0700, Clemens Schrimpe wrote: > > You can use filters: show route table r4 where net.asn = 4711 > > But > > show route table r4 where net = 1.1.1.0/24 > or even > show route table r4 for 1.1.1.1 > > doesn’t work. It that by design or just an oversight? Confusingly, 'net' represents whole route key, not just prefix. For IP route it is just prefix, while for ROA it is prefix, maxlen and asn. Its parts can be accessed using kewords ip, len, maxlen and asn. Therefore, this should work: show route table r4 where net.ip = 1.1.1.0 But note that like all 'show route where' variants, it has ti iterate through whole routing table. (Unlike show route NET. which does direct lookup). -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago(a)crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."

1 0

BIRD 2.0.2 segfaulting
by Clemens Schrimpe 06 Nov '18

06 Nov '18

Hello - just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI. In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died. Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“? I would have assumed „show route table r4 all 186.255.72.0/24“ or something like that would work, but it doesn’t (gives empty output). At least „show route table r4 count“ gives useful information, though. Thanks, Clemens

3 6

(Re)export unreachable routes via BGP.
by Grant Taylor 05 Nov '18

05 Nov '18

Is it possible to (re)export unreachable routes via BGP? I have established a pair of BGP neighbor sessions with Team Cymru Route Servers, both of which are receiving unreachable prefixes, namely bogons, like they should be. I would like to (re)export said prefixes to a different machine that is not able to form a BGP neighbor session with Team Cymru (for various reasons). All attempts thus far have resulted in the BGP neighbor session with the 3rd test machine not (re)exporting any unreachable routes. I can (re)export other routes without a problem. It looks to me like BGP is rejecting the the routes (I think) because they are unreachable. "show route table bogons" works as expected, and shows the routes received via both of the BGP neighbor sessions with the Team Cymru Route Servers. Similarly, I can see the unreachable routes in the proper table from Linux. Thank you in advance for any help / enlightenment that you can provide. --8<-- bird> show protocols all grant name proto table state since info grant BGP bogons up 21:12 Established Description: Feed to Grant at home Preference: 100 Input filter: REJECT Output filter: ACCEPT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 3031 3031 0 --- 0 Export withdraws: 0 --- --- --- 0 -->8-- --8<-- filter cymru_bogons_import { bgp_community.add((REDACTED,888)); #dest = RTD_BLACKHOLE; accept; } filter cymru_bogons_export { reject; } protocol bgp cymru1 { description "Team Cymru Bogons Route Server #1"; import filter cymru_bogons_import; #export filter cymru_bogons_export; #import all; export none; multihop 255; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } protocol bgp cymru2 { description "Team Cymru Bogons Route Server #2"; import filter cymru_bogons_import; #export filter cymru_bogons_export; #import all; export none; multihop 255; #password "FIXME"; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } protocol bgp grant { description "Feed to Grant at home"; import none; export all; multihop 255; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } -->8-- -- Grant. . . . unix || die

2 3

vrf configuration with same addresses
by Semion Lisyansky 05 Nov '18

05 Nov '18

Hi All, Tried to configure vrf with same own and peer addresses as in global. When I ping in vrf, packets go in and out via correct interfaces, but bird bgp sessions are constantly flapping. Only one session to peer with same address exists at each moment As a w/a tried to configure interface per session, but this did not helped. Here is my partial configuration: protocol device { scan time 2; # Scan interfaces every 2 seconds } protocol direct { interface "br*"; # bridge interfaces interface "swp*"; # router ports interface "bond*"; # Disable by default ipv4; # Connect to default IPv4 table ipv6; # ... and to default IPv6 table } protocol kernel { ipv4 { # Connect protocol to IPv4 table by channel table master4; # Default IPv4 table is master4 import none; # Import to table, default is import all export all; # Export to protocol. default is export none }; learn on; # Learn alien routes from the kernel merge paths yes; } protocol bgp bgp3411 { local as 65001; bfd yes; neighbor 191.34.1.3 as 65034; # interface "swp2"; ipv4 { import all; export all; }; } protocol bgp bgp3412 { local as 65001; bfd yes; neighbor 192.34.1.3 as 65034; # interface "swp1"; ipv4 { import all; export all; }; } ipv4 table table_vrf01; protocol kernel kernel_vrf01 { vrf "vrf01"; kernel table 101; scan time 2; ipv4 { table table_vrf01; import none; # Default is import all export all; # Default is export none }; merge paths yes; learn on; # Learn all alien routes from the kernel } protocol direct direct_vrf01 { vrf "vrf01"; ipv4 { table table_vrf01; }; interface "swp7.101"; interface "swp1.201"; interface "swp2.301"; interface "vrf01"; } protocol static static_vrf01 { vrf "vrf01"; ipv4 { table table_vrf01; }; } protocol bgp bgp_vrf01_n1 { vrf "vrf01"; local as 65001; graceful restart; neighbor 191.34.1.3 as 65034; ipv4 { table table_vrf01; import none; export none; }; } protocol bgp bgp_vrf01_n2 { vrf "vrf01"; local as 65001; graceful restart; neighbor 192.34.1.3 as 65034; ipv4 { table table_vrf01; import none; export none; }; } ip -br link show type vrf vrf01 UP fe:58:94:d2:d8:ee <NOARP,MASTER,UP,LOWER_UP> vrf02 UP 42:2d:8f:bd:87:9f <NOARP,MASTER,UP,LOWER_UP> (mlnx)root@bdg-crf-01:~# ip route show vrf vrf01 172.1.7.0/24 dev swp7.101 proto kernel scope link src 172.1.7.1 offload 191.34.1.2/31 dev swp2.301 proto kernel scope link src 191.34.1.2 offload 192.34.1.2/31 dev swp1.201 proto kernel scope link src 192.34.1.2 offload (mlnx)root@bdg-crf-01:~# ip route show table 101 broadcast 172.1.7.0 dev swp7.101 proto kernel scope link src 172.1.7.1 172.1.7.0/24 dev swp7.101 proto kernel scope link src 172.1.7.1 offload local 172.1.7.1 dev swp7.101 proto kernel scope host src 172.1.7.1 broadcast 172.1.7.255 dev swp7.101 proto kernel scope link src 172.1.7.1 local 191.34.1.2 dev swp2.301 proto kernel scope host src 191.34.1.2 191.34.1.2/31 dev swp2.301 proto kernel scope link src 191.34.1.2 offload local 192.34.1.2 dev swp1.201 proto kernel scope host src 192.34.1.2 192.34.1.2/31 dev swp1.201 proto kernel scope link src 192.34.1.2 offload -- Semion Lisyansky

3 11