Hoi,
Thanks for the release! I was wondering about this one:
o Static routes can have both nexthop and interface specified
Could I not have already been able to set 'route 192.0.2.1/32 via
100.64.0.1%eth0 onlink' ? If this is different, can you share a canonical
syntax ?
By the way, the following yields a crash upon startup of Bird 2.14 (perhaps
in 2.15 also, I will check):
protocol static s1 {
ipv4 { export all; };
route 192.0.2.1/32 via 192.168.10.2%e0 *onlink bfd*;
}
root@vpp0-3:~# bird -p
root@vpp0-3:~# birdc configure
BIRD 2.14 ready.
Connection closed by server
root@vpp0-3:~# journalctl -u bird-dataplane --since 22:00 | grep killed
Mar 10 22:10:34 vpp0-3 systemd[1]: bird-dataplane.service: Main process
exited, code=killed, status=11/SEGV
Mar 10 22:10:35 vpp0-3 systemd[1]: bird-dataplane.service: Main process
exited, code=killed, status=11/SEGV
Mar 10 22:10:35 vpp0-3 systemd[1]: bird-dataplane.service: Main process
exited, code=killed, status=11/SEGV
Mar 10 22:10:35 vpp0-3 systemd[1]: bird-dataplane.service: Main process
exited, code=killed, status=11/SEGV
Perhaps enabling BFD on such a static route is ill advised.
On Sun, Mar 10, 2024 at 10:06 PM Ondrej Filip <[email protected]> wrote:
> Dear BIRD users,
> we're releasing a new version 2.15. As usually, I am just a messenger,
> all credits go to my colleagues:
>
> Version 2.15
> o BGP: Send hold timer
> o BGP: New options to specify required BGP capabilities
> o BFD: Improvements to 'show bfd sessions' command
> o RPKI: New 'local address' configuration option
> o Linux: Support for more route attributes, including
> TCP congestion control algorithm
> o Support for UDP logging
> o Static routes can have both nexthop and interface specified
> o Completion of command options in BIRD client
> o Many bugfixes and improvements
>
> Happy routing!
>
> Ondrej
>
>
--
Pim van Pelt <[email protected]>
PBVP1-RIPE - http://www.ipng.nl/
