Hello!
It's hard to say what may be happening there. I'd suggest to switch on
some debug options, something like my favourite "debug protocols all;"
in the config, simply tracing everything and generating megs of logs
with (sometimes) useful info.
Then you can e.g. try to find when exactly the issue happens and what is
bird doing in that moment. I'd bet on some forgotten corner case route
that needs to be filtered out to not collide with systemd.
Maria
On 5/28/21 8:05 AM, Marvin Gaube wrote:
Hi,
on one of my systems, I'm migrating from ifupdown2 to systemd-networkd.
The scenario is an wireguard-overlay running OSPF and BGP using bird
2.0.7, and the underlay/public network interface being configured using
DHCP and SLAAC.
During the setup, I ran into problems with systemd-networkd, which
changed the interface state into "Could not set NDisc route: Connection
timed out" and loosing the Default WAN Route some time after bird
installed the routes.
This seems like a problem on a netlink-level etc. - likely on the
networkd side, but I wonder if someone on this list had a similar problem.
Bugreport and Discussion is ongoing over at systemd github:
https://github.com/systemd/systemd/issues/19738
Thanks!
Marvin
