Hi
I got two routers running freebsd (BSDRP).
Those two are used as redundant site firewalls and main routers / route
servers.
Both exchange routes between themselves and other routers using Bird
(OSPF+BGP).
Both serve as gateway for our management network, with carp enabled.
I got
> Just working around [...] babeld's non-atomic route replacement interacting
> badly with BIRD's proto/radv.
I guess we could revive atomic updates in babeld, perhaps the buggy
kernels it didn't work with are no longer relevant.
> *neighbour table*. I think the crux of the issue I was seeing is
Hi Juliusz,
On Sun, Mar 31, 2024 at 04:35:28PM +0200, Juliusz Chroboczek wrote:
> > I've just come across a reason I'd want to run babel with both bird and
> > babeld on the same node and have them become neighbours.
>
> I hope you know what you're doing.
I sure hope so too, haha. No it's
> I've just come across a reason I'd want to run babel with both bird and
> babeld on the same node and have them become neighbours.
I hope you know what you're doing.
The simplest solution would be to run each daemon in a different container.
If you don't want to use containers, you'll want to
Hi Babelers,
I've just come across a reason I'd want to run babel with both bird and
babeld on the same node and have them become neighbours. The details are
tedious -- my usual disclamer applies ;)
This got me to think about something I'd observed in the past and been
meaning to write about
Hoi Ondrej, Nico, Sebastian,
I am revisiting this thread based on the question from Benoit this week (
https://www.mail-archive.com/bird-users@network.cz/msg07961.html).
On Tue, Jan 30, 2024 at 3:25 PM Ondrej Zajicek
wrote:
> On Tue, Jan 30, 2024 at 12:20:41PM +0100, Sebastian Hahn wrote:
> >
correction: the error message is not related particularly to bird but seems
related to this issue in latest freebsd release:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275341
Once fixed though, I have the same results. routes are not applied to the
kernel. ospfv3. Applying a `/31` to
