W dniu 10.06.2024 o 14:19, Torsten Wilms via Bird-users pisze:
Thats it!
Ok, but is there some configuration option to use the normal bird2.15
with the same result as bird2-rtsock?
FreeBSD port net/bird2@netlink, which is now the default flavor for
FreeBSD 14.0 and later, will accept configuration inherited from
net/bird2@rtsock. The opposite statement is not true, there are some
configuration options allowed for Netlink flavor, which will be rejected
by rtsock-driven bird2.
*From: *Bird-users <bird-users-boun...@network.cz> on behalf of Jan
Bramkamp <cr...@rlwinm.de>
*Date: *Monday, 10. June 2024 at 13:34
*To: *bird-users@network.cz <bird-users@network.cz>
*Subject: *Re: bird2.15.1 - FreeBSD14
What changed recently is that the Bird 2.15 port defaults to using
Netlink instead of route sockets to access the kernel routing table on
FreeBSD 14.0 and later. Can you install the other flavor of the bird2
port (bird2-rtsock-2.15.1 instead of bird2-2.15.1), restart the bird2
service (not just reload the running process), and report back if that
works? If that alone solves your problem you've found a regression in
the new default flavor.
On 10.06.24 10:13, Torsten Wilms via Bird-users wrote:
I am using FreeBSD 14 with FIBs.
With bird2.14 I get routes via BGP and anything is fine.
With bird2.15.1 I get routes, but the daemon doesn’t put them into
the kernel routing table. Same configuration work with older version.
Does something change which has an effect on it?
The issue was fixed yesterday[1]. Please, try it if you can build kernel
from the sources with this patch applied.
1.
https://cgit.freebsd.org/src/commit/?id=f34aca55adef1e28cd68b2e6705a0cac03f0238e
--
Marek Zarychta
