[07:14] <slyon> fiesh: that "netplan-override.network.d" needs to match the file generated by netplan. Is your netplan interface called "override" in the YAML? Please check "ls /run/systemd/network/" to find the name/file generated by netplan.
[07:18] <fiesh> slyon: ah!  so I have /run/systemd/network/10-netplan-enp4s0f3.network
[07:18] <fiesh> slyon: so I have to call it /etc/systemd/network/10-netplan-enp4s0f3.network.d/override.conf ?
[07:19] <slyon> yes, exactly
[07:19] <fiesh> (I was actually hoping to override *all* devices since i suspect the others to also be susceptible to route-loss on carrier loss)
[07:19] <fiesh> it's just that the other devices are connected to internal network switches which aren't disconnected / restartet usually, unlike the ISP's router which just does its maintenance reboots without prior announcement
[07:21] <fiesh> slyon: I'll keep you posted when I can try it again ;-)
[07:21] <slyon> thanks!
[07:22] <fiesh> slyon: is a systemctl daemon-reload sufficient for it to come into effect?
[07:24] <slyon> Hmm... not sure. better try 'networkctl reload' as well
[08:21] <fiesh> slyon: ok thanks!
[08:56] <fiesh> well that didn't go as planned
[08:57] <fiesh> it triggered right away, and having `Name=*` in the match is *very* bad since all virtual devices get the default routes set too
[08:57] <fiesh> no idea why
[08:57] <fiesh> so anyway, need to match the proper devices explicitly, will try that when I don't screw up our entire network during operation time ;)
[17:34] <fiesh> slyon: so the overrides don't seem to help either :-(
[17:34] <fiesh> just tried
[17:34] <fiesh> fml how can it be so hard