Related

Unable to turn the zabbix server on to start monitoring. Question Question
Configuring virtual dev server - Apache question Question Question

Question

private-network is not correctly set on droplets

Posted November 29, 2015 5.7k views
CentOSGetting StartedNetworking

After creating 2 droplets(CentOS 7), and booting the system, I powered them down, added private network to them, which DO portal showed its addresses correctly.
But ifconfig command for eth1 did not have any of that IP address, just showing the IPv6 address.
I added the private IP address with ifconfig to eth1, which provided private IP to the instance(droplet), but since there is no file under /etc/sysconfig/network-scripts/ for ifcfg-eth1, most probably every time I reboot the instance, I have to re-assign the private IP to the instance. which can be counter-productive.
Could you please let me know which step I am missing here. Thanks.

Add a comment
saeed
By:
saeed
Add a comment

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.

×
2 answers
jtittle1 November 29, 2015

@saeed

If you’ll drop by the link below and look for the header “CentOS & Fedora”, it’ll provide you with the correct way to get the Private Network up and running :-). There’s a specific method you need to use when adding the interface and you need to make sure that you reboot after performing the changes as well (this reboot would be in addition to the one performed through the control panel to gain the IP).

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

Reply Report
saeed November 29, 2015

Adding the ifcfg-eth1 file manually resolved the concern of reboot and IP assignment for private interface.
Thanks @jtittle

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help