- Bird-users - Mailing Lists

BIRD 2.0.2 segfaulting
by Clemens Schrimpe 06 Nov '18

06 Nov '18

Hello - just wanted to report a little (easily reproducable) problem: I’m experimenting with BIRD 2.0.2 on a lab-router (Ubiquiti Edgerouter, MIPS platform) and RPKI. In my attempts to examine ROA tables more closely I entered „show route table r4 all“ into birdc and bird immediately segfaulted and died. Is there any „official“ way to examine the contents of ROA tables other than „eval roa_check(r4, 186.255.72.0/24, 204777)“? I would have assumed „show route table r4 all 186.255.72.0/24“ or something like that would work, but it doesn’t (gives empty output). At least „show route table r4 count“ gives useful information, though. Thanks, Clemens

3 6

(Re)export unreachable routes via BGP.
by Grant Taylor 05 Nov '18

05 Nov '18

Is it possible to (re)export unreachable routes via BGP? I have established a pair of BGP neighbor sessions with Team Cymru Route Servers, both of which are receiving unreachable prefixes, namely bogons, like they should be. I would like to (re)export said prefixes to a different machine that is not able to form a BGP neighbor session with Team Cymru (for various reasons). All attempts thus far have resulted in the BGP neighbor session with the 3rd test machine not (re)exporting any unreachable routes. I can (re)export other routes without a problem. It looks to me like BGP is rejecting the the routes (I think) because they are unreachable. "show route table bogons" works as expected, and shows the routes received via both of the BGP neighbor sessions with the Team Cymru Route Servers. Similarly, I can see the unreachable routes in the proper table from Linux. Thank you in advance for any help / enlightenment that you can provide. --8<-- bird> show protocols all grant name proto table state since info grant BGP bogons up 21:12 Established Description: Feed to Grant at home Preference: 100 Input filter: REJECT Output filter: ACCEPT 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: 3031 3031 0 --- 0 Export withdraws: 0 --- --- --- 0 -->8-- --8<-- filter cymru_bogons_import { bgp_community.add((REDACTED,888)); #dest = RTD_BLACKHOLE; accept; } filter cymru_bogons_export { reject; } protocol bgp cymru1 { description "Team Cymru Bogons Route Server #1"; import filter cymru_bogons_import; #export filter cymru_bogons_export; #import all; export none; multihop 255; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } protocol bgp cymru2 { description "Team Cymru Bogons Route Server #2"; import filter cymru_bogons_import; #export filter cymru_bogons_export; #import all; export none; multihop 255; #password "FIXME"; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } protocol bgp grant { description "Feed to Grant at home"; import none; export all; multihop 255; local as REDACTED; neighbor REDACTED as REDACTED; source address REDACTED; table bogons; } -->8-- -- Grant. . . . unix || die

2 3

vrf configuration with same addresses
by Semion Lisyansky 05 Nov '18

05 Nov '18

Hi All, Tried to configure vrf with same own and peer addresses as in global. When I ping in vrf, packets go in and out via correct interfaces, but bird bgp sessions are constantly flapping. Only one session to peer with same address exists at each moment As a w/a tried to configure interface per session, but this did not helped. Here is my partial configuration: protocol device { scan time 2; # Scan interfaces every 2 seconds } protocol direct { interface "br*"; # bridge interfaces interface "swp*"; # router ports interface "bond*"; # Disable by default ipv4; # Connect to default IPv4 table ipv6; # ... and to default IPv6 table } protocol kernel { ipv4 { # Connect protocol to IPv4 table by channel table master4; # Default IPv4 table is master4 import none; # Import to table, default is import all export all; # Export to protocol. default is export none }; learn on; # Learn alien routes from the kernel merge paths yes; } protocol bgp bgp3411 { local as 65001; bfd yes; neighbor 191.34.1.3 as 65034; # interface "swp2"; ipv4 { import all; export all; }; } protocol bgp bgp3412 { local as 65001; bfd yes; neighbor 192.34.1.3 as 65034; # interface "swp1"; ipv4 { import all; export all; }; } ipv4 table table_vrf01; protocol kernel kernel_vrf01 { vrf "vrf01"; kernel table 101; scan time 2; ipv4 { table table_vrf01; import none; # Default is import all export all; # Default is export none }; merge paths yes; learn on; # Learn all alien routes from the kernel } protocol direct direct_vrf01 { vrf "vrf01"; ipv4 { table table_vrf01; }; interface "swp7.101"; interface "swp1.201"; interface "swp2.301"; interface "vrf01"; } protocol static static_vrf01 { vrf "vrf01"; ipv4 { table table_vrf01; }; } protocol bgp bgp_vrf01_n1 { vrf "vrf01"; local as 65001; graceful restart; neighbor 191.34.1.3 as 65034; ipv4 { table table_vrf01; import none; export none; }; } protocol bgp bgp_vrf01_n2 { vrf "vrf01"; local as 65001; graceful restart; neighbor 192.34.1.3 as 65034; ipv4 { table table_vrf01; import none; export none; }; } ip -br link show type vrf vrf01 UP fe:58:94:d2:d8:ee <NOARP,MASTER,UP,LOWER_UP> vrf02 UP 42:2d:8f:bd:87:9f <NOARP,MASTER,UP,LOWER_UP> (mlnx)root@bdg-crf-01:~# ip route show vrf vrf01 172.1.7.0/24 dev swp7.101 proto kernel scope link src 172.1.7.1 offload 191.34.1.2/31 dev swp2.301 proto kernel scope link src 191.34.1.2 offload 192.34.1.2/31 dev swp1.201 proto kernel scope link src 192.34.1.2 offload (mlnx)root@bdg-crf-01:~# ip route show table 101 broadcast 172.1.7.0 dev swp7.101 proto kernel scope link src 172.1.7.1 172.1.7.0/24 dev swp7.101 proto kernel scope link src 172.1.7.1 offload local 172.1.7.1 dev swp7.101 proto kernel scope host src 172.1.7.1 broadcast 172.1.7.255 dev swp7.101 proto kernel scope link src 172.1.7.1 local 191.34.1.2 dev swp2.301 proto kernel scope host src 191.34.1.2 191.34.1.2/31 dev swp2.301 proto kernel scope link src 191.34.1.2 offload local 192.34.1.2 dev swp1.201 proto kernel scope host src 192.34.1.2 192.34.1.2/31 dev swp1.201 proto kernel scope link src 192.34.1.2 offload -- Semion Lisyansky

3 11

Add two bfd session with same dest ip and different local ip, can it work?
by bbk bbk 05 Nov '18

05 Nov '18

hi, Can the bird add two BFD sessions with same destination ip and different local ip? My testing is only one session can be added as if.

2 1

bird logging
by Alexander Zubkov 29 Oct '18

29 Oct '18

Hi, When I specify relative log file path, the file is created relative to the current working directory. But for the include directive relative path are applied relative to the config file. Probably it would be better to have a consistent path resolution? I also suppose it could have been done intentionally. But I did not find description of this behaviour in the documentation. And I did not find anything on this question with google.

2 1

[PATCH 2.x branch] BGP: Bind listen socket to VRF
by Alexander Zubkov 26 Oct '18

26 Oct '18

BGP protocol could not bind to the interface in a VRF even if the vrf option was specified in the configuration. Signed-off-by: Alexander Zubkov <green(a)qrator.net> --- proto/bgp/bgp.c | 1 + 1 file changed, 1 insertion(+) diff --git a/proto/bgp/bgp.c b/proto/bgp/bgp.c index e7479df..3aa35ae 100644 --- a/proto/bgp/bgp.c +++ b/proto/bgp/bgp.c @@ -168,6 +168,7 @@ bgp_open(struct bgp_proto *p) sock *sk = sk_new(proto_pool); sk->type = SK_TCP_PASSIVE; + sk->vrf = p->p.vrf; sk->ttl = 255; sk->saddr = addr; sk->sport = port; -- 1.9.1

2 4

segfault in bird v1.6.4
by Alexander Velkov 26 Oct '18

26 Oct '18

Hello bird-team, I have a bird v1.6.4. configuration that works fine. A certain set of actions leads to a segfault and a crash of the bird binary. I have configured and built bird 1.6.4. with IPv6 support that runs on a box with a i686 linux with kernel v4.14.75. My bird configuration: ### bird6.conf: protocol device { scan time 10; } protocol direct C_main { interface "*"; preference 255; check link; } protocol kernel K_main { preference 255; scan time 20; export all; learn; } include "*.conff"; ### ospfv3.conff in the same directory: debug protocols all; log syslog { info, remote, warning, error, auth, fatal, bug }; protocol ospf O_main { preference 145; instance id 0; area 172.16.0.0 { interface "vti0" { dead 120; hello 30; cost 1; priority 1; type pointopoint; neighbors { fe80::e68:3ff:fe26:5130; }; }; interface "eth1" { dead 40; hello 10; cost 1; priority 1; type broadcast; stub yes; }; }; import filter { accept; }; export filter { reject; }; } ### The following actions lead to a crash of bird6: EEPD[~]# /sbin/bird6 -P /var/run/bird6.pid -c /var/etc/bird6/bird6.conf Oct 24 14:23:08 EEPD info bird6 [ 4684]: Started EEPD[~]# ps | grep bird6 4930 root 1500 S /sbin/bird6 -P /var/run/bird6.pid -c /var/etc/bird6/bird6.conf 4932 root 1284 S grep bird6 EEPD[~]# EEPD[~]# ip -6 link add vti0 type vti6 local fd00::38 remote fd00::1b ikey 2 okey 2; EEPD[~]# ip -6 link set vti0 up; EEPD[~]# ifconfig vti0 mtu 1422 Oct 24 14:23:17 EEPD err bird6 [ 4684]: KIF: Received address message for unknown interface 33 Oct 24 14:23:20 EEPD err bird6 [ 4684]: O_main: Socket error on vti0: Invalid argument Oct 24 14:23:20 EEPD info kernel: [ 4684]: segfault at 58e ip b7eed103 sp bf9acad8 error 4 in libuClibc-1.0.30.so[b7ebd000+72000] EEPD[~]# EEPD[~]# ps | grep bird6 4988 root 1284 S grep bird6 EEPD[~]# ### Further testing - bird does NOT crash if the contents of bird6.conf and ospfv3.conf are placed in a single file without inclusion. - bird does NOT crash if the call 'ifconfig vti0 mtu 1422' is executed before 'ip -6 link set vti0 up'. Hope this information helps. Best Regards Alex

3 3

BIRD 2.0.2 VPNv4 RD Filter
by Hombach, Tobias 25 Oct '18

25 Oct '18

Hi, Is it possible in current BIRD 2.0.2 release to filter (more dynamically) VPNv4 prefixes based on RD? In our scenario, we want to use BIRD to connect large VPNv4 landscapes and want to filter prefixes based on RD on Route Server ingress. I can extract RD from VPNv4 prefix with special operator '.rd' filter vpnv4_ingress { if (net.rd = 5000:200) then accept; reject; } This is working but I don't want 1x if-statement per RD as we have lots of RD's. Any ranges or wildcards are not allowed. Something like '5000:200..299' does not work. Or '5000:*' also does not work. I tried to create a constant for a VPNv4 prefix to use it in a filter: function some_function() prefix set test; { test = [ 0:5000:200 10.0.0.0/24 ]; } Also not allowed. Creating a constant of data type 'vpnrd' did not work. Then I tried to handle the output of 'net.rd' as string to maybe use shell pattern. filter vpnv4_ingress string test; { test = "5000:20?"; if net.rd ~ test then accept; reject; } Results in error: "<ERR> filters, line 90: ~ applied on unknown type pair". Changing the if-statement to 'if net.rd = test then accept;' does work w/o error but all prefixes are filtered. The shell pattern is not working. I guess the output of 'net.rd' is not a string. I also cannot save 'net.rd' output in a string variable. Last but not least. I have found a undocumented function 'format()'. This function seems to return a string and shell patterns work. I guess the function should not be used in production so I just used it for testing. define test = "5000:20?"; filter vpnv4_ingress { if format(net.rd) ~ test then accept; reject; } <TRACE> some-router > added [best] 5000:200 200.200.200.0/24 unicast But this works only once. As soon as I run 'configure' in BIRD client, BIRD does crash. <INFO> Reconfiguring <BUG> Unknown instruction 70 in same (F) Long story short. Is there a best practice to filter VPNv4 based on RD? Or anything on the roadmap? Filtering on RT with Communities works fine but does not fit our purpose. Thanks in advance! Regards Tobias

2 2

Tell BGP Partner to prefer a specific bgp session
by Kevin Schmitz 20 Oct '18

20 Oct '18

Hi guys, how i can tell my bgp partner where to route the traffic? I have two sessions to my BGP partner and announce the same ip-range. Is there a way to do it from my site? Thanks in advance

2 1

bgp sorted tables
by Milen Bogunski 18 Oct '18

18 Oct '18

Hello, I'm trying to use sorted table feature (despite it is described as a little bit slower) I'm trying on 1.6.3, 1.6.4 with table master sorted; also on 2.0.2 format ipv4 table master4 sorted; But is does not seem to work, when show route from birdc routes are still in random order. anyone help on that, is this sorting still working ? Thanks in advance. Milen Bogunski

3 6