|
|
Ed Russell wrote: > Hello OpenVPN gurus, we are currently utilizing a network of about 75 > OpenVPN clients (Linux) connecting to 2 primary servers. We would like to > designate one server as a primary and the other as a secondary. At some > point soon we will introduce more servers. Basically what I am trying to > accomplish is the ability to specify a "main" server that the client will > always look for. Only after it is 100% sure it is down the client will > bounce to the secondary. While attached to the secondary it will > periodically look for the "main" server. Is this possible? Specifying multiple remote lines without remote-random already goes through the remote servers in order; the only thing you're missing is periodic checks to see if the old master has returned, which OpenVPN doesn't support. I address this issue via having a heartbeat solution at the server side, such that the hot spares stay down unless they notice that the master has died (and any higher-priority spares with it). That way, there's no chance of some clients being connected to the wrong server -- because only the intended live server is accessible in the first place. ______________________ OpenVPN mailing lists https://lists.sourceforge.net/lists/listinfo/openvpn-users Warning: require_once(../../../archive_common.php) [function.require-once]: failed to open stream: No such file or directory in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-11/msg00008.html on line 194 Fatal error: require_once() [function.require]: Failed opening required '../../../archive_common.php' (include_path='/usr/local/lib/php') in /home/openvpn/domains/openvpn.net/public_html/archive/openvpn-users/2006-11/msg00008.html on line 194 |