31 Mar
2024
31 Mar
'24
3:35 p.m.
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 that both daemons will use eg. fe80::1 to source their babel hellos
Oh, you're running both babeld and BIRD on the same interface? I assumed you were running them on different interfaces. I'm really not sure if it can be made to work. -- Juliusz