On 14-05-07 09:55 AM, David Goodenough wrote: > On Wednesday 07 May 2014 14:42:10 Timothy Murphy wrote: >> I'm running an openvpn server on my home CentOS server. >> Openvpn works fine on my Fedora/KDE laptop if I am away from home, >> but if the laptop is on my local LAN I have to edit client.conf >> to give the local name of the server. >> >> Although I am running NetworkManager on the laptop >> I am not using the NetworkManager-openvpn plugin, >> basically because openvpn works perfectly >> whereas NM occasionally causes problems. >> >> But I'm wondering if I did use this >> would it solve the remote/local problem I mention above? >> >> Of course this "problem" has a trivial solution >> so it may not be worth while doing anything about it. >> I've actually never seen the point of the NM-openvpn plugin - >> so I was wondering if this is one time when it would be useful. > You can specify multiple server addresses at the client end, > and it will find the first that works.
Indeed and it works well. Here's an example of this: remote vpn.example.com # public DNS remote 192.2.0.1 # internal/lan IP server-poll-timeout 3 # Try a remote for N seconds then try next one Regards, Simon ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
