- Bird-users - Mailing Lists

bird development
by Daniel Wendler 08 Feb '16

08 Feb '16

Hello everybody, the last bird version (1.5.0) was released around 8 month ago and since then, there were no bug fix release or something. On the RIPE 69 "Bird short update" Ondrej mentioned the 1.5 version is the last one of the 1.X releases and shows the future of bird with 2.x in Q1/2015 and final (3.x) in Q3/2015. As we now have Q1/2016 i want to know if there is an updated Roadmap for the bird development? Will there an 1.5.1 release? When could we expect the 2.X or the 3.X release or is the whole development effort actual in the Turris Omnia project? Thanks. -- Mit freundlichen Grüßen --------------------------------- Daniel Wendler

4 3

New Linux Networking + BIRD tutorial
by Hans van Kranenburg 08 Feb '16

08 Feb '16

Hi BIRD people, I'm excited to present some new linux networking tutorials that feature BIRD as routing software used in all examples. The target audience of the tutorials is Linux system/network administrators that are managing a growing network, and need to take the jump into the world of dynamic routing protocols, but don't really know where to start, being scared away, because most of the "Introduction to..." that you can find on the internet wants to learn you cisco, and starts pouring out shitloads of theoretical concepts before just starting to have fun. Well, just see for yourself, it's currently at: https://github.com/knorrie/network-examples/blob/master/README.md Have fun, Hans van Kranenburg

2 1

Re: static default vs bgp default
by Anand Buddhdev 07 Feb '16

07 Feb '16

On 02/02/16 23:23, Angel Lopez Delgado wrote: > Change the preference in your static protocol configuration: > > protocol static { > route 0.0.0.0/0 unreachable; > preference 99; > } Hi everyone, Following Angel's suggestion, I now have the following in bird.conf: protocol static dropall { preference 50; route 0.0.0.0/0 blackhole; } and the following in bird6.conf: protocol static dropall { preference 50; route ::/0 blackhole; } For IPv4, this appears to be working: # ip route show table 10 | fgrep default blackhole default proto bird However, it doesn't appear to have worked for IPv6 (yes, I reloaded bird6): # ip -6 route show table 10 | fgrep default # ip -6 route show table 10 | fgrep ::/0 I even piped the entire output of the "ip -6 route show table 10" command to a pager, and eyeballed the routes. There's no default. But... # birdc6 show route ::/0 BIRD 1.4.5 ready. ::/0 blackhole [dropall 11:19:29] ! (50) Is this a known bug? Or have I misconfigured something? What does the exclamation mean? Regards, Anand

4 4

OSPF and discard some ospf_router_id
by Anton Kiryushkin 05 Feb '16

05 Feb '16

Hello. I have next filters: filter export_OSPF { if net = white_ip2/32 then { ospf_metric2 = 5; print "router_id: ", ospf_router_id, " net: ", net; accept; } if net = white_ip1/32 then { ospf_metric2 = 10; print "router_id: ", ospf_router_id, " net: ", net; accept; } if ospf_router_id = 10.0.0.32 then { reject; } reject; } filter import_OSPF { if ospf_router_id = 10.0.0.32 then { reject; } reject; } And on second server I have another filters: filter export_OSPF { if net = white_ip1/32 then { ospf_metric2 = 5; print "router_id: ", ospf_router_id, " net: ", net; accept; } if net = white_ip2/32 then { ospf_metric2 = 10; print "router_id: ", ospf_router_id, " net: ", net; accept; } if ospf_router_id = 10.0.0.33 then { reject; } reject; } filter import_OSPF { if ospf_router_id = 10.0.0.33 then { reject; } reject; } As I think, on the first server I discard any announce from second server and conversely. But on both servers I see both servers as neighbors. Where I'm wrong? And maybe you suggest me another way for reservation ip on two servers? -- Best regards, Anton Kiryushkin

2 2

Re: static default vs bgp default
by Anand Buddhdev 03 Feb '16

03 Feb '16

On 02/02/16 23:23, Angel Lopez Delgado wrote: Hi Angel, > Change the preference in your static protocol configuration: > > protocol static { > route 0.0.0.0/0 unreachable; > preference 99; > } Thank you for this suggestion! Regards, Anand

1 0

static default vs bgp default
by Anand Buddhdev 03 Feb '16

03 Feb '16

Dear BIRD users, I want to configure bird with a static default like this: protocol static { route 0.0.0.0/0 unreachable; } so that if a more specific route isn't known, packets are discarded. With the same BIRD instance, I want to peer over BGP with multiple peers. However, if any one of these peers provides a default route over BGP, I want it to take precedence over the static. How do I get bird to install the peer-supplied default with a higher weight? Regards, Anand

3 2

BGP Multipath
by Roman Romanyak 01 Feb '16

01 Feb '16

Hello guys, Is BGP Multipath supported in BIRD? Thanks! Roman.

1 0

integration with Fastnetmon
by Neil Morris 01 Feb '16

01 Feb '16

Morning folks, I have just started looking into BIRD for use with Fastnetmon for DDoS mitigation. I see that ExaBGP is aready integrated with Fastnetmon, but was interested to hear from anyone who has used BIRD. thanks in advance Kind Regards, Neil

3 2

bgp path metric
by Rohrmann Sascha 29 Jan '16

29 Jan '16

Hi, I have 2 routers which perform an iBGP peer. Now, every route, which they exchange should get a special metric (e.g: received route from same ASN, route metric= route metric + 100). How am I be able to influence that? I've already tried to check from which AS a route came and preprent (I am not sure if this is the correct keyword btw) it. Here's my filter settings so far: export filter { if bgp_path ~ [= ASN =] then { bgp.path.prepend (ASN,100); accept; } }; I'd be thankful for every help.

1 0

BIRD and ECMP on Linux seems flaky
by Arno Töll 27 Jan '16

27 Jan '16

Hi list, I've been experimenting with bird's ECMP features added to the current git head a while back [1] on my Debian based Linux system. I tried the setup below with git head as of today. I have three Linux routers running with bird. Two I called gw (gateway) one being a frontend. The gateways are configured to establish one BGP session to the frontend each, and advertising fd57::1 and fd57::2 to it. The frontend accepts both advertisement, and exports both to the kernel table. All output below comes from this bird. I configured bird like this: log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; router id 10.3.101.3; # Filters filter kernel_export { if net ~ [ fd57::/64{128,128} ] then accept; reject; } # BGP Filters filter bgp_import { if net ~ [ fd57::/64{128,128} ] then accept; reject; } filter bgp_export { reject; } # Local devices protocol device { scan time 10; } protocol direct { interface "*"; } protocol kernel { import none; #learn; merge paths on; export filter kernel_export; } # BGP peers protocol bgp 'gw1' { description "gw1"; default bgp_local_pref 100; local fc57::3 as 65001; neighbor fc57::1 as 65000; next hop self; import filter bgp_import; export filter bgp_export; hold time 30; error wait time 5, 30; } protocol bgp 'gw2' { description "gw2"; default bgp_local_pref 100; local fc57::3 as 65001; neighbor fc57::2 as 65000; next hop self; import filter bgp_import; export filter bgp_export; hold time 30; error wait time 5, 30; } On the system I have this address configuration: root@debian:~# ip addr show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 64000 qdisc pfifo_fast state UP group default qlen 1000 link/ether 02:01:93:0b:5a:e9 brd ff:ff:ff:ff:ff:ff inet 10.10.216.12/24 brd 10.10.216.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc57::3/64 scope global valid_lft forever preferred_lft forever inet6 fe80::1:93ff:fe0b:5ae9/64 scope link valid_lft forever preferred_lft forever in bird: root@debian:~# birdc6 BIRD 1.5.0 ready. bird> show protocols name proto table state since info device1 Device master up 14:53:54 direct1 Direct master up 14:53:54 kernel1 Kernel master up 14:53:54 static1 Static master up 14:53:54 gw1 BGP master up 14:53:58 Established gw2 BGP master up 14:53:55 Established bird> show route fd57::2/128 via fc57::1 on eth0 [gw1 14:53:58] ! (100) [AS65000i] via fc57::2 on eth0 [gw2 14:53:55] (100) [AS65000i] fd57::1/128 via fc57::1 on eth0 [gw1 14:53:58] ! (100) [AS65000i] via fc57::2 on eth0 [gw2 14:53:55] (100) [AS65000i] fc57::/64 dev eth0 [direct1 14:53:54] * (240) Result being, that the multipath routes are being installed into the kernel routing table as expected once the sessions are up: root@debian:~# ip -6 route show fc57::/64 dev eth0 proto kernel metric 256 fd57::1 via fc57::1 dev eth0 proto bird metric 1024 fd57::1 via fc57::2 dev eth0 proto bird metric 1024 fd57::2 via fc57::1 dev eth0 proto bird metric 1024 fd57::2 via fc57::2 dev eth0 proto bird metric 1024 fe80::/64 dev eth0 proto kernel metric 256 However, after some time, bird seems to confuse itself by the routes it installed and removes the multipath route again. This can be seen again in ip route show: root@debian:~# ip -6 route show fc57::/64 dev eth0 proto kernel metric 256 fd57::1 via fc57::2 dev eth0 proto bird metric 1024 fd57::2 via fc57::2 dev eth0 proto bird metric 1024 fe80::/64 dev eth0 proto kernel metric 256 In bird they are however still received: root@ps:~# birdc6 show route all BIRD 1.5.0 ready. fd57::2/128 via fc57::1 on eth0 [gw1 16:25:25] ! (100) [AS65000i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65000 BGP.next_hop: fc57::1 fe80::1:bdff:feab:7f12 BGP.local_pref: 100 via fc57::2 on eth0 [gw2 16:25:23] (100) [AS65000i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65000 BGP.next_hop: fc57::2 fe80::1:bdff:fe05:64b7 BGP.local_pref: 100 fd57::1/128 via fc57::1 on eth0 [gw1 16:25:25] ! (100) [AS65000i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65000 BGP.next_hop: fc57::1 fe80::1:bdff:feab:7f12 BGP.local_pref: 100 via fc57::2 on eth0 [gw2 16:25:23] (100) [AS65000i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65000 BGP.next_hop: fc57::2 fe80::1:bdff:fe05:64b7 BGP.local_pref: 100 ... In the bird log, with debug output enabled I can see: Jan 11 15:12:46 ps bird6: gw1: Got KEEPALIVE Jan 11 15:12:49 ps bird6: gw2: Got KEEPALIVE Jan 11 15:12:50 ps bird6: gw1: Sending KEEPALIVE Jan 11 15:12:52 ps bird6: gw2: Sending KEEPALIVE Jan 11 15:12:54 ps bird6: device1: Scanning interfaces Jan 11 15:12:54 ps bird6: kernel1: Scanning routing table Jan 11 15:12:54 ps bird6: kernel1: fd57::1/128: will be updated Jan 11 15:12:54 ps bird6: kernel1: fd57::1/128: already seen Jan 11 15:12:54 ps bird6: kernel1: fd57::2/128: will be updated Jan 11 15:12:54 ps bird6: kernel1: fd57::2/128: already seen Jan 11 15:12:54 ps bird6: kernel1: Pruning table master Jan 11 15:12:54 ps bird6: kernel1: fd57::2/128: updating Jan 11 15:12:54 ps bird6: Netlink: File exists Jan 11 15:12:54 ps bird6: kernel1: fd57::1/128: updating Jan 11 15:12:54 ps bird6: Netlink: File exists After a while, the problem fixes itself, both routes are being installed, and then the problem reappears for the next cycle. Is there a way around this, or is this actually a bug? To me this looks like bird was scanning it's own routes and falsely scans only one of them. Experimenting with "import all", "learn" etc. for the kernel protocol seems to make no difference. [1] https://gitlab.labs.nic.cz/labs/bird/commit/8d9eef17713a9b38cd42bd59c4ce76c… -- Arno Töll GnuPG Key-ID: 0x9D80F36D

4 5