Using bfd {} casues error messages

[Nico Schottelius]

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.

All interfaces that are used for BGP obviously have an IP address , but
many bfd sessions are actually down that I'd expect to be up:

--------------------------------------------------------------------------------
bird> show bfd sessions 
bfd1:
IP address                Interface  State      Since         Interval  Timeout
2a0a:e5c0:10:1:fa5e:3cff:fe2d:eb04 eth0       Down       2024-08-06      1.000    0.000
2a0a:5480:5:2::1          or3ge      Down       2024-08-06      1.000    0.000
2a0a:e5c0:10:1::123       eth0       Up         2024-08-06      0.100    0.500
2a0a:e5c0:10:1:fa5e:3cff:fe2d:eafc eth0       Down       2024-08-06      1.000    0.000
2a0a:e5c0:32:1::1         oserver121 Down       2024-08-06      1.000    0.000
2a0a:e5c0:142:2::2        iserver138 Down       2024-08-06      1.000    0.000
2a0a:e5c0:142:3::2        iapured2   Down       2024-08-06      1.000    0.000
2a0a:e5c0:43:2::1         oserver138 Down       2024-08-06      1.000    0.000
2a0a:e5c0:142:1::2        ir3ge      Down       2024-08-06      1.000    0.000
2a0a:e5c0:10:1::141       eth0       Up         2024-08-06      0.100    0.500
2a0a:e5c0:10:1::122       eth0       Up         2024-08-06      0.100    0.500
bird> 
--------------------------------------------------------------------------------

(excluding the two 2a0a:e5c0:10:1:.. ones, they don't have bfd enabled
at the moment)

Is using protocol bfd {} actually *not* supported?

Best regards,

Nico


-- 
Sustainable and modern Infrastructures by ungleich.ch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 873 bytes
Desc: not available
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20240808/a118f9b9/attachment.sig>