On 17/03/2021 05:19, tincanteksup wrote:
On 15/03/2021 04:05, Eric Schoeller wrote:
Hello,
I've been an OpenVPN user for about 15 years, but I am brand new to
the mailing list.
I am building a redundant monitoring system (naemon+merlin) and I
would like to establish a means to connect three distributed
monitoring machines over a common private encrypted network using
OpenVPN. I am designing the system in a manner where any of the
machines can be off-line but the 'service' remains fully functional.
So, I wouldn't be able to define just one of the machines as the
OpenVPN server, since if it goes down the other two lose connectivity
to each other. And the intent of the system is to be fully
isolated/stand-alone - so I really shouldn't introduce other systems
into the mix.
The way I've accomplished this in the past is as follows:
Server A has clients B and C
Server B has clients C (and A)
Server C has clients A and B
problem solved.
As you pointed out in your OP:
<q>
I am designing the system in a manner where any of the
machines can be off-line but the 'service' remains fully
functional.
</q>
OSI Layer becomes the deciding factor.
If your application is resilient to any network failure then it
has nothing to do with OSI-Layer-3 because every node must offer
the same service.
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
