This is what we did (spoiler: no pacemaker)
We connect the openvpn-hosts via tinc (could also be openvpn but tinc is
more flexible when servers both initiate the connection) and put these
tunnels into a bridge (with stp).
Then all these nodes have openvpn with server-certificates from the same
ca
On 2012-07-10T14:58:31, emmanuel segura wrote:
> conntrackd - Connection tracking daemon
Syncing the state of a VPN is, due to the encryption, significantly more
difficult than just TCP/IP state. The reconnect/keepalive option is
really the best path forward.
Regards,
Lars
--
Architect S
conntrackd - Connection tracking daemon
2012/7/10 Michael Schwartzkopff
> > Hi there!
> >
> > OpenVPN server has an 'management interface' that allows the admin to
> > delete, add, modify, authorize client connections.
> >
> > As far as I know, it doesn't exist any preestablished method for
> >
>
> >* Hi there!*>* *>* OpenVPN server has an 'management interface' that allows
> >the admin to*>* delete, add, modify, authorize client connections.*>* *>* As
> >far as I know, it doesn't exist any preestablished method for*>* sharing
> >connections between openvpn servers, so in issues like*>
> Hi there!
>
> OpenVPN server has an 'management interface' that allows the admin to
> delete, add, modify, authorize client connections.
>
> As far as I know, it doesn't exist any preestablished method for
> sharing connections between openvpn servers, so in issues like
> failover and/or active
Hi there!
OpenVPN server has an 'management interface' that allows the admin to
delete, add, modify, authorize client connections.
As far as I know, it doesn't exist any preestablished method for
sharing connections between openvpn servers, so in issues like
failover and/or active-active configur
