Keepalived on private network

Posted July 30, 2018 2.8k views
MySQLUbuntu 18.04

I have 2 droplets with public and private IP addresses. I am trying to set up keepalived on both of them in a MASTER/BACKUP config using the private network.

I have been allocated private addresses from a /16 range for my droplets and I picked an unused one from the same range as the virtual IP, but after starting keepalived, other droplets on the same private network cannot reach the virtual IP:

PING ( 56(84) bytes of data.
From icmp_seq=1 Destination Host Unreachable
From icmp_seq=2 Destination Host Unreachable
From icmp_seq=3 Destination Host Unreachable

This works fine on VMs I have on another platform than Digital Ocean - is there something else I need to configure in DO for this to work?


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
2 answers

Hello friend!

In the case of private networking we do use a /16, but each droplet is allocated a single private IP that it must use. If created with private networking enabled, this will already be configured on the droplet. However, if you are adding it after the droplet’s creation, you will want to check the Networking tab on the droplet’s page in the control panel to find the specific IP that has been allocated to it.

Kind Regards,

Thanks Jarland,

So that confirms that there is no way to get a 2nd private IP out of the /16 for a droplet?