On 29/09/21 2:00 am, Henning Follmann wrote:
My comment to the OP was basically on the nebulous source (most VPN Providers) and the generalized categorization (N-M is buggy), which I disagree with.
My own problems with NM, which may be related, seem to be shared with many in the 'OpenVPN community'.
It seems that for configuring OpenVPN, NM does its own thing, and mostly ignores the 'standard' configuration files etc. that are covered by the OpenVPN documentation. Even some of the terminology seems to be different.
That makes it very difficult to match up the changes I might make on my server to those that are needed on the (NM-managed) client. I had it working on my buster laptop, but with a reinstall of bullseye, combined with some changed defaults in the OpenVPN setup, I ended up giving up - I now start my VPN with systemctl rather than clicking through NM. I should probably write a script rather than trying to remember how vpns map to systemctl unit targets (?), but I don't use it very often, and have moved on ...
I feel the NM maintainers could do more to talk to the OpenVPN folks, and maybe provide some tools to import standard configs, or generate something that NM can consume? Maybe vice-versa too. I don't know where those responsibilities lie.
Cheers, Richard