- Bird-users - Mailing Lists

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

Bird 2.0.2
by Шарпаев Антон 11 Sep '18

11 Sep '18

BGP direct not working with Bird 2.0.2. Only multihop working. When I try to use direct mode bird didn`t listen tcp port and don`t send packets to remote

2 1

generate default route and export to kernel if remote peer is up
by Nikola Mitev 08 Sep '18

08 Sep '18

Hi, I have a setup of ISP1 -- R1 -- LAN -- R2 -- ISP2 with BGP peerings from R1 to ISP1 and R2 to ISP2 Some hosts on the LAN have R1 as primary gateway, others R2 to distribute the load between the ISPs. I want to add a default route to the kernel on each router but only if the remote peer is up. The remote peer does not respond to BFD so that's not an option. Once both routers have a conditionally defined default route for their ISP, it should be easy to propagate that to each other with increased metric as a backup route. I am assuming here that if R1 has a default through R2 and ISP1 is down, R1 will respond with an ICMP redirect to any requests from hosts that need to be routed out of LAN. I searched for a recipe that would fit the above but found nothing yet, hoping someone here can help :) Nik

2 4

AS112 using BIRD
by Diarmuid O Briain 07 Sep '18

07 Sep '18

Hi all, Looking for a bit of a sanity check here. I established an AS112 Server in my testbed using BIRD as the router. I setup a dummy interface on the AS112 server (bs) for all the subnets with an interface name that starts with 'as112_'. I set up the bird and bird6 configuration files identically except for the prefix 'set allnets' and or course the IPv4 remote addresses in bird.conf and IPv6 addresses in bird6.conf. What is puzzling me is that in an ISP router I can see the IPv4 'allnets' in both the router BGP and IP routes tables but I cannot see the IPv6 'allnets' in the BGP and IPv6 routes tables. regards, Diarmuid 3: as112_br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 46:c1:5f:cd:9c:8d brd ff:ff:ff:ff:ff:ff inet 192.175.48.1/24 brd 192.175.48.255 scope global as112_br1 valid_lft forever preferred_lft forever inet 192.31.196.1/24 brd 192.31.196.255 scope global as112_br1 valid_lft forever preferred_lft forever inet 192.175.48.6/24 brd 192.175.48.255 scope global secondary as112_br1 valid_lft forever preferred_lft forever inet 192.175.48.42/24 brd 192.175.48.255 scope global secondary as112_br1 valid_lft forever preferred_lft forever inet6 2001:4:112::1/128 scope global valid_lft forever preferred_lft forever inet6 2620:4f:8000::42/128 scope global valid_lft forever preferred_lft forever inet6 2620:4f:8000::6/128 scope global valid_lft forever preferred_lft forever inet6 2620:4f:8000::1/128 scope global valid_lft forever preferred_lft forever inet6 fe80::44c1:5fff:fecd:9c8d/64 scope link valid_lft forever preferred_lft forever ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ root@bs:/etc/bird# cat bird.conf router id 199.9.9.204; filter as112 prefix set allnet; { allnet = [ 192.175.48.0/24, 192.31.196.0/24 ]; if ! (net ~ allnet) then reject; accept; } protocol device { } protocol direct { interface "as112_*"; } protocol kernel { learn; metric 64; import all; export all; } template bgp PEERS { local as 112; hold time 30; startup hold time 30; connect retry time 120; connect delay time 5; error forget time 0; export filter as112; } protocol bgp as5222 from PEERS { neighbor 199.9.9.22 as 5222; } protocol bgp as5333 from PEERS { neighbor 199.9.9.33 as 5333; } protocol bgp as5111 from PEERS { neighbor 199.9.9.11 as 5111; } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ root@bs:/etc/bird# cat bird6.conf router id 199.9.9.204; filter as112 prefix set allnet; { allnet = [ 2620:4f:8000::/48, 2001:4:112::/48 ]; if ! (net ~ allnet) then reject; accept; } protocol device { } protocol direct { interface "as112_*"; } protocol kernel { learn; metric 64; import all; export all; } template bgp PEERS { local as 112; hold time 30; startup hold time 30; connect retry time 120; connect delay time 5; error forget time 0; export filter as112; } protocol bgp as5222 from PEERS { neighbor 2a99:9:9::22 as 5222; } protocol bgp as5333 from PEERS { neighbor 2a99:9:9::33 as 5333; } protocol bgp as5111 from PEERS { neighbor 2a99:9:9::11 as 5111; } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ISP1_RTR#show bgp ipv4 unicast BGP table version is 22, local router ID is 200.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.31.196.0 199.9.9.204 0 112 i *> 192.175.48.0 199.9.9.204 0 112 i *> 199.1.1.0 0.0.0.0 0 32768 i *> 199.2.2.0 199.9.9.22 0 0 5999 5222 i *> 199.3.3.0 199.9.9.33 0 0 5999 5333 i ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ISP1_RTR# show ip route C 199.9.9.0/24 is directly connected, FastEthernet0/0 B 192.31.196.0/24 [20/0] via 199.9.9.204, 00:36:07 200.1.1.0/32 is subnetted, 1 subnets C 200.1.1.1 is directly connected, Loopback0 B 199.3.3.0/24 [20/0] via 199.9.9.33, 00:36:10 B 199.2.2.0/24 [20/0] via 199.9.9.22, 00:35:47 C 199.1.1.0/24 is directly connected, FastEthernet0/1 B 192.175.48.0/24 [20/0] via 199.9.9.204, 00:36:07 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ISP1_RTR# show bgp ipv6 unicast BGP table version is 8, local router ID is 200.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 2A99:1:1::/48 :: 0 32768 i *> 2A99:2:2::/48 2A99:9:9::22 0 0 5999 5222 i *> 2A99:3:3::/48 2A99:9:9::33 0 0 5999 5333 i ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ISP1_RTR# show ipv6 route C 2A99:1:1::/48 [0/0] via ::, FastEthernet0/1 L 2A99:1:1::1/128 [0/0] via ::, FastEthernet0/1 B 2A99:2:2::/48 [20/0] via FE80::21E:BEFF:FE17:EB9A, FastEthernet0/0 B 2A99:3:3::/48 [20/0] via FE80::C671:FEFF:FE10:FE00, FastEthernet0/0 C 2A99:9:9::/48 [0/0] via ::, FastEthernet0/0 L 2A99:9:9::11/128 [0/0] via ::, FastEthernet0/0 L FE80::/10 [0/0] via ::, Null0 L FF00::/8 [0/0] via ::, Null0 -- *Irish by birth, located in Uganda but Munster by the grace of God.*

2 1

Malformed AS Path
by Ajai Kumar 05 Sep '18

05 Sep '18

Dear All, One customer is using Huawei equipment and bgp is not coming up with Bird RS.We are getting error of Malformed AS Path. They don not want to use *undo check-first-as *for resolving this problem as it is global command and may create loop as referred at http://support.huawei.com/hedex/pages/EDOC1000127118DEG0629M/03/EDOC1000127… Is there any other way to resolve this problem. Looking forward for your support pls. Regards, Ajai Kumar -- Please don't print this email unless you really need to. This will preserve trees on our planet.

1 0

BIRD BGP Attributes Function Info
by Isaac HO 05 Sep '18

05 Sep '18

Hi Support, May I know where i can find the details manual of BIRD BGP Attributes? Ex. the website have introduce bgp_path and bgp_community only... can't find the information about bgp_path.xxx and bgp_community.xxx Thanks, Isaac

1 0

RE: Adding a Remote looking Glass to our IXP Manager
by Anibe Onuche 04 Sep '18

04 Sep '18

Sorry, My most sincere apologies Got my mailing address wrong. This was supposed to be posted on the ixp manager mailing list. Sorry. Thanks. Anibe From: Anibe Onuche <a.onuche(a)ixp.net.ng> Sent: Tuesday, September 4, 2018 2:23 PM To: 'bird-users(a)network.cz' <bird-users(a)network.cz> Subject: Adding a Remote looking Glass to our IXP Manager Hello All, I have a looking glass installed in a remote server separate from my IXP Manager local host. Is it possible to implement the looking glass as an addition on my IXP manager? The same applies to my birdseye configuration. Can someone help me out. Thanks. Warm Regards, -- A.o

1 0

Adding a Remote looking Glass to our IXP Manager
by Anibe Onuche 04 Sep '18

04 Sep '18

Hello All, I have a looking glass installed in a remote server separate from my IXP Manager local host. Is it possible to implement the looking glass as an addition on my IXP manager? The same applies to my birdseye configuration. Can someone help me out. Thanks. Warm Regards, -- A.o

1 0

Problem to receive an announcement in BIRD.
by Marcio 02 Sep '18

02 Sep '18

Dear, I have a topology with many ASes using BIRD except one. This AS(called SDNRTR) is using a SDN technology and it is programmed to announce some prefixes. When it announces, some of it neighbors(BIRD ASes) are rejecting the announcement. Follow the line in BIRD logs. 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Got UPDATE 2018-09-01 21:21:08.000 <TRACE> SDNRTR > added [best] 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> kernel1 < replaced 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> SDNRTR < rejected by protocol 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> R8 < replaced 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> R8: Sending UPDATE 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Got UPDATE 2018-09-01 21:21:08.000 <TRACE> SDNRTR > removed [replaced] 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> kernel1 < replaced 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> SDNRTR < added 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> R8 < rejected by protocol 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> R8 < removed 10.3.1.0/24 unicast 2018-09-01 21:21:08.000 <TRACE> SDNRTR: Sending UPDATE 2018-09-01 21:21:08.000 <TRACE> R8: Sending UPDATE 2018-09-01 21:21:08.001 <TRACE> R8: Got UPDATE 2018-09-01 21:21:08.001 <TRACE> R8 > removed [sole] 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> kernel1 < removed 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> SDNRTR < removed 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> SDNRTR: Sending UPDATE 2018-09-01 21:21:08.001 <TRACE> R8: Got UPDATE 2018-09-01 21:21:08.001 <TRACE> R8 > added [best] 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> kernel1 < added 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> SDNRTR < added 10.3.1.0/24 unicast 2018-09-01 21:21:08.001 <TRACE> R8 < rejected by protocol 10.3.1.0/24 unicast It is showing "rejected by protocol". Do you know what it means? How could i solve this trouble?

2 6