Bird-users

Download

bird-users@network.cz

November 2010

14 participants
12 discussions

Re: Detecting static route availability [Was: Detecting link state, FreeBSD]
by Matthew Walster 04 Nov '10

04 Nov '10

The obvious way would be to use a FHRP such as VRRP or CARP, alternatively use something like RIP in receive only mode. There has to be a decent reason to use that though! Matthew Walster On 4 Nov 2010 16:16, "Stéphan Kochen" <stephan(a)kochen.nl> wrote: On do, 2010-11-04 at 10:24 +0100, Ondrej Zajicek wrote: > I would suggest to use some shell/perl script that ping to the gateway > and according to its reachability it will enable/disable static > protocol (with routes using that gateway) in BIRD. While we're on this topic... I'm facing a similar situation, where a bunch of publicly addressable hosts have a primary default route and a secondary. I was wondering if there is some reliable way of doing this kind of failover, or even if there is a ready-made solution out there. My concern with doing this myself is important scenarios I might be missing. For example, routers that drop pings under congestion. Or indeed if both my routers end up in an unreachable state, to not end up with an empty route table. I'm not on FreeBSD, but Linux myself. And I know Linux can do failover using the neighbour table and multiple routes with metrics. But all of this appears to be undocumented voodoo. What's really the proper way of doing this? Thanks, -- Stéphan

1 0

Detecting link state, FreeBSD
by Mahlon E. Smith 04 Nov '10

04 Nov '10

I'm running bird 1.2.4 on a series of FreeBSD OSPF routers. Had a backhoe go through some fiber this morning (really), and was surprised to find that bird didn't update routes automatically. The state of the interface in question looked like so, while bird was still happily reporting that it was available: bge1: flags=8802<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:18:8b:f6:e5:a8 inet x.x.x.x netmask 0xfffffffc broadcast x.x.x.x media: Ethernet autoselect (none) status: no carrier I performed a 'ifconfig bge1 down', and the failover routes immediately propagated. I've got a device scan in my config: protocol device { scan time 10; } I don't see anything else to add or modify in the config for checking interface status -- did I miss something? My anticipated behavior would be that a link down would perform a route update. It appears that interface state with the 'device' protocol is different or separate from its link state. Or maybe this is a FreeBSD (or Broadcom?) specific issue? Any ideas/suggestions appreciated. -- Mahlon E. Smith http://www.martini.nu/contact.html

5 9