Private Network does not work.

Posted March 16, 2018 5.4k views

Private Networking does not work.

I created two droplet. A and B. All from scratch and Private IP enabled.

When I ssh into A, ping to Private IP of B fails. When I ssh into B, ping to Private IP of A fails.

I’ve followed the tutorial provided: How To Set Up And Use DigitalOcean Private Networking and it still fails. I have removed all the rules from firewall and it still fails.

Here is what I get when I ping:

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

Note that pinging the public ip works. But I am setting up a private network in NYC1 datacenter and it doesn’t help.

This is on a Ubuntu 16.04 LTS droplet.
Also all the droplets are created from the same Digitalocean account.

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

Interestingly, when I ran arp -an it showed this:

? (OTHER_PRIVATE_IP) at <incomplete> on eth1

I talked with support and the told me to manually add the private ip and hwadress of the other droplet. So I ran the following:


I ran it on each of the droplets with the other machines ip and hwaddr (found using ifconfig). Now pinging the machines works!!!

  • i have a similar issue, so i set this while I ssh into A
    arp -s <machine B private ip> <machine B mac address>

    and in machine B I set
    arp -s <machine A private ip> <machine A mac address>

    still not working.
    Mind to share what else do you need to set for iptables for private network?

What does your routing table show.

netstat -rn