September 2017 - Bird-users

BIRD IP tunnel problem
by noc＠joey-network.de 12 Sep '17

12 Sep '17

Hi, I figured out a problem with the BIRD routing daemon. It is not possible to route BGP via IPIP tunnels. As you can see below the packets will be routed through the wrong device. Normally it should choose "ASIX" as right device, but it does not. root@cr01:/etc/bird# ip -6 route | grep 2a06:8187:fe48::/48 2a06:8187:fe48::/48 via 2a06:8187:fe01:100::2 dev vlan1000 proto bird src 2a06:8187:fe01::2 metric 1024 pref medium The interface configuration is the following: iface ASIX inet manual pre-up ip -6 tunnel add ASIX mode any local 2a07:59c6:d007::1 remote 2a00:1ca8:2a::730 ttl 255 pre-up ip link set dev ASIX mtu 1476 pre-up ip link set dev ASIX up pre-up ip address add 89.46.125.149/30 dev ASIX pre-up ip address add 2a06:8187:fe01:100::1/56 dev ASIX post-down ip -6 tunnel del ASIX root@cr01:/etc/bird# birdc6 -v 0001 BIRD 1.6.3 ready. bird> Maybe you can help me here? Kind regards. Joey

2 1

Bird redundant routers with same AS on same location and prefix delegation to lower router
by Gelderman, Richard 07 Sep '17

07 Sep '17

I am trying to achieve a redundant routing setup with two routers with the same ASN who do prefix delegation to a lower router. The setup is the following: AS1000 ISP1 ISP2 AS2000 | | | | AS10000 R1 ======== R2 AS10000 prefix /22 \ iBGP / prefix /22 \ / \ / \ / R3 AS65000 / \ / \ net A net B prefix /24 prefix /24 Does anybody has experience with this kind of setup? Regards, Richard

2 1

Monthly Reminders
by Jason Kopacko 01 Sep '17

01 Sep '17

Can we get the password field removed from the monthly emails? I find that highly bad juju emailing out passwords every month. Sent from my Verizon Wireless 4G LTE Droid Turbo 2.

1 0

Error sending route to kernel on FreeBSD (ARM)
by Eugene Sevastyanov 01 Sep '17

01 Sep '17

Hi! I tried to run a bird (v1.6.3) under FreeBSD on ARM architecture. An error occurred: <ERR> KRT: Error sending route XX.XX.XX.XX/XX to kernel: Invalid argument My config: log "/var/log/bird.log" all; router id xx.xx.xx.xx; #debug protocols all; protocol device { scan time 10; } protocol kernel { import none; export all; scan time 15; } protocol bgp ULNIX { local as 65507; neighbor xx.xx.xx.xx as xxx; source address xx.xx.xx.xx; import all; import limit 5000 action restart; } Studying the source code, found out that the problem with aligning the structure (file: /sysdep/bsd/krt-sock.c): struct ks_msg { struct rt_msghdr rtm; struct sockaddr_storage buf[RTAX_MAX]; }; After making changes (see patch in attached), I managed to run the bird. -- Regards Eugene Sevastyanov

2 2

Fix IPv6 ECMP handling with 4.11+ kernel
by Vincent Bernat 01 Sep '17

01 Sep '17

Hey! Starting from kernel 4.11 (commit beb1afac518d), IPv6 are now notified using RTA_MULTIPATH, like IPv4 routes. Those routes are not handled correctly by BIRD. We handle them correctly. This also enable to parse alien routes correctly. Route modifications is still done in the old way as for insertion/deletion, this is not helpful to optimize in those cases and for replace, IPv4 case is not optimized either. It should be possible to detect appropriate support for RTA_MULTIPATH when receiving an IPv6 route with this attribute, but I don't see how it would be helpful, so I didn't do it (simpler code this way). I did some quick tests and routes are removed/added correctly: Deleted 2001:db8:a3::/64 proto bird metric 1024 nexthop via 2001:db8:ff::5 dev vti5 weight 1 nexthop via 2001:db8:ff::7 dev vti6 weight 1 2001:db8:a3::/64 via 2001:db8:ff::7 dev vti6 proto bird metric 1024 pref medium Deleted 2001:db8:a3::/64 via 2001:db8:ff::7 dev vti6 proto bird metric 1024 pref medium 2001:db8:a3::/64 via 2001:db8:ff::5 dev vti5 proto bird metric 1024 pref medium 2001:db8:a3::/64 proto bird metric 1024 nexthop via 2001:db8:ff::7 dev vti6 weight 1 nexthop via 2001:db8:ff::5 dev vti5 weight 1 Also, alien routes are correctly parsed when next-hops are correctly ordered (I didn't check if this restriction is also present for IPv4 or if Linux is always sending IPv4 multipath routes with next-hops correctly ordered): 2001:db8:a4::/64 metric 1024 nexthop via 2001:db8:ff::5 dev vti5 weight 1 nexthop via 2001:db8:ff::7 dev vti6 weight 1 2001:db8:a4::/64 multipath [kernel1 22:30:54] * (10) via 2001:db8:ff::5 on vti5 weight 1 via 2001:db8:ff::7 on vti6 weight 1 I'll try to investigate that unless someone already knows the answer. -- Make input easy to proofread. - The Elements of Programming Style (Kernighan & Plauger)

3 8