- Bird-users - Mailing Lists

Re: BIRD routing daemon - exact session uptime
by Martin Mares 16 Jun '11

16 Jun '11

Hello! > I'd like to ask you a quick question. > I'm working on a BIRD looking glass script and what I need is an > exact uptime of BGP session. "sh protocols all" doesn't seem to be > particularly useful as it isn't accurate enough (e.g. session is up > since 18May) > Is there a simple way to get more accurate uptime of BGP session? I do not work on BIRD too much these days, but others do. So I am forwarding your query to the BIRD mailing list. Have a nice fortnight -- Martin `MJ' Mares <mj(a)ucw.cz> http://mj.ucw.cz/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth

3 2

keepalive timer problem
by Arnold Nipper 16 Jun '11

16 Jun '11

Hi, we run BIRD 1.2.5 and have an issue with one customer all the time where we see constantly a negative keepalive timer Ryyy_xxx BGP TableXYZ up 2011-06-16 11:32:42 Established Keepalive timer: -41901542/60 Any hints to debug this further? All other 360 sessions are doing fine. Best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arnold(a)nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333

2 2

BIRD exporting to kernel although disabled
by Bernhard Hahn 16 Jun '11

16 Jun '11

Dear Bird Mailinglist, We are running Bird 1.2.5 under Debian Etch AMD64 as a routeserver. Last Friday we changed a filter to allow the import of prefixes from a peer with the same AS as the routeserver. The broken design of the configuration, allowed the import of prefixes with empty AS-path to the master table and their export to the EBGP peers. Unfortunately this caused nearly all Cisco (&RFC compliant) machines to close their sessions. At this time, one of our two routeservers started exporting the Master table to the kernel table. There is currently no impact, but we are wondering how this could happen and how to resolve this situation, without affecting the running sessions. The kernel part of the configuration never changed and looks like: protocol kernel { disabled; import all; # Default is import all export all; # Default is export none scan time 10; # Scan kernel tables every 10 seconds } When we remove one of the kernel prefixes like: route del -net X.Y.Z.A netmask 255.255.255.0 gw X.X.X.X eth1 It reappears after around 10 seconds. Guess the scan time is taking effect here. "configure soft" was already triggered several times without effect to the kernel protocol. Regards Bernhard -- Bernhard Hahn DE-CIX Management GmbH e-mail: bernhard.hahn(a)de-cix.net Lindleystr. 12, 60314 Frankfurt Phone: +49 69 1730 902-34 Geschaeftsfuehrer Harald A. Summa Mobile: +49 171 552 3643 Registergericht AG Koeln, HRB 51135 Fax: +49 69 4056 2716

4 12

lists
by Robert Harris 15 Jun '11

15 Jun '11

1 0

IPv6 address classification
by lex 10 Jun '11

10 Jun '11

bird6 has a rather limited list of IPv6 address classifications, unfortunately limiting the routes that it will accept. ipv6_classify(ip_addr *a) in lib/ipv6.c: if ((x & 0xe0000000) == 0x20000000) /* 2000::/3 Aggregatable Global Unicast Address */ if ((x & 0xffc00000) == 0xfe800000) /* fe80::/10 Link-Local Address */ if ((x & 0xffc00000) == 0xfec00000) /* fec0::/10 Site-Local Address */ if ((x & 0xfe000000) == 0xfc000000) /* fc00::/7 Unique Local Unicast Address (RFC 4193) */ if ((x & 0xff000000) == 0xff000000) /* ff00::/8 Multicast Address */ Unfortunately there is a bad side-effect when a BGP peer sends a route for an address that does not fit any of these classifications; bird6 claims that they are "bogus routes", and then seems to drop any routes that have already been received by that peer. This problem can be very easily reproduced in bird6-1.3.1 by receiving a route outside of these ranges. The validation code appears below, and the problem can be very easily corrected by commenting it out: rte_validate(rte *e) in nest/rt-table.c: c = ipa_classify_net(n->n.prefix); if ((c < 0) || !(c & IADDR_HOST) || ((c & IADDR_SCOPE_MASK) <= SCOPE_LINK)) { log(L_WARN "Ignoring bogus route %I/%d received via %s", n->n.prefix, n->n.pxlen, e->sender->name); return 0; } I am interested to hear whether the strictness of the ipv6_classify(ip_addr *a) function would be considered a "bug" or a "feature", but from what I can tell, quagga and openbgpd do not classify addresses in such a strict fashion, and this can produce problems in mixed environments where quagga/openbgpd peers may try and send such routes to bird6. Perhaps any address that is not link-scoped should be implicitly classified as global? At the very least, receiving a "bogus route" should not result in all existing routes from that peer being dropped.

3 2

OSPF: Socket error: No buffer space available
by Sid Narasimhan 10 Jun '11

10 Jun '11

Hello, Can someone pls. provide some insight into this? Am a first-time user of BIRD and OSPF. I have two machines (bird0 and bird1) running bird with a OSFP router for the same area configured and both using a non default routing table (vr1) pointing to kernel routing table 1. One of the birds config files (on bird0) also has a large number of static routes configured, also for vr1. There are 512k static routes with contain more than 100k unique prefixes. The idea is that the other birds (bird0) OSFP will get a dump of these routes. - starting up bird0 and after a while: bird0: birdc show route table vr1 | wc -l --> 116977 bird0: ip route show table 1 | wc -l --> 116973 - then starting up bird1 and after a while: bird1: birdc show route table vr1 | wc -l --> 116977 bird1: ip route show table 1 | wc -l --> 116974 I see the "bird: OSPF: Socket error: No buffer space available" error on bird1 console, BUT all routes are propagated so there does not seem to be an issue handling this many routes. So is this some type of transient condition? Or is there a deeper hidden issue here handling this volume of routes, for which i may have to tweak things? Any help here is greatly appreciated. Thanks Sid Narasimhan

2 1

bird6 bgp - no listening socket
by Adrian Czapek 10 Jun '11

10 Jun '11

Hello, bird6.conf: -------------------------------------------------------------------------- log syslog all; router id 80.50.131.218; listen bgp address 2a03:6600:3::2 port 179 dual; protocol kernel { scan time 20; # import none; export all; } protocol static { route 2a03:6600:4::/48 reject; } protocol bgp leszczyny { local as 44124; neighbor 2a03:6600:3::1 as 44124; hold time 240; startup hold time 240; connect retry time 120; keepalive time 80; start delay time 5; error wait time 60, 300; error forget time 300; disable after error; path metric 1; default bgp_med 0; default bgp_local_pref 0; gateway direct; export all; import all; } ---------------------------------------------------------------------------------------- sadly, BGP is not working, I found that there is no listening socket created on 2a03:6600:3::2 and it refuses connections from 2a03:6600:3::1: 15:10:48.187179 IP6 2a03:6600:3::1.49296 > 2a03:6600:3::2.179: S 515376837:515376837(0) win 5760 <mss 1440,sackOK,timestamp 722432390 0,nop,wscale 6> 15:10:48.191276 IP6 2a03:6600:3::2.179 > 2a03:6600:3::1.49296: R 0:0(0) ack 515376838 win 0 There is already bird (v4) running on that machine listening on 0.0.0.0:179 How to solve this? Can both bird and bird6 (both with bgp protocol configured) on the same machine? Regards -- Adrian Czapek

3 7

Netlink: file exists problem
by Łukasz Chrustek 08 Jun '11

08 Jun '11

Hello bird-users, I have following log-filler (this after debug all all - without debug there is only bird: Netlink: File exists): Jun 8 10:53:28 rtr-waw bird: kernel1: Pruning table master Jun 8 10:53:28 rtr-waw bird: kernel1: 192.168.201.32/27: reinstalling Jun 8 10:53:28 rtr-waw bird: Netlink: File exists Jun 8 10:53:28 rtr-waw bird: kernel1: X.Y.11.16/29: reinstalling Jun 8 10:53:28 rtr-waw bird: Netlink: File exists Jun 8 10:53:28 rtr-waw bird: kernel1: X.Y.10.252/30: reinstalling Jun 8 10:53:28 rtr-waw bird: Netlink: File exists ip r l | grep X.Y.11.16 X.Y.11.16/29 dev eth1.203 proto kernel scope link src X.Y.11.17 ip r l | grep X.Y.10.252 X.Y.10.252/30 dev eth2 proto kernel scope link src X.Y.10.254 ip r l | grep 192.168.201.32 192.168.201.32/27 dev eth1.201 proto kernel scope link src 192.168.201.33 my bird.conf, section kernel: protocol kernel { #learn; preference 10000; #persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds # import filter no_export_default_1; import none; # Default is import all export all; # Default is export none } Why bird try to reinstall this routes ? How can I filter this out ? -- Pozdrawiam, brushek

3 3

Extra Tun Address Problem
by Nick 06 Jun '11

06 Jun '11

I can not reproduce in my nodes, but this happens in some of my peers with debian. ip addr add 1.2.3.4 peer 1.5.6.7/32 dev tun0 scope link #bird now establishes the BGP connection. ip addr add 1.2.3.4/32 dev tun0 scope global #bird now removes the BGP connection and says waiting for 1.5.6.7 to become my neighbor. ip addr del 1.2.3.4/32 dev tun0 #bird now establishes the BGP connection again. Is bird confused? -- Wanna turn ICANN into ICANN't? Join a darknet today: http://www.anonet2.org/darknet_comparison

2 1

BIRD and RIP
by Schmidt, Bernhard 04 Jun '11

04 Jun '11

Hi, we are using RIP(v2|NG) with very low timers for the one hop between our routers and our Anycast cluster nodes for DNS, NTP and others due to its simplicity. Historically we are running either Quagga or a self-written Python daemon to announce the anycast cluster address. In order to get to use a modern software, I've tried to use BIRD in a new deployment and failed horribly. RIPv2 ===== protocol rip RIP { debug all; period 10; port 520; interface "eth0" { metric 3; mode multicast; }; honor neighbor; authentication none; import filter { print "importing"; accept; }; export filter { print "exporting"; accept; }; } Importing routes (which is the thing we don't need) seems to work. Exporting routes does not work at all. I get a single message at startup saying bird: RIP: Broadcasting routing table to eth0 bird: RIP: Unexpected error at rip transmit: Invalid argument bird: RIP: Unexpected error at rip transmit: Unknown error 18446744073709551615 and nothing more of that. RIPng ===== protocol rip RIPng { debug all; period 10; port 521; interface "eth0" { metric 3; mode multicast; }; honor neighbor; authentication none; import filter { print "importing"; accept; }; export filter { print "exporting"; accept; }; } Importing routes does not work at all, probably because it has bound the listening socket to the global address on eth0 udp 0 0 2001:4ca0:0:101::81:521 :::* 4895/bird6 Sending routes does not really work either. a) it completely ignores the period setting and sends every 30 seconds b) it speaks RIPng on port 520 by default, you have to set it in the config c) it sets version=2 in the RIPng header (probably because it thinks multicast=RIPv2), which makes all routers ignore the update anyway So, the big question is, am I doing something horribly wrong or is RIP just broken/untested in BIRD? Best Regards, Bernhard

2 1