- Bird-users - Mailing Lists

bird's not forwarding point-to-point routes via OSPF
by Noel Burton-Krahn 16 Oct '14

16 Oct '14

Is there something about point to point addresses that could keep bird from forwarding them? I'm assigning a point-to-point address to a veth pair like so: ip link add veth1 type veth peer name veth2 ip addr add 10.0.0.1/32 peer 10.0.0.2/32 dev veth1 ip addr add 10.0.0.2/32 peer 10.0.0.1/32 dev veth2 Neither of those addresses get forwarded via OSPF to other hosts. They *do* get forwarded if I add the addresses without a peer like this: ip addr add 10.0.0.1/32 dev veth1 Now I've added the same address (10.0.0.1/32) to veth twice, and bird is forwarding a route for that address to OSPF peers. Is there a way for bird to accept the "peer" address? I tried "learn" in the kernel but that didn't help. TIA, -- Noel

2 1

RIP not doing "triggered update" following route deletion
by Tore Anderson 15 Oct '14

15 Oct '14

I've noticed that BIRD doesn't withdraw (i.e., advertising them with metric 16) RIP routes when they disappear from the routing table. This means that the neighbour router ends up waiting for the route to time out before ceasing to send traffic to the BIRD router, rather than doing so immediately. I'm running v1.4.0 with a bird.conf containing: log syslog { info, remote, warning, error, auth, fatal }; router id 192.0.2.1; protocol device {} protocol direct {} protocol rip { interface "*" { mode nolisten; ttl security on; }; import none; export all; } To reproduce the issue, look at "tcpdump -v port 520" while doing: 1) ip address add 192.0.2.2/32 dev lo -> a triggered update appears (advertising 192.0.2.2/32) 2) ip address delete 192.0.2.2/32 dev lo -> a triggered update doesn't appear (it should have) For what it's worth, step #2 does increase the RIP protocol's "Export withdraws" counter. This issue also applies to RIPng/bird6. AFAICT, not sending these triggered updates immediately is a standards violation. Quoting RFC 1812 F.2: «A router MUST send a triggered update when routes are deleted or their metrics are increased.» Also see RFC 2453 section 3.10.1. Tore

2 3

BIRD on FreeBSD
by Eric Nghia Nguyen Duy 13 Oct '14

13 Oct '14

Dear all BIRD users, At this moment we are looking into deploy BIRD of FreeBSD so we would like to have some opinion from someone already did it. It should be pretty straight forward but if there is any concerns/issue/experience that anyone want to share, it would be appreciated. -- Best Regards, Eric Nghia Nguyen-Duy NOC engineer www.ams-ix.net eric(a)ams-ix.net

7 11

OSPF stubnets of PtP interfaces
by Thomas Goldberg 10 Oct '14

10 Oct '14

Hello, we've OSPF running over a openvpn ptp tunnel and some problems with the routes injected by bird (v1.4.5). OSPF is running in PtP mode on the tun0 interface of each router. The problem is that bird doesn't inject any routers for the local interface IP as intra-area route into OSPF itself. We've to inject them as external route via import of routes learned by a direct protocol (d_local). This is how the end result looks: Router A: interface config: 17: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 10.176.3.29 peer 10.176.3.30/32 scope global tun0 bird routes: 10.176.3.30/32 dev tun0 [d_local 2014-10-07 16:13:46] * (240) 10.176.3.29/32 via 10.176.3.30 on tun0 [o_internal 2014-10-09 17:45:44] * E1 (150/100) [10.176.3.30] Router B: interface config: 13: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100 link/none inet 10.176.3.30 peer 10.176.3.29/32 scope global tun0 bird routes: 10.176.3.29/32 dev tun0 [d_local 2014-10-09 17:45:43] * (240) 10.176.3.30/32 via 10.176.3.29 on tun0 [o_internal 2014-10-09 17:40:51] * E1 (150/100) [10.176.3.29] Shouldn't bird inject routes like this on the corresponding router (without having to learn them via the direct protocol)? 10.176.3.29/32 dev lo [o_internal 2014-10-09 00:00:00] * I (150/0) [10.176.3.29]

2 1

Re: OSPF route selection
by Olivier Benghozi 09 Oct '14

09 Oct '14

On 9 oct. 2014 à 12:54, Ondrej Zajicek <santiago(a)crfreenet.org> wrote : > On Wed, Oct 08, 2014 at 01:28:43PM +0200, Olivier Benghozi wrote: >> it should be noted that the RFC 2328 explains in its annex C.1 that the "RFC1583Compatibility" flag must be "Set to enabled by default". > > Thanks, i never noticed that. And some codes don't even allow to switch it off (Ericsson/Redback...) :-/ >> The critical thing is having that configuration consistant across the >> network (default values sometimes suck), and understanding what is done >> (if set to off, the particular loop case design must be avoided). > > This is probably a typo, but the loop case must be avoided when > RFC1583Compatibility is enabled, not when it is turned off. Right, if set to On :)

1 0

Version 1.4.4
by Ondrej Filip 07 Oct '14

07 Oct '14

Dear Bird users, the new version is out: Version 1.4.4 o Extended OSPF multipath support. o Default router preference for RAdv. o Significant changes in socket layer. o Important bugfix in BGP. o Several minor bugfixes. Ondrej

7 9

[PATCH] bird.init: Added a check_config function and call it prior of, start and reload
by Pavlos Parissis 06 Oct '14

06 Oct '14

Hi, This another patch for the init script which adds a check_config function and call it prior of, start and reload. It should be applied on top the other patch I sent on 2nd Sep. Cheers, Pavlos

4 8

Netconf/YANG support
by Mathias Wolkert 06 Oct '14

06 Oct '14

Hello list Anyone besides me who would like to see Netconf/YANG support in BIRD? Any plans for that? /Tias

1 0

[PATCH] bird.init: Run status, reload and stop only for enabled, versions of IP
by Pavlos Parissis 02 Oct '14

02 Oct '14

Hi, Here is my 1st patch for this project! Please let me know if it is rejected or accepted:-) Cheers, Pavlos

1 0

prefix patterns cannot be defined as constants
by Kai 02 Oct '14

02 Oct '14

Hi there! Just noticed that (shorthand and long) prefix patterns cannot be defined as constants. During a quick search I couldn't find this behaviour documented, so maybe it might be considered a bug? Example: define my_const = fc01:2345::/48+; ... returns a syntax error. As does: define my_const = fc01:2345::/48{48,128}; Best regards, Kai

2 1