Well, looks like I spoke too soon. The fix does not persist across
reboots - fails with the backup routing table error.However, then
changing the metric again gets the client working again, until another
reboot. Back to OpenFortiVPN, I guess...
I think I may have solved this. The metric for my wired connection
("connect automatically with priority") was set to -999. I have never
touched that setting, AFAIK. Hovering over the value, the help popup
said the default value is 0. Changed it to 0...
This actually stopped working after a while - either after a reboot or
after something else was updated, not exactly sure what. Will try the
solution linked by Sadullah below.In the meantime, I've just been using
openforticlient.
This didn't work for me, but based on it, I just did: cp
/usr/bin/resolvctl /usr/bin/systemd-resolve There was no
/usr/bin/systemd-resolve file present before copying resolvctl to it.
The Forticlient VPN is now working as expected, instead of termina...
