private networking between two droplets not working Ubuntu 16LTS

September 2, 2017 1.6k views
Networking Ubuntu 16.04
kevinmc
By:
kevinmc

I had an existing instance of ubuntu (WordPress app ubuntu 16) running and I setup another droplet to move the DB.

On existing droplet I powered down and installed the private Networking option and powered back up.

On new droplet setup with private networking.

I was unable to connect to the mysql server so I disabled uff and checked to ensure it was down. Same on existing server.

eth0 public facing
eth1 private network

Pinging on eth0 works pinging on eth1 fails (this is on both machines)

Found this guide…

https://www.digitalocean.com/community/tutorials/how-to-enable-digitalocean-private-networking-on-existing-droplets

So following the guide for Ubuntu and Debian…

vim /etc/network/interfaces

As stated in post…

"You will see two main sections, each used to define the two active network interfaces. We will create another section at the bottom to describe the eth1 interface that will be used for private networking.”

The only thing I see is…

auto lo
iface lo inet loopback

And adding

iface eth1 inet static
address 10.132.84.55
netmask 255.255.0.0

And of course reboot

Results in nothing

The provided article to enable Private Networking is from 2013 so I am thinking that the default interface config file is loading from somewhere else? Something has changed?

If there is anyone that could help me wrap my head around this I would greatly appreciate it!!!!

IN addition the guide How To Set Up a Remote Database to Optimize Site Performance with MySQL is dated a bit using ubuntu 12.04 so i am not sure how relevant that is considering that i cannot get the servers to talk to one another on the private network. :(

Log In to Comment
3 Answers
championswimmer September 7, 2017

There is a step missing in that guide.
You need to edit this file - 

sudo nano /etc/udev/rules.d/70-persistent-net.rules

and add a line for your networking interface.
Usually if you perform sudo ifconfig -a you'll find an ethernet interface names as ens4 or ens3p2 or something that like that. That needs to be renamed to eth1. Copy it's HwAddr and add a line to the 70-persistent-net.rules in this format

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="0a:83:3f:62:be:86", NAME="eth1"
Reply
bladedshard February 1, 2018

What If I followed every guide, digital oceans guide, and this guide, plus a lot more. And I cant ping my private ips within the same datacenter, but I can certainly ping the public IP.

Now... after following more guides, eth1 shows up, but there is no gateway, ip, netmask and 38 hours and digital ocean hasn't responded to my ticket. The community is the only other option

Also the above
'''sudo nano /etc/udev/rules.d/70-persistent-net.rules'''
doesn't exist. The directory does but that file does. and my interface names showed up just fine.

I know a way to fix it but I'm trying to avoid that.

Help would be appreciated.

Reply
bladedshard February 1, 2018

This is why I prefer Excelnode. You will ALWAYS get a response in-under 10hours....90% of the time in the 3 years I've used them. I've never had to wait for a response for more than 1 hr.

Come to digital ocean for private ips....Response wait time 24-48hrs+

ANY ASSISTANCE PLEASE DIGITAL OCEAN. Probably will just be cancelling my service since the lack of support from digital ocean.

Reply
Have another answer? Share your knowledge.

Related Questions