| === slyon is now known as slyon_ | ||
| === slyon_ is now known as slyon__ | ||
| === slyon__ is now known as slyon | ||
| fiesh | even in the virtual machine that I just set up with a stock Ubuntu 20.04, I cannot manage to have netplan / systemd not drop routes of a device on carrier loss... It does re-add them correctly when the carrier comes back, unlike on our actual server, so the problem would arise as such, but since I can't see why this doesn't happen on our server, setting the `ActivationPolicy` to `always-up` *seems* to be | 09:11 |
|---|---|---|
| fiesh | what I'd want, but it just seems to have no effect :-( | 09:11 |
| fiesh | I disconnect the (virtual) cable, and the routes are gone | 09:11 |
| fiesh | hmm it works when configuring the device via systemd's network directly. So I guess I'll have to not use netplan on our server then as a solution | 09:33 |
| slyon | fiesh: uh.. that's really interesting. Could you spot the difference between your manual systemd-networkd config (probably in /etc/systemd/network/) and netplan's systemd-networkd config in /run/systemd/network/ ? If it's just a single setting, you could always use a systemd-networkd override config/snipped, to adopt netplan's config to your needs | 09:55 |
| slyon | (and we could potentially fix it in upstream netplan, if we know which setting makes the difference) | 09:56 |
| fiesh | ah no, I didn't know the generated config was available there | 10:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!