I have a fantasy concerning all routing daemons that I hope is the
case in bird, but isn't, in babeld.
It's this pattern:
while(true) {
do_somework();
}
where if do_somework() exceeds a deadline (about 4s in the babel
case), bad things start to happen, and cascade.
Modern linux and windows at
Hi,
On Sat, Feb 25, 2023 at 01:01:20AM +0100, Daniel Gröber wrote:
> > If you're really keen on avoiding disruptions, you should first increase
> > the metric to something very lare (say, 2^15), then wait a couple of
> > seconds, then send a retraction, then wait 200ms.
>
> Could you go into a
Hi Juliusz,
On Sat, Feb 25, 2023 at 12:10:26AM +0100, Juliusz Chroboczek wrote:
> > I can't say I agree with the "their problem" mentality. The way I see it
> > during graceful shutdown we're still responsible for in-flight traffic
> > anyway.
>
> What I mean is that after our neighbours receive
>> Of course, if there are no feasible routes to a given destination, then
>> the neighbours will perform an end-to-end search for a loop-free route,
>> but that's the neghbours' problem, not ours.
> I can't say I agree with the "their problem" mentality. The way I see it
> during graceful
On Fri, Feb 24, 2023 at 07:41:03PM +0100, Juliusz Chroboczek wrote:
> > I think I figured out whats going on: babeld immediately flushes the kernel
> > routes it installed when shutting down, without waiting for neighbours to
> > switch to a different path.
>
> Right. How long is the disruption?
