Using bfd {} casues error messages
Ondrej Zajicek
santiago at crfreenet.org
Thu Aug 8 14:55:44 CEST 2024
On Thu, Aug 08, 2024 at 01:10:39PM +0200, Nico Schottelius via Bird-users wrote:
>
> Salut fellow bird users,
>
> we recently tried to simplify the bfd configuration and replaced our
> existing configuration with the following:
>
> --------------------------------------------------------------------------------
> # Using BFD virtually everywhere, enable it globally
> protocol bfd { }
>
> ...
> protocol bgp incoming_r3ge {
> local as myas;
> direct;
> bfd on;
> ...
> --------------------------------------------------------------------------------
>
> And now bird repots every second the following message:
>
> --------------------------------------------------------------------------------
> 2024-08-08 11:00:15.727 <ERR> bfd1: Socket error: Destination address required
> --------------------------------------------------------------------------------
>
> The router has various interfaces, some tunnel, some wireguard tunnel,
> some bridges, etc. and I have a bit trouble to spot, what is causing the
> error message.
>
> Is using protocol bfd {} actually *not* supported?
Hi
Yes, it is, That is the usual way how i configure it. I could imagine
there could be issues in combination with VRFs (in which case i would
suggest BFD protocol for each VRF),
The error message looks like there is a BFD session with zero remote
IP... Perhaps there is some issue with unnumbered links asking for
BFD sessions?
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
"To err is human -- to blame it on a computer is even more so."
More information about the Bird-users
mailing list