That is surprising, because Ubuntu has been using systemd-resolved for four years now, so I would expect third-party developers to have figured it out, but Ubuntu is a little different in that it reads /etc/nf still. A bug report against the app is warranted regardless, because it clearly doesn’t know how to create NetworkManager profiles that are compatible with split DNS. Otherwise, I’m going to recommend disabling systemd-resolved as there’s not much else you can do if you have a third-party VPN app creating and deleting broken NetworkManager profiles such that it’s impossible to permanently modify them. So if you have good luck with that NetworkManager plugin, that would probably be much better than using a third-party application to configure your VPN. If you let NetworkManager handle your VPN, you’ll not only have much better desktop integration, you definitely won’t experience this bug (because NetworkManager knows how to configure systemd-resolved properly), and for bonus points you’ll be able to make permanent modifications to the NetworkManager profile if needed. So I see three options: (a) fix that app (good luck? it’s probably proprietary?), (b) disable systemd-resolved, or © sudo dnf install NetworkManager-fortisslvpn-gnome and try creating your VPN connection in System Settings instead. If so, no amount of configuration outside the app is going to help. I guess it is creating and deleting NetworkManager profiles itself. Hm, you might want to create a bug report against that app directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |