November 2018 - Bird-users

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