September 2018 - Bird-users

BGP-LS
by Fabien VINCENT (Bird-Users) 21 Sep '18

21 Sep '18

Dear List, Do you know if Bird supports BGP-LS AFI 16388 / SAFI 71 ? If yes, where can I found documentation ? If no, any plan for this ? Thanks ! -- Fabien VINCENT @beufanet

2 1

No routes being broadcast
by Leon A. Morris 19 Sep '18

19 Sep '18

Hi, I am hoping someone here might be able to give me a hand. I am having issues getting BIRD to broadcast routes to other peers. Attached is my config, could someone look at it and advise. Thanks, Lee Morris Ki’tpu Computer & Technical Services PH: (506) 962-8687

1 0

Static routes stuck in dormant state (interface discovery broken?)
by Kenth Eriksson 19 Sep '18

19 Sep '18

Hi! I'm using BIRD 2.0.2 and have trouble with static routes that gets stuck in dormant state. It looks as the problem happens if the static route is pushed into BIRD config before the interface exists. BIRD detects when interfaces go up and down, but misses when interfaces are added. The only way I have found to kick BIRD out if this state is to issue another configure command after the interface exists. Reproducing this is very easy, simply add a static route over a sub-interface that is not yet created, this leaves the route in dormant state Add static route over a sub-interface protocol static { route 172.23.1.0/24 via "eth1.666"; } Reconfigure BIRD, note it picks it up as dormant. bird> configure Reading configuration from /tmp/bird.conf Reconfigured bird> show static 172.23.1.0/24 dev eth1.666 (dormant) bird> Now create the sub-interface and bring it up vconfig add eth1 666 ifconfig eth1.666 up BIRD does not discover that the interface was created and does not push the route into the kernel. Thanks, Kenth

2 7

Help with AS-Path manipulation
by Marcio 18 Sep '18

18 Sep '18

Dear, Could you help me with an information? Is there a way to generate an announce modifying the AS Path field using BIRD? For example, i´d like to announce a prefix with a false AS Path field where i could change it, inserting or removing an AS.

5 9

Multiple RIB
by Diarmuid O Briain 18 Sep '18

18 Sep '18

Hi, I have been trying to setup a simple config using multiple RIB for a Route Server. Here are two compatible configurations, the first with multiple tables, the second with a single master configuration. The single master works fine and the peers get routing updates but the multiple tables version does not pass routes. ANy ideas why ? regards, Diarmuid ######### bird.conf multiple RIB ######### log syslog all; define LOCAL_AS = 5999; define RTR_ADDR = 199.9.9.1; include "import_policy_v4"; router id 199.9.9.1; listen bgp address RTR_ADDR; template pipe PIPES { table master; mode transparent; } template bgp PEERS { rs client; local as LOCAL_AS; source address RTR_ADDR; import filter import_policy_v4; import all; export all; } protocol device { scan time 10; } protocol kernel { export all; scan time 15; } # as5111 member table T5111; protocol pipe P5111 from PIPES { description "as5111"; peer table T5111; } protocol bgp as5111 from PEERS { description "as5111"; neighbor 199.9.9.11 as 5111; table T5111; } # as5222 member table T5222; protocol pipe P5222 from PIPES { description "as5222"; peer table T5222; } protocol bgp as5222 from PEERS { description "as5222"; neighbor 199.9.9.22 as 5222; table T5222; } # as5333 member table T5333; protocol pipe P5333 from PIPES { description "as5333"; peer table T5333; } protocol bgp as5333 from PEERS { description "as5333"; neighbor 199.9.9.33 as 5333; table T5333; } ######### bird.conf master RIB only ######### log syslog all; define LOCAL_AS = 5999; define RTR_ADDR = 199.9.9.1; include "import_policy_v4"; router id 199.9.9.1; listen bgp address RTR_ADDR; template bgp PEERS { rs client; local as LOCAL_AS; source address RTR_ADDR; import filter import_policy_v4; import all; export all; } protocol device { scan time 10; } protocol kernel { export all; scan time 15; } # as5111 member protocol bgp as5111 from PEERS { description "as5111"; neighbor 199.9.9.11 as 5111; } # as5222 member protocol bgp as5222 from PEERS { description "as5222"; neighbor 199.9.9.22 as 5222; } # as5333 member protocol bgp as5333 from PEERS { description "as5333"; neighbor 199.9.9.33 as 5333; } -- *Irish by birth, located in Uganda but Munster by the grace of God.*

2 1

BIRD Ubuntu Package
by Jonathan Stewart 17 Sep '18

17 Sep '18

Hi All, Where are you getting the latest BIRD 1.6.4 and 2.0.2 releases for Ubuntu? The official repository is 1.6.3: https://packages.ubuntu.com/bionic/bird The PPA is also at 1.6.3: https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird Finally, there are instructions on the BIRD site: https://bird.network.cz/?download&tdir=debian/ It says that there are packages for Ubuntu, but following the process results in an error: E: The repository 'http://bird.network.cz/debian bionic Release' does not have a Release file. Is there another location i'm missing? How are others dealing with lack of packages? Thanks, Jonathan Stewart MBIX.ca

1 0

Two ASes in iBGP configuration
by Marcio 14 Sep '18

14 Sep '18

Dear, I have a BIRD router performing a iBGP connection with a ExaBGP software acting like a route collector. When BIRD receives an announcement, it forward to the ExaBGP. I think the BIRD is forwarding only the announcements that change the best path to a prefix but, actually i need that all announcements received(best or not) be forward to ExaBGP. It there a way do perform this? I attached a simple diagram to show you the explained behavior.

2 2

Routes received from another AS marked as IGP
by Marcio 13 Sep '18

13 Sep '18

Dear, I have a topology where each AS is represented by a BIRD router. But in the BIRD table of the routers. The announcements received are marked as IGP but all the BGP sessions are done between different ASes. Do you know why it occur? Follow an example about a prefix announced by two different ASes and marked as IGP origin in a third one. 10.3.1.0/24 unicast [SDNRTR 13:18:10.201] * (100) [AS65507i] via 192.168.1.1 on eth0 Type: BGP univ BGP.origin: *IGP* BGP.as_path: 65507 BGP.next_hop: 192.168.1.1 BGP.local_pref: 100 unicast [R6 21:25:23.642] (100) [AS65501i] via 192.168.7.2 on eth1 Type: BGP univ BGP.origin: *IGP* BGP.as_path: 65501 BGP.next_hop: 192.168.7.2 BGP.local_pref: 100

2 2

Question about BIRD feature.
by Marcio 13 Sep '18

13 Sep '18

Dear, Is it possible to know which criteria BIRD used to prefer one route rather than another directed to the same BGP prefix?

3 3

Multiple neighbours between same devices
by Saku Ytti 11 Sep '18

11 Sep '18

I'm trying to setup between DUT<->Bird in same interface multiple iBGP neighbours with DUT IP and routerID staying same, and Bird sourceIP and table changing. If I configure just 1, it works grand, the 2nd one won't come up. If I change the order, the previous one which didn't work now works, and previous which did work, now does not. bird.conf: router id 100.100.100.100; filter f_export { accept; } template bgp clients { neighbor 204.42.112.1; local as 65000; neighbor as 65000; ipv4 { import none; export filter f_export; add paths rx; }; } include "clients.conf"; clients.conf: ipv4 table t_client1; protocol bgp client1 from clients { router id 204.42.112.100; source address 204.42.112.100; ipv4 { table t_client1; }; } include "routes/client1.conf"; ipv4 table t_client2; protocol bgp client2 from clients { router id 204.42.112.101; source address 204.42.112.101; ipv4 { table t_client2; }; } include "routes/client2.conf"; clients1.conf: protocol static { ipv4 { table t_client1; }; route 100.101.1.0/24 unreachable; route 100.101.2.0/24 unreachable { bgp_local_pref = 99; }; } I'm running debugging on, and getting no complains. I don't really have any idea how to debug this in 'birdc', everything I check seems fine. I tried for heck of it 'strict bind;' no help. bird: client1: Channel ipv4 connected to table t_client1 bird: client1: Initializing bird: client2: Channel ipv4 connected to table t_client2 bird: client2: Initializing bird: client1: Starting bird: client1: State changed to start bird: client2: Starting bird: client2: State changed to start bird: Started bird: client1: Started bird: client1: Connect delayed by 5 seconds bird: client1: Connecting to 204.42.112.1 from local address 204.42.112.100 bird: client1: Connected bird: client1: Sending OPEN(ver=4,as=65000,hold=240,id=cc2a7064) bird: client1: Got OPEN(as=65000,hold=90,id=204.42.110.40) bird: client1: Sending KEEPALIVE bird: client1: Got KEEPALIVE bird: client1: BGP session established bird: client1: State changed to up bird: client1: Got UPDATE bird: client1 > filtered out 129.250.15.35/32 unreachable bird: client1 > filtered out 198.64.6.173/32 unreachable bird: client1 > filtered out 129.250.15.39/32 unreachable bird: client1 > filtered out 129.250.15.40/32 unreachable bird: client1 > filtered out 129.250.26.240/28 unreachable bird: client1 > filtered out 129.250.35.250/32 unreachable bird: client1 > filtered out 129.250.35.251/32 unreachable bird: client1 > filtered out 129.250.38.61/32 unreachable bird: client1 > filtered out 129.250.47.99/32 unreachable bird: client1 > filtered out 129.250.48.0/24 unreachable bird: client1 > filtered out 129.250.49.0/24 unreachable bird: client1 > filtered out 157.238.66.224/27 unreachable bird: client1 > filtered out 165.254.18.128/25 unreachable bird: client1 > filtered out 165.254.19.128/25 unreachable bird: client1 > filtered out 198.58.5.0/24 unreachable bird: client1 > filtered out 198.64.6.107/32 unreachable bird: client1 > filtered out 198.64.6.110/32 unreachable bird: client1 > filtered out 198.64.6.116/32 unreachable bird: client1 > filtered out 198.64.6.127/32 unreachable bird: client1 > filtered out 198.64.6.205/32 unreachable bird: client1 > filtered out 198.64.6.229/32 unreachable bird: client1 > filtered out 202.47.30.113/32 unreachable bird: client1 > filtered out 129.250.38.85/32 unreachable bird: client1 > filtered out 198.64.6.151/32 unreachable bird: client1 > filtered out 213.130.47.24/32 unreachable bird: client1 > filtered out 66.129.224.37/32 unreachable bird: client1 > filtered out 207.17.137.34/32 unreachable bird: client1 > filtered out 129.250.38.101/32 unreachable bird: client1 > filtered out 198.64.6.172/32 unreachable bird: client1 > filtered out 203.105.73.118/32 unreachable bird: client1 > filtered out 198.64.72.220/32 unreachable bird: client1: Got UPDATE bird: client1 > filtered out 204.42.111.0/25 unreachable bird: client1 > filtered out 204.42.112.0/24 unreachable bird: client1 > filtered out 204.42.110.40/32 unreachable bird: client1 > filtered out 129.250.0.254/32 unreachable bird: client1 > filtered out 129.250.0.255/32 unreachable bird: client1: Got UPDATE bird: client1: Got END-OF-RIB bird: client1 < added 100.101.1.0/24 unreachable bird: client1 < added 100.101.2.0/24 unreachable bird: client1: Sending UPDATE bird: client1: Sending UPDATE bird: client1: Sending END-OF-RIB bird: client1: Got UPDATE bird: client1: Got UPDATE bird: client1: Got KEEPALIVE bird: client1: Sending KEEPALIVE bird: client1: Got KEEPALIVE bird: client1: Sending KEEPALIVE bird: client1: Got KEEPALIVE bird: client1: Sending KEEPALIVE bird: client1: Got KEEPALIVE bird: client1: Sending KEEPALIVE bird: client1: Got KEEPALIVE bird: client1: Sending KEEPALIVE -- ++ytti

2 3