- Bird-users - Mailing Lists

Errors like "bgp1: Error: Hold timer expired"
by Roger Whittaker 05 Jan '17

05 Jan '17

I'm trying to use bird to help prevent spam as described here: https://debian-administration.org/article/715/Preventing_SPAM_connections_w… I understand very little about BGP, so I'm really using that article as a "recipe", and have used the config file there more or less as is, except for changing the router id setting and enabling logging (and I've increased scan time to 600). First question: is trying to use bird in this way in any case this a sensible thing to do? If so: second question - I'm seeing the following behaviour: 2017-01-05 15:24:21 <INFO> Started 2017-01-05 15:24:21 <ERR> KRT: Received route 0.0.0.0/0 with unknown ifindex 2 2017-01-05 15:27:59 <RMT> bgp1: Error: Hold timer expired 2017-01-05 15:34:01 <RMT> bgp1: Error: Hold timer expired 2017-01-05 15:34:21 <ERR> KRT: Received route 0.0.0.0/0 with unknown ifindex 2 2017-01-05 15:40:11 <RMT> bgp1: Error: Hold timer expired 2017-01-05 15:44:21 <ERR> KRT: Received route 0.0.0.0/0 with unknown ifindex 2 2017-01-05 15:46:16 <RMT> bgp1: Error: Hold timer expired 2017-01-05 15:52:20 <RMT> bgp1: Error: Hold timer expired 2017-01-05 15:54:21 <ERR> KRT: Received route 0.0.0.0/0 with unknown ifindex 2 2017-01-05 15:58:35 <RMT> bgp1: Error: Hold timer expired I can't find much reference to these errors in the mailing list archives. But it seems that when the "Hold timer expired" errors happen, the blackhole entries in the routing table disappear for a while. It would be great if someone could comment on this. Roger -- ======================== Roger Whittaker roger(a)disruptive.org.uk ========================

3 4

old tools
by Alexander Lazarev 02 Jan '17

02 Jan '17

Hello, bird users. Suggestion for developers. Please consider updating tools in your packages. Couldn't rebuild srpm on arm64 CentOS 7 because of old tools/config.guess. Cheers.

3 5

Upgrade to 1.6.3
by Michal 02 Jan '17

02 Jan '17

Hi, I was trying to upgrade my bird instance from v1.6.0 to v1.6.3 today. Unfortunately immediately after start the bird started generating these messages 2016-12-30 12:02:35 <INFO> Started 2016-12-30 12:02:43 <WARN> I/O loop cycle took 8679 ms for 8 events 2016-12-30 12:02:43 <WARN> Kernel dropped some netlink messages, will resync on next scan. 2016-12-30 12:02:43 <WARN> Kernel dropped some netlink messages, will resync on next scan. 2016-12-30 12:02:52 <WARN> Kernel dropped some netlink messages, will resync on next scan. 2016-12-30 12:03:03 <WARN> Kernel dropped some netlink messages, will resync on next scan. 2016-12-30 12:03:10 <WARN> Kernel dropped some netlink messages, will resync on next scan. 2016-12-30 12:03:16 <WARN> Kernel dropped some netlink messages, will resync on next scan It's a full BGP IPv4 instance with just three interfaces. Tested on linux kernels 4.4 or 4.8. Package is from cznic deb repository. I can see the warning log line was added at Dec 20 2016, which ended up in 1.6.3 release. Hence this was happening probably even before the upgrade, but it was not visible. So the question is simple. Does it means there is something terribly wrong with my machine, or the high rate of this warning is expected? Cheers Michal

4 10

Route aggregation
by Paul Donohue 31 Dec '16

31 Dec '16

I see that Alexander V. Chernikov wrote a patch to implement route aggregation back in 2012, and Ondrej Zajicek was planning on merging it with some changes: http://bird.network.cz/pipermail/bird-users/2013-January/003337.html However, it does not look like this was ever actually merged, and the latest version of the patch ("Version 7") seems to be missing from the mailing list archives. Does anyone know where I can find the latest version of this patch? Is there any chance this patch will ever be merged? Thanks! -Paul

1 0

having trouble getting default to be added to route table, says filtered out
by Jerry Scharf 31 Dec '16

31 Dec '16

Hi, I did a quick look at the archives and didn't see exactly what I was trying discussed. I have some border machines running bird connected to junpiers that are bgp peering with our ISPS. I have the junipers set up such that they generate a default route and send it to the border machines. I want the border machines to put it in the system routing table and then pass that on to the inside systems. Everyone is speaking bgp, one AS for the outside and one for the inside. I am running 1.4.5 (centos 7 release) here are the parts of the config that are involved: filter load_default { if net = [0.0.0.0/0] then accept; else reject; } template bgp toedge { description "bgp to edge/ISP as"; local as 65401; direct; export filter outside_only; import filter load_default; allow local as; bfd on; source address 172.18.2.10; } protocol bgp edgeA from toedge { neighbor 172.18.2.1 as 65401; debug all; } protocol bgp edgeB from toedge { neighbor 172.18.2.2 as 65401; } here's the debug output: 2016-12-30 11:28:53 <INFO> Started 2016-12-30 11:28:53 <TRACE> edgeA: Started 2016-12-30 11:28:53 <TRACE> edgeA: Connect delayed by 5 seconds 2016-12-30 11:28:57 <TRACE> edgeA: Connecting to 172.18.2.1 from local address 172.18.2.10 2016-12-30 11:28:57 <TRACE> edgeA: Connected 2016-12-30 11:28:57 <TRACE> edgeA: Sending OPEN(ver=4,as=65401,hold=240,id=01020304) 2016-12-30 11:28:57 <TRACE> edgeA: Got OPEN(as=65401,hold=90,id=ac120001) 2016-12-30 11:28:57 <TRACE> edgeA: Sending KEEPALIVE 2016-12-30 11:28:57 <TRACE> edgeA: Got KEEPALIVE 2016-12-30 11:28:57 <TRACE> edgeA: BGP session established 2016-12-30 11:28:57 <TRACE> edgeA: Connected to table master 2016-12-30 11:28:57 <TRACE> edgeA: State changed to feed 2016-12-30 11:28:57 <TRACE> edgeA < added 198.48.100.20/32 dev lo 2016-12-30 11:28:57 <TRACE> edgeA < added 198.48.100.21/32 dev lo 2016-12-30 11:28:57 <TRACE> edgeA < added 8.25.217.22/32 dev lo 2016-12-30 11:28:57 <TRACE> edgeA: State changed to up 2016-12-30 11:28:57 <TRACE> edgeA: Sending UPDATE 2016-12-30 11:28:57 <TRACE> edgeA: Sending End-of-RIB 2016-12-30 11:28:57 <TRACE> edgeA < filtered out 10.200.32.0/28 via 10.200.0.3 on eth4 2016-12-30 11:28:57 <TRACE> edgeA < filtered out 10.200.0.1/32 via 10.200.0.3 on eth4 2016-12-30 11:28:57 <TRACE> edgeA < filtered out 10.200.16.1/32 via 10.200.0.3 on eth4 2016-12-30 11:28:57 <TRACE> edgeA: Got KEEPALIVE 2016-12-30 11:28:57 <TRACE> edgeA: Got UPDATE 2016-12-30 11:28:57 <TRACE> edgeA: Got End-of-RIB 2016-12-30 11:28:57 <TRACE> edgeA: Got UPDATE 2016-12-30 11:28:57 <TRACE> edgeA > filtered out 0.0.0.0/0 via 172.18.2.1 on eth1 2016-12-30 11:28:58 <TRACE> edgeA < filtered out 10.200.16.1/32 via 10.200.16.3 on eth5 As you can see (second line from the bottom of the debug), it got the default advertisement from the peer and bird says it filtered it out (the other filters are correct.) I set allow-local-as for the peer and have a filter that is supposed to match and accept exactly the route that says was filtered. what am I doing wrong? BTW, I am also having trouble with setting localpref in a filter. here's the config pieces: function is_primary() { return net = [198.48.100.10/32, 198.48.100.20/32]; } function is_secondary() { return net = [8.25.217.10/32, 8.25.217.21/32]; } function is_tertiary() { return net ~ [198.48.100.0/24+, 8.25.217.0/24+]; } filter outside_only { if is_primary() then bgp_local_pref=100; else if is_secondary() then bgp_local_pref=80; else if is_tertiary() then bgp_local_pref=60; if net_outside() then accept; else reject; } They all end up on the junipers with locappref of 60. How do I do this right? thanks in advance, jerry

2 2

OSPF: Route attribute "ospf_tag" lost between different OSPF instances
by markus/grundmann 28 Dec '16

28 Dec '16

Hello! I believe that I'm a user with BIRD experiences but current I have no idea why the attribute "ospf_tag" from one OSPF instance to another is unavailable. In this real life example you can see that I receive a default route from my ISP that is tagged with "7b". This tag is not visible on the VPN client. I use for each VPN network a OSPF instance with some filter rules but only static routes (Core VPN) with a "ospf_tag" are usable to filter like "if ospf_tag = xyz then ..." How can I exchange routes based on a "ospf_tag" between two or more OSPF router instances? [Core VPN Router] BIRD 1.6.0 ready. 0.0.0.0/0 via 82.206.X.33 on lagg0 [titan 2016-12-25] * E2 (150/5/10) [7b] [217.173.X.190] [VPN Client] BIRD 1.6.0 ready. 0.0.0.0/0 via 10.82.16.1 on tun2 [lte 00:28:10] * E1 (150/5) [82.206.X.34] via 10.82.17.1 on tun3 [umts 00:28:11] E1 (150/10) [82.206.X.34] -- Static-Tagging Works Fine --- route 11.0.0.0/8 via 82.206.X.33 { ospf_tag=16170; }; filter openvpn9x16171_export { if net = 0.0.0.0/0 then { ospf_metric1 = SEC_M1_VPN; ospf_metric2 = SEC_M2_VPN; accept; } // [...] if ospf_tag = 16171 then { <== WORKS FINE because static route ospf_metric1 = SEC_M1_VPN; ospf_metric2 = SEC_M2_VPN; accept; } reject; } -- Best regards, Markus

2 6

Version 1.6.3
by Ondrej Filip 23 Dec '16

23 Dec '16

Dear users, a new version of the 1.6.x branch is out: Version 1.6.3 o Large BGP communities o BFD authentication (MD5, SHA1) o SHA1 and SHA2 authentication for RIP and OSPF o Improved documentation o Several bug fixes This is meant to be a stable version. An upgrade is recommended. Enjoy it! And Merry Xmas! Ondrej

4 3

Re: BIRD patches for IP-in-IP
by Mohammad Banikazemi 22 Dec '16

22 Dec '16

2 1

Dynamic cost?
by Mike Jones 22 Dec '16

22 Dec '16

Hi, I have an OSPF based network using bird for routing the core and it seems to work fine, however the network is geographically diverse and some of the routing is sub-optimal. Specifically, the default route is going shortest hops rather than lowest latency. What I would like to do is have the OSPF cost reflect the latency of the link, however I am having a problem coming up with a scalable/automated way of doing this. As far as I can tell there is no built in "latency to peer" I can reference? I could configure a manual entry for each peer in the config file, however that doesn't seem very manageable, even with some kind of script to generate the config file. >From what I can gather there is no way for a filter to reference an external file/database/script to adjust the routes on import. I even considered a convoluted approach of having a script inject the peers IP address in to a special kernel table and using the route metric to feed numbers in to bird, but couldn't find a way of storing the data and referencing it on a later route lookup. Basically what I want is that when an OSPF peer comes up I ping it then set the cost for all routes received from that neighbour to the latency (with some basic sanity like a min and max). I don't expect the latency to vary much once a link is up, however I do need to auto-discover new peers appearing on the network. Any ideas? Thanks - Mike Jones

5 6

BIRD 1.6.2 removes IPv6 kernel routes
by Robert Sander 21 Dec '16

21 Dec '16

Hi, I have an issue with BIRD 1.6.2 from http://bird.network.cz/debian/ on Debian jessie: When bird6 is running and I "ifup" an interface with a static IPv6 address the address is added but no IPv6 route in the associated network via that interface. When bird6 is not running everything works. It looks like bird6 1.6.2 is eating IPv6 routes set by the kernel. I have not encountered this issue with the IPv4 bird daemon. After downgrading to bird 1.4.5 from Debian jessie everything works as expected. What information do you need? Regards -- Robert Sander Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-43 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

3 5