August 2017 - Bird-users

bird: memory exhausted
by Job Snijders 10 Aug '17

10 Aug '17

Dear all, It appears I'm hitting some kind of limit in yacc stuff (on 1.6.3-1+trusty+1): router# bird -c rpki-match-roa-ipv4.conf -p bird: rpki-match-roa-ipv4.conf, line 4998: memory exhausted The error message is generated by generated code: $ grep -r 'memory exhausted' * Binary file bird matches obj/conf/cf-parse.tab.c: yyoverflow (YY_("memory exhausted"), obj/conf/cf-parse.tab.c: yyerror (YY_("memory exhausted")); Binary file obj/conf/all.o matches Binary file obj/conf/cf-parse.tab.o matches The config file can be found here: http://instituut.net/~job/rpki-match-roa-ipv4.conf.txt Any ideas how to increase the memory available to things on the stack? Kind regards, Job

3 3

Re: Unexpected behavior of static routes
by Alexander Demenshin 10 Aug '17

10 Aug '17

On 2017-05-10 13:16, Ondrej Zajicek wrote: > But such design would bring plenty of issues w.r.t. multiple routing > tables - may next hops resolve just in the same routing table or also > in > another routing table? Well, at least in Linux device/direct routes may exist in any table, so where is the difference between device/direct routes and arbitrary next-hop route? How I would implement this: - Try to find if next-hop is routable via any of existing devices (including explicitly routed networks - as in my case); - If it is routable (which also means that device has to be up), install it (so it can be exported to the kernel tables). > What if the device route is available, but not exported to kernel? You mean if it is configured but not exported? Then it should be ignored, obviously, though this could happen only in few cases: - device does not exists (yet) - device is not up (kernel will not accept any routes in this case) - protocol is disabled If no kernel export is configured at all then the route does not make any sense anyway. > Static onlink routes is something that probably could be implemented > and > it is a good idea. This could solve one of the most typical scenarios - keep static (local) routes up for specified set of devices/gateways - once they become available. What is interesting, quagga behaves exactly in the same way as bird, and only cisco (well, may be other routers too) does what is (logically) expected - and it allows Linux-like onlink routes, which specify both device and gateway address, and those routes are linked to device state (i.e. exported and used when device is active). --- Best regards, Alexander.

3 3

gateway recursive
by Mikhail Mayorov 10 Aug '17

10 Aug '17

Hi all! Please help me with recursion to caclulate bgp_next_hop using IGP. I have 2 router "A" and "B" connected to each other via iBGP. Each of the routers has connection to the outside world in different AS and get full view. "A" has a eBGP session to the neighbor "A2" and "B" has a eBGP session to the neighbor "B2". I configure "gateway recursive; direct;" on iBGP. In this case, all the routes from the A2 got to B via A are as unreachable. A IP: 95.174.97.1/26 A2 IP: 188.43.24.90/30 B: 95.174.97.33/26 B2: 87.245.238.204/31 This is debug from birdcl router B: bird ~ # birdcl 'show route for 37.231.192.1' table master all BIRD 1.6.3 ready. 37.231.192.0/22 via 87.245.238.204 on vlan91-retn [retn_ipv4 07.08.2017 11:06:57] * (100) [AS47589i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 9002 15412 9155 47589 BGP.next_hop: 87.245.238.204 BGP.med: 999 BGP.local_pref: 100 BGP.community: (9002,9002) (9002,64679) (49037,0) (49037,10001) unreachable [twix_ipv4 07.08.2017 17:17:17 from 95.174.97.1] (100) [AS47589i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 20485 15412 9155 47589 BGP.next_hop: 188.43.24.90 BGP.med: 999 BGP.local_pref: 100 BGP.community: (20485,22007) (20485,22307) (49037,0) bird ~ # birdcl 'show route for 188.43.24.90' table master all BIRD 1.6.3 ready. 188.43.24.88/30 via 95.174.97.1 on vlan8 [twix_ipv4 07.08.2017 17:17:17] * (100) [i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: BGP.next_hop: 95.174.97.1 BGP.med: 0 BGP.local_pref: 500 BGP.community: (49037,49037) bird ~ # birdcl 'show route for 95.174.97.1' table master all BIRD 1.6.3 ready. 95.174.97.0/26 dev vlan8 [direct1 07.08.2017 00:20:09] * (240) Type: device unicast univ via 95.174.97.1 on vlan8 [twix_ipv4 07.08.2017 17:17:17] (100) [i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: BGP.next_hop: 95.174.97.1 BGP.med: 0 BGP.local_pref: 500 BGP.community: (49037,49037) -- Regards, Mikhail V. Majorov

2 2

Error: Hold timer expired
by Marek Królikowski 09 Aug '17

09 Aug '17

Hello guys, I buy VPS with BGP and try setup BGP session but got strange problem. VPS support send me this information to setup session: "Please peer with 185.144.XXX.YYY, you will need to enable eBGP multihop. Our ASN is XXXX. The IPv6 peer address is 2a04:9dc0:XX:YYY::1" My bird configuration looks like this: --------------------------------------- router id 85.204.XXX.YYY; # debug protocols all; protocol device { scan time 10; } protocol static { route 2a04:9dc0:XX:YYY::1/128 via "eth0"; } protocol kernel { device routes; import none; scan time 15; export filter { if net = 2a04:9dc0:XX:YYY::1/128 then reject; if source = 2a04:9dc0:XX:YYY::1/128 then reject; accept; }; } protocol bgp Romania { description "Romania link local"; local as YYYYY; source address 2a04:9dc0:X:YY::f0; graceful restart on; default bgp_local_pref 200; multihop 2; neighbor 2a04:9dc0:XX:YYY::1 as XXXX; import filter { if net = 2a04:9dc0:XX:YYY::1/128 then reject; if source = 2a04:9dc0:XX:YYY::1/128 then reject; if bgp_path.len > 49 then reject; accept; }; export filter { if net = 2a07:1c44:3511::/48 then accept; reject; }; } --------------------------------------- In logs got it: Aug 8 16:21:41 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:24:02 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:27:07 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:35:58 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:37:25 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:39:27 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:41:57 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 16:56:19 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:00:29 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:06:10 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:09:58 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:13:01 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:15:08 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:18:15 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:22:58 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:29:17 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:31:49 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:35:17 ro-bgp bird6: Romania: Error: Hold timer expired Aug 8 17:40:08 ro-bgp bird6: Romania: Error: Hold timer expired root@bgp:~# birdc6 show protocols all Romania BIRD 1.6.3 ready. name proto table state since info Romania BGP master up 16:22:37 Established Description: Romania link local Preference: 100 Input filter: (unnamed) Output filter: (unnamed) Routes: 11560 imported, 5 exported, 11560 preferred Route change stats: received rejected filtered ignored accepted Import updates: 11560 0 0 0 11560 Import withdraws: 0 0 --- 0 0 Export updates: 11586 11560 21 --- 5 Export withdraws: 0 --- --- --- 0 BGP state: Established Neighbor address: 2a04:9dc0:XX:YYY::1 Neighbor AS: XXXX Neighbor ID: 185.144.XXXX Neighbor caps: refresh restart-aware AS4 Session: external multihop AS4 Source address: 2a04:9dc0:X:YY::f0; Hold timer: 27/90 Keepalive timer: 23/30 root@bgp:~# birdc6 show protocols all Romania BIRD 1.6.3 ready. name proto table state since info Romania BGP master start 16:24:05 Idle BGP Error: Hold timer expired Description: Romania link local Preference: 100 Input filter: (unnamed) Output filter: (unnamed) Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0 BGP state: Idle Neighbor address: 2a04:9dc0:XX:YYY::1 Neighbor AS: XXXX Error wait: 57/120 Last error: BGP Error: Hold timer expired Best Regards Marek Krolikowski

2 1

BIRD BGP and VRF - Cannot assign requested address
by Clément Guivy 08 Aug '17

08 Aug '17

Hello, I am trying to set up 2 BIRD routers as AS border routers (on Debian 9). Installation is as follows : |BIRD router 1|-----IBGP-----|BIRD router 2| | | EBGP EBGP | | |Hardware router 1|---IBGP---|Hardware router 2| | (downstream) | | (downstream) | (later the BIRD routers would also be connected to our upstreams ISPs, but for the sake of simplicity let's just consider this part of the setup) I plan to use both ipv4 and ipv6 and also, on BIRD routers both the forwarding and the BGP peerings are to take place in a linux vrf named "internet" (using l3mdev, not namespaces or custom ip rules). At the BIRD level I also set up a table named "internet". Now, to my problem : the EBGP peerings with the downstreams routers are UP, but on the other hand the IBGP between the two BIRD routers won't come up, I get the following error messages : On ipv4 peering, the service complains that : ibgp_internet: Socket error: bind: Cannot assign requested address On ipv6 peering : the service won't complain but using birdc6 I can see that the protocol says : Socket: Network is unreachable Both routers have almost identical config (apart from the IP addresses of course), here is the conf on BIRD router 1 : ------------------------------------------------------ ---------------------bird.conf------------------------ ------------------------------------------------------ table internet; router id 10.206.81.36; define my_as=205555; protocol device { } protocol kernel { kernel table 10; table internet; metric 64; import all; export all; scan time 10; } protocol static default_route_to_bgp { import all; table internet; route 0.0.0.0/0 reject; } template bgp template_base_bgp { med metric; } protocol bgp ibgp_internet from template_base_bgp { table internet; source address 10.206.81.81; local as my_as; neighbor 10.206.81.82 as my_as; import all; export all; next hop self; } protocol bgp downstream_internet from template_base_bgp { table internet; export where proto = "default_route_to_bgp"; source address 10.206.81.90; local as my_as; neighbor 10.206.81.89 as 65206; } ------------------------------------------------------ ------------------end of bird.conf-------------------- ------------------------------------------------------ ------------------------------------------------------ ---------------------bird6.conf----------------------- ------------------------------------------------------ table internet; router id 10.206.81.36; define my_as=205555; protocol device { } protocol kernel { kernel table 10; table internet; metric 64; import all; export all; scan time 10; } template bgp template_base_bgp { med metric; } protocol bgp ibgp_internet from template_base_bgp { table internet; source address 2a0b:95c0:0000:0101::1; local as my_as; neighbor 2a0b:95c0:0000:0101::2 as my_as; import all; export all; next hop self; } protocol static default_route_to_bgp { import all; table internet; route ::/0 reject; } protocol bgp downstream_internet from template_base_bgp { table internet; export where proto = "default_route_to_bgp"; source address 2a0b:95c0:0000:0102::2; local as my_as; neighbor 2a0b:95c0:0000:0102::1 as 65206; } ------------------------------------------------------ -----------------end of bird6.conf-------------------- ------------------------------------------------------ The network interfaces seems to be properly UP and attached to the internet VRF, here is the IBGP one : # ip addr show eth1.3 7: eth1.3@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master internet state UP group default qlen 1000 link/ether 94:18:82:ab:8b:ec brd ff:ff:ff:ff:ff:ff inet 10.206.81.81/29 brd 10.206.81.87 scope global eth1.3 valid_lft forever preferred_lft forever inet6 2a0b:95c0:0:101::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::9618:82ff:feab:8bec/64 scope link valid_lft forever preferred_lft forever and here is the EBGP one (the one which has the functional peering) : # ip addr show ens1.14 8: ens1.14@ens1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master internet state UP group default qlen 1000 link/ether 9c:dc:71:45:5f:e0 brd ff:ff:ff:ff:ff:ff inet 10.206.81.90/29 brd 10.206.81.95 scope global ens1.14 valid_lft forever preferred_lft forever inet6 2a0b:95c0:0:102::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::9edc:71ff:fe45:5fe0/64 scope link valid_lft forever preferred_lft forever Now the "internet" kernel routing table, we can see that the local and broadcast routes are attached to it too : # ip route show table internet unreachable default proto bird metric 64 broadcast 10.206.81.80 dev eth1.3 proto kernel scope link src 10.206.81.81 10.206.81.80/29 dev eth1.3 proto kernel scope link src 10.206.81.81 local 10.206.81.81 dev eth1.3 proto kernel scope host src 10.206.81.81 broadcast 10.206.81.87 dev eth1.3 proto kernel scope link src 10.206.81.81 broadcast 10.206.81.88 dev ens1.14 proto kernel scope link src 10.206.81.90 10.206.81.88/29 dev ens1.14 proto kernel scope link src 10.206.81.90 local 10.206.81.90 dev ens1.14 proto kernel scope host src 10.206.81.90 broadcast 10.206.81.95 dev ens1.14 proto kernel scope link src 10.206.81.90 Finally, netstat shows that the BGP service is listening on * as it is supposed to. We also see the established EBGP downstream sessions : # netstat -an | grep 179 tcp 0 0 0.0.0.0:179 0.0.0.0:* LISTEN tcp 0 0 10.206.81.90:179 10.206.81.89:9266 ESTABLISHED tcp6 0 0 :::179 :::* LISTEN tcp6 0 0 2a0b:95c0:0:102::2:179 2a0b:95c0:0:102:::64247 ESTABLISHED and tcp_l3mdev_accept is enabled in the kernel config : # sysctl net.ipv4.tcp_l3mdev_accept net.ipv4.tcp_l3mdev_accept = 1 So overall it seems like BIRD fails to bind to one interface, this is possibly linked to the kernel VRF setup but I can't see why it doesn't work when the peering to downstream routers using the same VRF do work properly. Any help would be greatly appreciated. Thanks. clément

2 9

Hold time expired error
by Ajai Kumar 06 Aug '17

06 Aug '17

Dear All, We are facing problem with few peers in our IX. Frequently they get Hold Timer Expired Error and they are not able to ping our route server IP. After shut no shut this problem resolves for sometime. One log message appended bgp_hold_timeout:4690: NOTIFICATION sent to X.X.X.X (External AS 132953): code 4 (Hold Timer Expired Error), Reason: holdtime expired for X.X.X.X (External AS 132953), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 728368567 snd_nxt: 728368624 snd_wnd: 15744 rcv_nxt: 429172199 rcv_adv: 429188583, hold timer out 90s, hold timer remain 0s Requesting for help pls. Regards, Ajai Kumar -- (M) +91-9868477444 Skype ID:erajay P-mail: joinajay1 at gmail.com ................................. Please don't print this email unless you really need to. This will preserve trees on our planet.

4 5

Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory
by Janvier Rwakagabo 05 Aug '17

05 Aug '17

Hi all Need your help, I have installed properly bird, Edit bird.conf file with my configuration, then when I restart the service bird it give this error #/etc/init.d/bird restart stop: Unknown instance: start: Job failed to start by typing #birdc it give below error #birdc Unable to connect to server control socket (/run/bird/bird.ctl): No such file or directory I checked under /run/bird/ folder there is no bird.ctl only bird6.ctl is present I deleted bird.conf and restaured default bird.conf the issue was solved, by editing again bird.conf and restarting the service, bird.ctl is droped again. Can anyone assist me to solve this issue. Thanks, Regards, Janvier R.

2 2

Read-only access
by Łukasz Trąbiński 03 Aug '17

03 Aug '17

Hi It’s possible to do read only access via birdc? I know that I can setup LG but question is about command line (birdc, birdctl)? Thnx

4 4

You have plans to add to the bird native support for working with the VPP fib.
by Гришин В.С. 02 Aug '17

02 Aug '17

Hi, You have plans to add to the bird native support for working with the VPP fib. References for understanding the my question. https://wiki.fd.io/view/VPP/Features https://github.com/FRRouting/frr/wiki/Alternate-forwarding-planes:-VPP --- This link contains a description of the very curve way to support VPP fib by linux daemons. https://docs.fd.io/vpp/17.07/release_notes_1707.html Regards, Vladislav

2 2

BGP Conditional Advertisement
by e2rd 02 Aug '17

02 Aug '17

Hi, Is there any way to configure BGP Conditional Advertisement like in cisco: http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/16… ? -- Łukasz

3 4