I'm still thinking about something to write regarding standalone openconnect and connman+openconnect...
However we can say this commit was very short lived and it was a bit of bad luck that it snuck into Ubuntu 22.04 LTS. It only exists in 8.20 and was reverted in the next release.
Maybe upstream developer @dwmw2 can explain more himself?
"No problem. Apologies for the regression. I think this is the best way forward — we revert the offending change in OpenConnect, and make NetworkManager-openconnect recognise the default route in the split includes and handle it accordingly. If we're going to have to update NM-openconnect anyway, we shouldn't have broken the compatibility in the first place. So this is what I'd like to merge into both projects:"
I'm still thinking about something to write regarding standalone openconnect and connman+ openconnect. ..
However we can say this commit was very short lived and it was a bit of bad luck that it snuck into Ubuntu 22.04 LTS. It only exists in 8.20 and was reverted in the next release.
Maybe upstream developer @dwmw2 can explain more himself?
Here's more notes on upstreams thoughts: /gitlab. gnome.org/ GNOME/NetworkMa nager-openconne ct/-/issues/ 63#note_ 1437353
https:/
"No problem. Apologies for the regression. I think this is the best way forward — we revert the offending change in OpenConnect, and make NetworkManager- openconnect recognise the default route in the split includes and handle it accordingly. If we're going to have to update NM-openconnect anyway, we shouldn't have broken the compatibility in the first place. So this is what I'd like to merge into both projects:"