Thanks Colin,
just missed the policy "local" thereby
ip_heartbeat site
so I can log into both master and slave servers
2013/12/17 Colin Ryan
> Unless I'm reading your original post wrong this is your issue.
>
> > local 192.168.20.253
>
> When you have a cluster (active-passive) - as I believ
Unless I'm reading your original post wrong this is your issue.
> local 192.168.20.253
When you have a cluster (active-passive) - as I believe you are trying
to do - each hardware node, has as you outlined, a real physical
address and then there is a floating IP ( or what I call VIP ) that t
Hi Colin,
My nat rule are correct. To ensure this, when I switch on the firewall
to redirect
it to the address I connect .253.
In my server.conf not know the "local" policy, as stated by you.
Follow my server.conf
proto udp
port 1194
dev tun0
ca /etc/openvpn/easy-rsa/2.0/keys/ca.crt
cert /etc/o
Hello,
OpenVPN will listen on all interfaces by default.
I have a working setup with two OpenVPN servers master-slave with ucarp and
it works very well.
ucarp allows you to run scripts when a host becomes MASTER or SLAVE so in
addition of migrating the virtual IP address you can also perform oth
Christiano...
I assume your your reference to heartbeat is actually the floating VIP
that is the fail-over IP between the cluster nodes.
And your firewall's allow UDP access to only the .20.24
Have you told your OpenVPN instance ( you didn't post your config file
;-) ) to bind specifically
Hi,
I have two openvpn servers in cluster with heartbeat + drbd.
server01 ip: 192.168.20.253
server02 ip: 192.168.20.254
heartbeat ip: 192.168.20.24
I like working with high availability, my external connections arrive at
the firewall on port 1194 udp and are redirected to 192.168.20.24, so if t
