Hi,
Generally, BIRD should not try to use an address before it notices that
the address is available/active. If BIRD tries to bind the socket before
that, then it is a bug.
This seems to be a common pattern for services that are started when
network is supposedly ready, but it really isn't (s
Hi,
upon a reboot of a system running BFD I recently noticed BFD breaking
with error "Cannot assign requested address" once the system came back.
Restarting the BFD protocol in question solved the problem.
Hence, apparently the system's network wasn't fully up and running at
the time bird started;
On 31.10.2016 16:02, Ondrej Zajicek wrote:
> Is there no other factor like firewall, NAT?
*sigh*
Thanks for pointing me there, this apparently was the factor I forgot
myself. Yes, the BFD traffic was blocked by a packet filter.
Sincere apologies for the noise, and great software, by the way :)
Th
Ondrej Zajicek:
I think that if there is no explicit 'requestor' for BFD session (like
static protocol on client), you have to explicitly add neighbors
in BFD protocol on gateways:
protocol bfd {
interface "vlan*" {
passive;
};
neighbor 192.168.1.3;
}
Un
Hello all,
I am trying to make use of BFD for default gateway failover (in my BFD
test bed). I used multiple variations, but according to the
documentation (if I get it right), I should be fine using something like
this:
,-- on client:
# empty BFD config
protocol bfd {
#debug all;
}
