- Bird-users - Mailing Lists

next-hop announcement/withdrawal process
by Pavlos Parissis 04 Aug '14

04 Aug '14

Hi, I am building a solution where I have N HAProxy servers which have BGP and BFD sessions with 2 upstream routers. Bird runs on all HAProxy servers and announces the same prefixes via BGP. I am using ECMP on upstream routes to balance incoming traffic to these HAProxy servers, which balance traffic to N backend servers. I need to advertise/withdraw several IP prefixes within the same range (192.168.200.0/24) based on the health of a service, in this case the frontend on HAProxy. These IPs are assigned only the loopback interface. The problem I am facing is that when I adjust a filter in order to withdraw the route, all routes are withdrawn and the remaining are announced again. According to the doc if a reload on bird brings a new configuration for a protocol, that protocol will be restarted. So, it is expected behavior. Below is the log[1] after I removed '192.168.200.1' from prefix set anycast_prefixes in loopback_ACL filter and reloaded bird. I was monitoring BGP protocols in a loop running bird show protocols all "bgp8" and saw that 'export updates' counter was increased from 2 to 3 and 'export withdraws' counter was increased from 0 to 2. Is there a way to withdraw to a route from a list without effecting the rest routes from the list? The only way I have found so far, it was by removing the specific IP from the loopback interface. But, this solution prevents a reload/restart on HAProxy as it can't bind anymore to the socket Cheers, Pavlos [1] 23:37:52 <INFO> Reconfiguration requested by SIGHUP 23:37:52 <INFO> Reconfiguring 23:37:52 <TRACE> direct1: Reconfigured 23:37:52 <INFO> Reloading protocol direct1 23:37:52 <INFO> Restarting protocol direct1 23:37:52 <TRACE> direct1: Shutting down 23:37:52 <TRACE> direct1: State changed to flush 23:37:52 <TRACE> bgp_peer1: Reconfigured 23:37:52 <TRACE> bgp_peer2: Reconfigured 23:37:52 <INFO> Reconfigured 23:37:52 <TRACE> direct1 > removed [sole] 192.168.200.1/32 dev lo 23:37:52 <TRACE> direct1 > removed [sole] 192.168.200.2/32 dev lo 23:37:52 <TRACE> direct1: State changed to down 23:37:52 <TRACE> direct1: Starting 23:37:52 <TRACE> direct1: Connected to table master 23:37:52 <TRACE> direct1: State changed to feed 23:37:52 <TRACE> direct1 < primary address 192.168.200.1/32 on interface lo added 23:37:52 <TRACE> direct1 > filtered out 192.168.200.1/32 dev lo 23:37:52 <TRACE> direct1 < secondary address 127.0.0.0/8 on interface lo added 23:37:52 <TRACE> direct1 < secondary address 192.168.200.2/32 on interface lo added 23:37:52 <TRACE> direct1 > added [best] 192.168.200.2/32 dev lo 23:37:52 <TRACE> bgp_peer2 < filtered out 192.168.200.2/32 dev lo 23:37:52 <TRACE> bgp_peer1 < filtered out 192.168.200.2/32 dev lo 23:37:52 <TRACE> direct1 < primary address 192.168.80.0/20 on interface eth0 added 23:37:52 <TRACE> direct1: State changed to up 23:37:54 <TRACE> bgp_peer2: Sending KEEPALIVE 23:37:54 <TRACE> bgp_peer1: Sending KEEPALIVE 23:37:54 <TRACE> bgp_peer2: Got KEEPALIVE 23:37:56 <TRACE> bgp_peer1: Got KEEPALIVE bird.conf # Override router ID router id 192.168.88.194; # Listens only on eth0's IP listen bgp address 192.168.88.194; filter loopback_ACL prefix set anycast_prefixes; { anycast_prefixes = [ 192.168.200.1/32, 192.168.200.2/32 ]; if net ~ anycast_prefixes then accept; else reject; } filter anycast_range { if net ~ [ 192.168.200.0/24 ] then accept; else reject; } protocol direct { interface "lo"; debug all; import filter loopback_ACL; export none; } protocol kernel kernel1 { disabled yes; } protocol device { scan time 10; # TODO do I need this? } protocol static { disabled yes; } protocol bfd { interface "eth0" { min rx interval 500 ms; min tx interval 500 ms; idle tx interval 1000 ms; multiplier 3; }; } template bgp BGP_PEERS { bfd on; debug all; import none; export filter anycast_range; direct; hold time 30; startup hold time 240; connect retry time 120; keepalive time 10; start delay time 5; error wait time 60, 300; error forget time 300; disable after error off; next hop self; path metric 1; default bgp_med 0; default bgp_local_pref 0; } protocol bgp bgp_peer1 from BGP_PEERS { disabled no; description "My-BGP-Peer1"; local as 46111; neighbor 192.168.95.252 as 46111; source address 192.168.88.194; } protocol bgp bgp_peer2 from BGP_PEERS { disabled no; description "My-BGP-Peer2"; local as 46111; neighbor 192.168.95.253 as 46111; source address 192.168.88.194; }

5 8

Allow configuration of BGP sessions to non standard ports.
by João Taveira Araújo 02 Aug '14

02 Aug '14

Hi, The current configuration options assume that one or both BGP peers will be listening on port 179. As a result it becomes impossible to configure BIRD instances to talk to each other if both are running BGP on non standard ports, or if a single instance is on a non standard port and running in passive mode. I've attached a patch which I think does the trick, allowing the user to specify a 'neighbor port <portnum>;' option, but I'm not that familiar with the codebase so I might be missing something. If the patch is not appropriate in its current form, please consider this a feature request for future versions. Thanks, Joao.

1 0

Prefix count limit?
by Tom van Leeuwen 31 Jul '14

31 Jul '14

Hi everyone, I got an announcement from my iptransit provider stating the ipv4 routing table size has now exceeded 500k routes, so I thought lets check if bird is able to handle this and actually find out if there are any limitations. I could not find it on the website, but if I remember correctly the amount of routes is only impacted by the amount of memory the bird server has? Kind regards, Tom van Leeuwen

3 2

how to use "Operators" in bird
by 曾小小 30 Jul '14

30 Jul '14

hi, My system is Ubuntu 13.04, kernel version is 3.8.0-21-generic, bird version is 1.4.4. Device configuration is as follows: 1. about function function rt_import (int asn; int set peer_asns; prefix set peer_nets) { if (net ~ peer_nets) then return false!; } 2. about filter filter bgp_upstream { if rt_import (64609, [64609], [192.168.1.0/24]) then reject; } In the above function, I use net ~ peer_nets to filter out peer_nets route, but in filter medium, peer_nets defined as 192.168.1.0/24, which would lead to such a fine route 192.168.1.1 will be filtered out. If the test using the "-" operator, will lead filter to filter out all the routes. Why? In the above example, how can I use "operators" to achieve peer_nets defined as 192.168.1.0/24, 192.168.1.1 subnet address to ensure it will not be filtered out. Thank you very much for nothing always help, thanks.

2 1

Protocol static with virtual devices
by kiwi 30 Jul '14

30 Jul '14

Hi everyone, many months ago I tried to install a route on a virtual device (IPIP, GRE, doesn't matter) like this: protocol static { 1.2.3.0/24 via "ipip0"; } It didn't worked out. So I've choosen another non-bird solution. Yesterday I tried it again and it still does not work. Now I've tried to investigate a bit: birdc show interfaces: ipip0 DOWN (index=39) PtP Multicast AdminUp LinkUp MTU=16412 Looks like bird don't want to install the route because of the devices state (AdminUp, LinkUp but DOWN). "Protocol device" is active (scan time 10) and birdrestarts also don't help. bird> show route for 1.2.3.0/24 Network not in table Any ideas? Best regards, Manu

2 1

Ubuntu / debian bird packaging
by Alex Bligh 25 Jul '14

25 Jul '14

Previous packaging had the init script read /etc/default/bird, which pretty standard Modern packaging seems to look for /etc/bird/envvars Is there a reason for this change (which broke stuff here) and would reading both be better? -- Alex Bligh

1 0

Re: ubuntu packages upstart config - $BIRD_ARGS missing
by Frederik Kriewitz 24 Jul '14

24 Jul '14

On Thu, Jul 24, 2014 at 5:01 PM, Ondřej Surý <ondrej(a)debian.org> wrote: > I have added your patch and updated Ubuntu PPAs with Ubuntu patch > level 2 (+2 at the end). Should be built and up shortly. Thank you very much for your instant action.

1 0

ubuntu packages upstart config - $BIRD_ARGS missing
by Frederik Kriewitz 24 Jul '14

24 Jul '14

Hello Ondřej, it looks like you forgot to add $BIRD_ARGS during the creation of the upstart config files. That causes some trouble if you try to enable e.g. graceful restarts (-R flag). We would appreciate it if you could apply the attached patch to fix that. Best Regards, Frederik Kriewitz

1 0

RFC5549?
by Sargun Dhillon 22 Jul '14

22 Jul '14

Is there an plan to support RFC5549 with eBGP soon? Would it require a ton of work (I imagine, given that BIRD, isn't IPv6 aware)?

1 0

Getting started with OSPFv3
by Daniel Corbe 22 Jul '14

22 Jul '14

I'm trying to get an IPv6 adjacency up and running and I'm having issues. I'm hoping someone can point me in the right direction here. When I bring up bird6 I get this: Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::/96 Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::/0 Jul 11 18:08:38 router-priamry bird6: main: Cannot find forwarding address for NSSA-LSA ::ffff:0.0.0.0/96 Followed by this, repeatedly, forever: Jul 11 18:21:15 router-priamry bird6: OSPF: Received non-hello packet from unknown neighbor (src fe80::c67d:4fff:fe9f:945, iface em0) The relevant interface config: em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:0c:29:9c:5c:28 inet 70.32.199.66 netmask 0xffffffe0 broadcast 70.32.199.95 inet6 fe80::20c:29ff:fe9c:5c28%em0 prefixlen 64 scopeid 0x1 inet 70.32.199.65 netmask 0xffffffff broadcast 70.32.199.65 vhid 1 nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> media: Ethernet autoselect (1000baseT <full-duplex>) status: active carp: MASTER vhid 1 advbase 1 advskew 0 The bird config: log syslog all; debug protocols all; router id 70.32.199.66; protocol kernel { learn; # Learn all alien routes from the kernel # persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds import all; # Default is import all export all; # Default is export none # kernel table 5; # Kernel table to synchronize with (default: main) } # This pseudo-protocol watches all interface up/down events. protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol ospf main { # tick 2; # rfc1583compat yes; import all; export all; area 900 { stub; nssa; interface "em0" { hello 1; dead 4; type broadcast; }; }; } And the config from the Cisco side: interface Vlan881 ip address 70.32.199.94 255.255.255.224 ip policy route-map LAB ipv6 enable ipv6 ospf hello-interval 1 ipv6 ospf 100 area 900 end ! route-map LAB permit 5 match ip address LAB set ip next-hop 10.120.0.93 ! ip access-list extended LAB permit ip 70.32.199.64 0.0.0.31 any ! ipv6 router ospf 100 router-id 10.120.9.1 area 900 nssa passive-interface default no passive-interface Vlan881 ... redistribute connected redistribute static ! Regards, Daniel

3 3