August 2019 - Bird-users

ospf authentication status from bird cli?
by Kenth Eriksson 12 Sep '19

12 Sep '19

Is it possible to see ospf authentication status from bird cli? I have seen that authentication failures are logged to file, but it would be good to have it visible in cli as well. Thanks, Kenth

3 5

Multisite BGP - One site behind OpenVPN
by Michael McConnell 01 Sep '19

01 Sep '19

Hello all, I’ve been debating with myself the best way to handle this situation. I have a two site deployment with a /23 prefix available. I wish to assign 1 /24 to site one (Main), and 1 /24 to site two (Satellite) and then link them via OpenVPN. I am debating the pro’s and con’s of running bird at both sites with BGP or just doing a static route at site two behind the VPN. BGP at Both Sites; - Announce the /23 to the Internet at Main Site - Announce one /24 and use locally at Main site - Run a BGP session between Main and Satellite and announce the 2nd /24 at site two I feel the main advantage here is that I can scale if more connectivity ever comes to the Satellite site. BGP at single site with static route over VPN - Announce the /23 to the Internet at Main Site - Use VPN as default gateway for all satellite users I feel like I must be missing something in both of these designs, can anyone see any issue with either of these setups and possibly suggest why one might be better over the other? Thanks for your thoughts and time! Mike

2 3

Segfault in bird 2.0.5 when issuing "show ospf lsadb" from birdc
by aldem-bird.201704＠nk7.net 29 Aug '19

29 Aug '19

Hi, Attempt to show ospf's lsadb using birdc produces segfault, with or without ospf routes: 2019-08-29 20:04:39.203 <TRACE> device1: Initializing 2019-08-29 20:04:39.203 <TRACE> ospf1: Channel ipv4 connected to table master4 2019-08-29 20:04:39.203 <TRACE> ospf1: Initializing 2019-08-29 20:04:39.203 <TRACE> device1: Starting 2019-08-29 20:04:39.203 <TRACE> device1: State changed to up 2019-08-29 20:04:39.203 <INFO> Chosen router ID 192.168.255.4 according to interface failover 2019-08-29 20:04:39.203 <TRACE> ospf1: Starting 2019-08-29 20:04:39.203 <TRACE> ospf1: State changed to up 2019-08-29 20:04:39.203 <INFO> Started # birdc BIRD 2.0.5 ready. bird> show ospf lsadb Connection closed by server Program received signal SIGSEGV, Segmentation fault. 0x000055555558b3d8 in ospf_sh_lsadb (ld=0x5555558c2ea0) at ../proto/ospf/ospf.c:1455 1455 uint num = p->gr->hash_entries; (gdb) list 1450 1451 void 1452 ospf_sh_lsadb(struct lsadb_show_data *ld) 1453 { 1454 struct ospf_proto *p = ld->proto; 1455 uint num = p->gr->hash_entries; 1456 uint i, j; 1457 int last_dscope = -1; 1458 u32 last_domain = 0; 1459 u16 type_mask = ospf_is_v2(p) ? 0x00ff : 0xffff; /* see lsa_etype() */ (gdb) p p $1 = (struct ospf_proto *) 0x0 In bird 2.0.4 everything is ok. Seems that 2.0.5 has too many issues... Best regards, Alexander.

2 1

BGP reported established and last change time
by Van Dyk, Donovan 28 Aug '19

28 Aug '19

Hi, Has anyone eve ran into the issue of the date reporting for an established BGP peer being reset to 00:00:00 when it rolls over to a new day using peer status? It appears that when the session rolls into the next day, the established time gets set to only a date and it drops the HH:MM:SS /route-mon/peer_status | grep last_change "last_change": "2019-08-27T00:00:00", "last_change": "2019-08-27T00:00:00", "last_change": "2019-08-20T00:00:00", "last_change": "2019-08-20T00:00:00", "last_change": "2019-08-27T00:00:00", "last_change": "2019-08-27T00:00:00", Also, the time being reported for the route duration is just a date. tbird.ctl show route BIRD 1.6.3 ready. 172.16.1.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.2.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.3.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.4.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.5.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.6.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.7.0/24 dev bbforward [static_bgp 2019-08-20] * (200) 172.16.8.0/24 dev bbforward [static_bgp 2019-08-20] * (200) It would be nice if I could get more granularity out of the commands. Any ideas? Thanks -- Platform Operations Engineer Fort Lauderdale, FL USA [id:9A68E9F7-1C69-4FEA-A38A-3B3754E954E2] The information contained in this electronic mail transmission and its attachments may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient (or an individual responsible for delivery of the message to such person), you are strictly prohibited from copying, disseminating or distributing this communication. If you have received this communication in error, please notify the sender immediately and destroy all electronic, paper or other versions.

2 1

A bug in patch from FreeBSD ports
by Ondrej Zajicek 28 Aug '19

28 Aug '19

Hello There is a patch for BIRD in FreeBSD ports that causes OSPF crash: https://svnweb.freebsd.org/ports?view=revision&revision=484648 22 + if (en->lsa_body && (en->lsa.age == LSA_MAXAGE)) 23 + { 24 + /* en could be an unexpected self-originated lsa in which case nf is NULL */ 25 + log(L_INFO "%s: Found flushing LSA while originating %I/%d with fib: %p", 26 + p->p.name, lsa->nf->fn.prefix, lsa->nf->fn.pxlen, en->nf); 27 + en->nf = lsa->nf; 28 + } 29 lsa->nf here may be NULL. I would suggest to send BIRD patches for review to the BIRD mailing list so we can review it and also merge it upstream. -- 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."

2 2

Reconfiguring problem while having a lot of static routes
by Vasily Oleynikov 26 Aug '19

26 Aug '19

Hello I have a bird 1.6.3 installation where is over 500k static routes. From some moment service reconfiguring occupies significant time (over 20 minutes). Is there some method to reduce time needed to reconfigure? My config is below log syslog all; router id X.X.X.X; filter BGW_WAN_import { if net ~ [0.0.0.0/0] then accept; reject; } filter BGW_LAN_import { reject; } filter BGW_LAN_export { if dest = RTD_UNREACHABLE then reject; accept; } filter DROP_STATIC { if dest = RTD_BLACKHOLE then { bgp_community.add((65535, 65282)); bgp_community.add((X, 666)); accept; } if source = RTS_STATIC then reject; if source = RTS_BGP then accept; reject; } protocol bgp BGW1_WAN { local as 65511; neighbor Y.Y.Y.X as X; import filter BGW_WAN_import; export filter DROP_STATIC; } protocol bgp BGW0_WAN { local as 65511; neighbor Y.Y.Y.Z as X; import filter BGW_WAN_import; export filter DROP_STATIC; } protocol device { scan time 10; } protocol kernel { scan time 10; export filter DROP_STATIC; } protocol static { include "/opt/etc/bird/static_null.conf"; } in /opt/etc/bird/static_null.conf there is routes like this: route 13.59.179.106/32 drop; WBR, Vasily

2 1

Bird 2 OSPF Authentication Type unknown (256) issue
by James Swineson 24 Aug '19

24 Aug '19

Hi, I have a Linux server and a Cisco IOS XE device connected with GRE/IPSec and then can ping each other. Today I installed Bird 2.0.5 on the Linux server and enabled OSPFv2 on both of them. Although they receive HELLO packets from each other, they refuse to establish a connection. A packet capture shows Bird is sending packets with auth type = 256 which is not something I would expect everyday: 05:38:06.129722 IP (tos 0xc0, ttl 1, id 48901, offset 0, flags [none], proto OSPF (89), length 64) 192.168.1.2 > ospf-all.mcast.net: OSPFv2, Hello, length 44 Router-ID 192.168.1.2, Backbone Area, Authentication Type: unknown (256) As a test I changed authentication type from none to simple; this time Bird gave me 257: 05:40:36.129411 IP (tos 0xc0, ttl 1, id 3669, offset 0, flags [none], proto OSPF (89), length 64) 192.168.1.2 > ospf-all.mcast.net: OSPFv2, Hello, length 44 Router-ID 192.168.1.2, Backbone Area, Authentication Type: unknown (257) Is there something wrong with my config or there is a bug in Bird2? Is there any workaround I can use right now? I've already checked on both sides their interface type is set to ptp and all timers match. My environment: * Cisco IOS XE 16.9.3, CSR1000v in Hyper-V VM * Debian 10 in KVM, Bird 2.0.5 via official unstable repo, IPSec done with strongswan Thanks ahead, James Swineson

2 2

Re: IPv6 routes inserted into the kernel with 'route' end up with invalid type
by Toke Høiland-Jørgensen 23 Aug '19

23 Aug '19

David Ahern <dsahern(a)gmail.com> writes: > On 8/23/19 8:43 AM, Toke Høiland-Jørgensen wrote: >> Hi David >> >> Tom noticed[0] that on newer kernels, the Bird routing daemon rejects IPv6 >> routes received from the kernel if those routes were inserted with the >> old 'route' utility (i.e., when they're inserted through the ioctl >> interface). >> >> We tracked it down to the routes having an rtm_type of RTN_UNKNOWN, and >> a bit of git archaeology points suggestively at this commit: >> >> e8478e80e5a ("net/ipv6: Save route type in rt6_info") >> >> The same setup works with older kernels, so this seems like it's a >> regression, the age of 'route' notwithstanding. Any good ideas for the >> proper way to fix this? >> > > Should be fixed by: > > commit c7036d97acd2527cef145b5ef9ad1a37ed21bbe6 > Author: David Ahern <dsahern(a)gmail.com> > Date: Wed Jun 19 10:50:24 2019 -0700 > > ipv6: Default fib6_type to RTN_UNICAST when not set > > A user reported that routes are getting installed with type 0 > (RTN_UNSPEC) > where before the routes were RTN_UNICAST. One example is from accel-ppp > which apparently still uses the ioctl interface and does not set > rtmsg_type. Another is the netlink interface where ipv6 does not require > rtm_type to be set (v4 does). Prior to the commit in the Fixes tag the > ipv6 stack converted type 0 to RTN_UNICAST, so restore that behavior. > > Fixes: e8478e80e5a7 ("net/ipv6: Save route type in rt6_info") > Signed-off-by: David Ahern <dsahern(a)gmail.com> > Signed-off-by: David S. Miller <davem(a)davemloft.net> Ah, great! Guess that hasn't made its way to the stable and distribution kernels yet. Thanks for the pointer! :) -Toke

1 0

bird 1.6 seems to ignore ipv6 kernel routes on 4.19
by Tom Bird 23 Aug '19

23 Aug '19

Hi, I recently updated some virtual machine hosting nodes to Debian Buster from Stretch, and I'm having an interesting problem with IPv6 kernel routes. My example uses 1.6.6 but 1.6.7 shows the same behaviour, so I'm just wondering what I am missing. v4 is all working as expected. I tried a bird6.conf from a machine still running Debian Stretch, and that also did not import the kernel routes. I've tried this on a test VM with bird 1.6.3 and kernel 4.9.0 and it imports the routes as expected. I've set up a test VM in the lab with the following bird6.conf: -------------------------------------- root@os-test:~# grep -v ^# /etc/bird/bird6.conf router id 198.51.100.1; protocol kernel { scan time 60; learn; device routes; #import none; import all; } protocol device { scan time 60; } -------------------------------------- This is just the sample file with "learn", "import all" and "device routes" added to the kernel protocol. I have added a test kernel route: root@os-test:~# route -6 add 2a03:9804::/64 gw 2a03:9802:1000:aa::1 I would expect to see this in a "show route" output from birdc6, but I don't. I only see the default: root@os-test:~# birdc6 BIRD 1.6.6 ready. bird> show route ::/0 via 2a03:9802:1000:aa::1 on ens2 [kernel1 21:14:40] * (10) bird> If I add a protocol direct section, then I get device routes but still not indirect kernel routes. Some other stuff about the system, sorry if this hasn't pasted so well. root@os-test:~# uname -a Linux os-test.portfast.net 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux root@os-test:~# netstat -rn6 Kernel IPv6 routing table Destination Next Hop Flag Met Ref Use If ::1/128 :: U 256 2 0 lo 2a03:9802:1000:aa::/64 :: U 256 3 0 ens2 2a03:9804::/64 2a03:9802:1000:aa::1 UG 1 1 0 ens2 fe80::/64 :: U 256 1 0 ens2 ::/0 2a03:9802:1000:aa::1 UGH 1024 2 0 ens2 ::1/128 :: Un 0 4 0 lo 2a03:9802:1000:aa::2/128 :: Un 0 3 0 ens2 fe80::5054:ff:fe10:d040/128 :: Un 0 3 0 ens2 ff00::/8 :: U 256 2 0 ens2 ::/0 :: !n -1 1 0 lo Thanks, -- Tom Bird http://www.portfast.co.uk/ : AS8916 UK Limited company #6061075 : +44 1777 29 28 27

4 6

IPsec (OSPFv3)
by Kenth Eriksson 19 Aug '19

19 Aug '19

Hi! What is the plan for IPsec with regards to OSPFv3? Is it part of roadmap? If not a roadmap item, what is the recommended way to get IPsec support for OSPFv3 with bird? libreswan? Thanks, Kenth

3 4