July 2020 - Bird-users - Mailing Lists

BIRD on physical / virtual server.
by Mike Neo 10 Jul '20

10 Jul '20

Hi, what is your experience with installing bird on virtual server (ESXi)? Is there any limitation of this kind of deployment for example problems with performance etc.? Regards, Mike

3 4

Check filtered RPKI routes
by Fabiano D'Agostino 10 Jul '20

10 Jul '20

Hi all, is there a way to check quickly filtered RPKI routes? I can check the syslog, but if I delete the log I think the only way to check filtered routes (having import keep filtered enabled) is: show route table table_name all filtered but having a lot of tables it is not easy to handle this command for every single table. Thanks, Fabiano

1 0

Re: Pointers please - OSPFv3 vs Cisco IOS XR
by Elmar K. Bins 07 Jul '20

07 Jul '20

Hi Ondrej, sorry, I missed your response (T., thank you for forwarding): >> I am very certain somebody has experienced similar issues and solved them; I >> did not find any pointers - please throw them at me. If this is new or unsolved, >> please help me forward, I can get more output, naturally. > > Hi > > It might be useful if you enable 'debug all' for OSPFv3 in BIRD. Alright...sorry, I thought I had "all" on, but apparently didn't. Here's the output from that, shortened and edited to protect the innocent. (If you require the full output, I'll email it to you) Thank you for taking a look at this, Elmar. ======================================================================================= 2020-06-03 12:30:13.801 <TRACE> ospf2: HELLO packet received from nbr <router-1> on igb0 2020-06-03 12:30:16.899 <TRACE> ospf2: DBDES packet received from nbr <router-1> on igb0 2020-06-03 12:30:16.899 <TRACE> ospf2: length 28 2020-06-03 12:30:16.899 <TRACE> ospf2: router <router-1> 2020-06-03 12:30:16.899 <TRACE> ospf2: mtu 1500 2020-06-03 12:30:16.899 <TRACE> ospf2: imms I M MS 2020-06-03 12:30:16.899 <TRACE> ospf2: ddseq 147850133 2020-06-03 12:30:16.899 <TRACE> ospf2: Neighbor <router-1> on igb0 changed state from ExStart to Exchange 2020-06-03 12:30:16.899 <TRACE> ospf2: DBDES packet sent to nbr <router-1> on igb0 2020-06-03 12:30:16.899 <TRACE> ospf2: length 108 2020-06-03 12:30:16.899 <TRACE> ospf2: router <bird-ip> 2020-06-03 12:30:16.899 <TRACE> ospf2: mtu 1500 2020-06-03 12:30:16.899 <TRACE> ospf2: imms 2020-06-03 12:30:16.899 <TRACE> ospf2: ddseq 147850133 (a handful of LSAs) 2020-06-03 12:30:16.901 <TRACE> ospf2: DBDES packet received from nbr <router-1> on igb0 2020-06-03 12:30:16.901 <TRACE> ospf2: length 1228 2020-06-03 12:30:16.901 <TRACE> ospf2: router <router-1> 2020-06-03 12:30:16.901 <TRACE> ospf2: mtu 1500 2020-06-03 12:30:16.901 <TRACE> ospf2: imms M MS 2020-06-03 12:30:16.901 <TRACE> ospf2: ddseq 147850134 (more LSAs) 2020-06-03 12:30:16.901 <TRACE> ospf2: DBDES packet sent to nbr <router-1> on igb0 2020-06-03 12:30:16.901 <TRACE> ospf2: length 28 2020-06-03 12:30:16.901 <TRACE> ospf2: router <bird-ip> 2020-06-03 12:30:16.901 <TRACE> ospf2: mtu 1500 2020-06-03 12:30:16.901 <TRACE> ospf2: imms 2020-06-03 12:30:16.901 <TRACE> ospf2: ddseq 147850134 2020-06-03 12:30:16.903 <TRACE> ospf2: LSREQ packet sent to nbr <router-1> on igb0 2020-06-03 12:30:16.903 <TRACE> ospf2: length 736 2020-06-03 12:30:16.903 <TRACE> ospf2: router <bird-ip> (some LSRs) 2020-06-03 12:30:16.906 <TRACE> ospf2: LSREQ packet received from nbr <router-1> on igb0 2020-06-03 12:30:16.906 <TRACE> ospf2: length 52 2020-06-03 12:30:16.906 <TRACE> ospf2: router <router-1> (more LSRs) 2020-06-03 12:30:16.906 <TRACE> ospf2: LSUPD packet sent to nbr <router-1> on igb0 2020-06-03 12:30:16.906 <TRACE> ospf2: length 144 2020-06-03 12:30:16.906 <TRACE> ospf2: router <bird-ip> (some LSAs) 2020-06-03 12:30:16.906 <TRACE> ospf2: DBDES packet received from nbr <router-1> on igb0 2020-06-03 12:30:16.906 <TRACE> ospf2: length 28 2020-06-03 12:30:16.906 <TRACE> ospf2: router <router-1> 2020-06-03 12:30:16.906 <TRACE> ospf2: mtu 1500 2020-06-03 12:30:16.906 <TRACE> ospf2: imms I M MS 2020-06-03 12:30:16.906 <TRACE> ospf2: ddseq 147850135 2020-06-03 12:30:16.906 <RMT> ospf2: Bad DBDES packet from nbr <router-1> on igb0 - I-bit mismatch (7) =======================================================================================

3 5

Minor usability enhancement for birdc - show hostname
by Tim Small 04 Jul '20

04 Jul '20

Hi, I'm finding Bird very useful, thanks! I wondered if it might be useful to show the hostname in the bird prompt? e.g. instead of: bird> Something like: testlab1 bird> ... would spare users the potential frustration or downtime of operating on the wrong bird instance. I couldn't see a way of doing this, but would be happy to submit a patch (to make this configurable or otherwise) if that would be useful? Thanks! Tim.

3 2

Kernel protocol and multiple routes
by Magnus Löfqvist 04 Jul '20

04 Jul '20

Hi, Im running bird 1.6.6 on a openwrt device, having two internet connections (one over 4G and one over ethernet). The main routing table : default via 10.70.69.193 dev wwan0 proto static src 10.70.69.192 default via 10.3.5.1 dev eth1 proto static src 10.3.5.129 metric 10 10.3.5.0/24 dev eth1 proto static scope link metric 10 10.3.5.1 dev eth1 proto static scope link src 10.3.5.129 metric 10 10.70.69.128/25 dev wwan0 proto kernel scope link src 10.70.69.192 10.70.69.193 dev wwan0 proto static scope link src 10.70.69.192 As you see I get the default gateway over 4G as primary (lowest metric), and that are by design. I want to use bird to import the default gateways and pipe them to two different tables. Relevant Config: filter export_wan { if proto = "krn_main" then { if ifname = "wwan0" then { if (net = 0.0.0.0/0) then { accept; } } } reject; } filter export_wan2 { if proto = "krn_main" then { if ifname = "eth1" then { if (net = 0.0.0.0/0) then { accept; } } } reject; } protocol kernel krn_main { learn; import all; scan time 5; kernel table 254; merge path yes; } protocol kernel krn_wan { learn; import none; export all; kernel table 200; scan time 5; table wan; } protocol kernel krn_wan2 { learn; import none; export all; kernel table 200; scan time 5; table wan2; } protocol pipe pipe_wan { peer table wan; export filter export_wan; import all; } protocol pipe pipe_wan2 { peer table wan2; export filter export_wan2; import all; } # birdc4 show route 0.0.0.0/0 all protocol krn_main BIRD 1.6.6 ready. 0.0.0.0/0 via 10.70.69.193 on wwan0 [krn_main 2020-07-03] (10) Type: inherit unicast univ Kernel.source: 4 Kernel.metric: 0 Kernel.prefsrc: 10.70.69.192 As you see Im only get the route for 4G interface (wwan0) and not for the ethernet (eth1). Why is that, and what can be done to fix it? / Magnus Sent from Nine<http://www.9folders.com/>

1 0

Bird 2 for CentOS/EPEL 6?
by Tim Meusel 02 Jul '20

02 Jul '20

Hi people, thanks for the great software! I'm happily using Bird 2 on multiple CentOS 7 nodes. Sadly I now need to rollout BGP to some CentOS 6 boxes :sadface:. I noticed that ftp://bird.network.cz/pub/bird/centos/ only contains CentOS 7 packages, and EPEL 6 only has Bird 1.6.8. However I wanted to ask if Bird 2 would work on CentOS 6? Would Bird itself compile but dependencies are outdated/missing? Cheers, Tim

3 3