Le 07/08/2023 à 22:39, Selva Nair a écrit :
Hi,

    Hi Gert, many thanks, everything's fine, the "block-outside-dns" option
    works perfectly, but we'll have to use OpenVPN GUI only, as OpenVPN
    Connect rejects this as an unknown option. Not a big deal, at least we
    have a working solution.


I'm just being curious, is there any reason why you would prefer Connect over OpenVPN-GUI? Apart from the superficial looks, that is....

Thanks,

Hi Selva,

For a few different reasons, none of which is really a good one however, I plead guilty. ;-)

In fact I began using OpenVPN Connect at work, coupled with OpenVPN Access Server, because we needed MFA and a kind of post-auth checking.

In my private activities, for a not-for-profit organisation, until recently I was still using the open source versions of the server and the client however. But a few months ago, when some of my users told me they were sometimes having DNS lookup problems, I made a few tests with the "OpenVPN Connect" client, which at first seemed less prone to DNS problems. I now know this is dead wrong, as the problem lies in the O.S. itself.

Another reason which incited me to continue using the "Connect" client was the fact that for rather old people not very accustomed to VPNs and the like (my "customers" are mostly retired people in their sixties or seventies), having a big window open, with a clear feedback showing data flowing in and out and displaying quite clearly valuable information as the local IP address and the server's address, seemed easier to use and also for me to diagnose when problems occur.

I'm now reverting to OpenVPN GUI, anyway. That's going to give me a little more work with some of my users, but nothing too serious.

Regards,

Bruno


_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to