- Bird-users - Mailing Lists

bird (2.0.4) does not install multipath route in kernel
by Arno O 11 Jun '19

11 Jun '19

This topic was already discussed around March 1st 2019, without having received a clear outcome. Now, dealing with ECMP with OSPF in Bird 2.04 on Fedora30, I run in same problems: -> multiple next hops to same destination (50.50.50.0/24) are in the route table of bird: bird> sho route Table master4: 10.10.10.0/24 unicast [OIPv46 13:39:16.979] I (150/10) [10.10.10.1] dev enp0s3 192.168.122.0/24 unicast [OIPv46 13:46:18.979] E2 (150/10/10000) [10.10.10.3] via 10.10.10.3 on enp0s3 50.50.50.0/24 unicast [OIPv46 13:46:18.979] E2 (150/10/100) [10.10.10.3] via 10.10.10.2 on enp0s3 weight 11 via 10.10.10.3 on enp0s3 weight 11 bird> [root@localhost ~]# but kernel route table looks unexpectedly different: root@localhost ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.10.10.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s3 50.50.50.0 10.10.10.2 255.255.255.0 UG 0 0 0 enp0s3 192.168.122.0 10.10.10.3 255.255.255.0 UG 0 0 0 enp0s3 [root@localhost ~]# Kernel looks configured correctly (*CONFIG_IP_ROUTE_MULTIPATH=y), etc.etc.* *Bird config on ECMPed bird router: *protocol ospf OIPv46 { tick 2; rfc1583compat yes; ecmp yes limit 8; merge external yes; ipv4 { import all; export all; }; area 0 { interface "enp0*" { # type broadcast; # Detected by default cost 10; # Interface metric ecmp weight 11; What is missing either in the bird-config or the kernel part? Thx BR Ar

3 3

radv/OpenWRT: "propagate routes yes" syntax error
by Marvin Gaube 11 Jun '19

11 Jun '19

Hello, I'm currently trying to run bird6 on a Gluon-Device (Gluon is build upon OpenWRT) to announce Router Advertisments. I need to announce more specific routes, which I'm trying to export like this: table radv_routes; # Add routes protocol static { table radv_routes; route fd21:b4dc::/40 via fe80::1; } protocol radv { table radv_routes; propagate routes yes; export all; interface "local-gw" { max ra interval 5; default preference high; default lifetime 1600; }; prefix 2a0e:...::/64 { }; } The configuration is inspired by the example from https://bird.network.cz/?get_doc&v=16&f=bird-6.html#ss6.10 Every time I'm trying to start bird with "propagate routes yes" it says that there's a syntax error in this line. Without - announcing only the default route - everything works fine. The exact version is 1.6.3 on OpenWRT 18.02. Has anyone an idea on how to solve this? I didn't found this as "known bug" yet. Thanks and best regards Marvin

2 1

[PATCH] Fix an issue where bird may accidently close a socket
by Kenth Eriksson 11 Jun '19

11 Jun '19

Datagram sockets may return 0 and stream sockets can return 0 if the requested number of bytes to read is 0. Signed-off-by: Kenth Eriksson <kenth.eriksson(a)infinera.com> --- sysdep/unix/io.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sysdep/unix/io.c b/sysdep/unix/io.c index d1d86e3b..44dd3172 100644 --- a/sysdep/unix/io.c +++ b/sysdep/unix/io.c @@ -1873,7 +1873,7 @@ sk_read(sock *s, int revents) s->err_hook(s, 0); } } - else if (!c) + else if (!c && (revents & POLLHUP)) s->err_hook(s, 0); else { -- 2.21.0

3 7

adding MED to + bgp_med
by Łukasz Trąbiński 06 Jun '19

06 Jun '19

Hello In my configuration I export policy function like this: if (yyyyy,xxxxx) ~ bgp_community && (defined (bgp_med)) then { bgp_med = bgp_med + 100; accept; } It worked well in 1.6.4 if the prefix was set community yyyyy,xxxxx and med was set to for example = 20, med was set to 120 in export bgp session. In version 1.6.6 it looks like it does not work, med is set = 100. Something was changed beetwen versions? Maybe it’s a bug? Łukasz Trąbiński

2 2

2 upstreams 1 downstream BGP configuration optimization
by Kevin B 05 Jun '19

05 Jun '19

Hello, I have 2 upstream transit providers and 1 downstream customer we provide transit to - http://paste.debian.net/1086030/ (full Bird configuration with explanation) There is a problem: Bird is exporting all the imported prefixes from my upstreams back to them. For example 10.40.40.0/24 is being exported from us even when AS20's customer doesn't announce it, because it is announced somewhere else in the full table and we just export it back from the full view. Here is `birdc show protocols all` output - http://paste.debian.net/1086033/ I would like to prevent exporting the full view tables imported from my upstreams back to them, can you help me to understand what is wrong with the configuration and why does it happen?

4 4

Re: Submitting code? (Wireguard)
by Janne Heß 02 Jun '19

02 Jun '19

Hey everyone, I wrote code that adds Wireguard support (new kernelspace VPN) to Bird 2. The problem is that with the cryptokey routing of Wireguard, it needs to know which IPs are behind which peers. The patch does exactly that: If the interface is a wireguard interface, try modifying the list of IPs. So my question is: How do I contribute that? I think the feature would be useful for other people, so having it upstream would be nice. Should I just post the patch here? Or create a GitLab PR? PR would probably be more convenient due to the discussion feature, but I'm unable to fork the project because my project limit is at 0. Could you give me information on how to contribute the code? Thanks and regards Janne

3 2

Forward full view to a downstream
by Kevin B 30 May '19

30 May '19

Hello, My customer wants me to announce a full IPv4 table via BGP to him, but we don't use it on the BGP node where that customer is peered. We receive the default from our BGP upstream, but can actually ask for and receive a full view as well, but only for a purpose of forwarding it to the customer. What would be a scheme to receive a full-table from a BGP upstream and forward it to a BGP downstream, without importing it to our own routing table? I am not very experienced with Bird, but some guys on Freenode ##networking have suggested using a pipe, can someone help me on this please?

4 3

Help with SNMP for BIRD
by Glenn Peace 28 May '19

28 May '19

Good afternoon everyone, I hope this message finds you well. We would like to monitor the BGP session stablished by our BIRD Route server with monitoring tools like Nagios or LibreNMS. I’ve found a couple email threads indicating this was not directly available a couple years ago. On the other hand, some web sites suggest tools for this purpose, but I’m u sure if they are reliable. Is this now available with BIRD? Or, can you suggest a tool for this? Best, N I C . C R Glenn Peace Sr. Network Engineer gtpeace(a)nic.cr

4 5

Received route with strange next-hop
by Adrichem, N.L.M. (Niels) van 28 May '19

28 May '19

Hello, I'm trying to redistribute routes from another routing daemon through synchronization of the kernel table using the kernel protocol in BIRD 2.0.4. However, I run into some problems that not all routes are imported by the BIRD router. The kernel routing table contains the following routing table: # ip route 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.1 10.0.1.3 via 10.0.1.4 dev eth1 proto zebra metric 2 10.0.1.4 dev eth1 proto zebra scope link metric 1 10.0.4.0/24 via 10.0.0.2 dev eth0 proto bird metric 32 The interface eth1 has the address 10.0.1.1/32 in an ad-hoc routing domain, through OSPF-MDR (which is an extension of Quagga) it finds the direct neighbor 10.0.1.4 which is added as "10.0.1.4 dev eth1 proto zebra scope link metric 1". The neighbor 10.0.1.4 advertises that it can forward to 10.0.1.3 which is added as "10.0.1.3 via 10.0.1.4 dev eth1 proto zebra metric 2". The routing of OSPF-MDR works, in the sense that 10.0.1.1 can reach 10.0.1.3 and 10.0.1.4. However, when we try to import these routes from the protocol kernel into the Bird routing table, only the directly connected route to 10.0.1.4 shows while the route to 10.0.1.3 are not imported: # birdc show route BIRD 2.0.4 ready. Table master4: 10.0.1.4/32 unicast [kernel1 10:27:29.329] (10) dev eth1 10.0.4.0/24 unicast [babel1 10:27:23.461 from fe80::200:ff:feaa:4] (130/96) [00:00:00:00:0a:00:00:02] via 10.0.0.2 on eth0 10.0.0.0/24 unicast [direct1 10:27:21.870] * (240) dev eth0 unicast [babel1 10:27:23.461 from fe80::200:ff:feaa:4] (130/96) [00:00:00:00:0a:00:00:02] via 10.0.0.2 on eth0 Additionally, the bird.log file throws the following error: 2019-05-15 10:27:21.869 <INFO> Started 2019-05-15 10:27:21.902 <WARN> Missing broadcast address for interface vxlan0 2019-05-15 10:27:29.329 <ERR> KRT: Received route 10.0.1.3/32 with strange next-hop 10.0.1.4 It may be that kernel protocol rejects the route because the next-hop is not in the interface its regular netmask (which is set to /32), though I am not familiar enough with the source code to determine the exact cause except that the error gets thrown from sysdep/linux/netlink.c line 1643. However, I think the line should be accepted since there is another routing rule confirming that the next-hop is directly attached to device eth1. Given the explicit error I don't think this is a configuration error (though I am open to learn more), so I hope BIRD can be patched to solve this. I have attached the bird.conf file, as well as an image of the example topology. Above snippets and config file are taken from node n1 which is running both the OSPF-MDR router based on Quagga and BIRD Router. Any help would be much appreciated. Thanks in advance, Niels van Adrichem [cid:image001.png@01D50B0D.4706B540] This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.

2 2

Hardware Server requirements for building up BIRD
by Isaac HO 28 May '19

28 May '19

Dear All, Would you mind suggesting the hardware configuration to us? Please find our BGP sessions status for your reference: IPv4 Session 600 (around) IPv6 Session 400 (around) Thanks, Isaac

3 3