Ask Your Question
0

VMs dhcp requests getting public IP instead of private

asked 2016-02-14 21:25:47 -0600

SanDiegoEarl gravatar image

I've installed an all-in-one devstack from master. Everything seems to be working, however, after the first instance is deployed, all of the following instances get an IP address in the public range instead of the internal private subnet. My deployment is on a VM using NAT networking with the ip configured to 192.168.157.10.
I have the local.conf file with the following

HOST_IP=192.168.157.10
FIXED_RANGE=10.0.0.0/24

This is what the 1st instance log shows...

Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending select for 10.0.0.2...
Lease of 10.0.0.2 obtained, lease time 86400

This is what the 2nd and all following instance logs show... Starting network...

udhcpc (v1.20.1) started
Sending discover...
Sending select for 10.0.0.7...
Received DHCP NAK
Usage: /sbin/cirros-dhcpc <up|down>
Sending discover...
Sending select for 192.168.157.203...
Lease of 192.168.157.203 obtained, lease time 433800

Please let me know if there is something I have done wrong or is missing, and if you need more details please just ask. I've been trying to resolve this issue for days. Thank you in advance.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
1

answered 2016-02-17 17:28:42 -0600

SanDiegoEarl gravatar image

So after days of trying to solve this challenge, I've finally found the cause. My environment is run on my workstation using VMware Workstation. I setup the interface for my all in one VM to use the NAT virtual network.

The solution to my problem was first set the network to use a static IP, then to edit the VMware workstation virtual network settings to turn off the "Use local DHCP service to distribute IP addresses to VMs" setting for the NAT network.

Once that was turned off, all of the images deployed through openstack are getting IPs assigned from the internal 10.0.0.0 network.

One thing to note about this solution is that if you have other VMs running in your VMware Workstation, and they are using NAT networking, you will have to set them all to use a static IP configuration because you can only have 1 NAT interface in VMware Workstation. I will be looking at creating custom network interfaces using the "Add Network" feature of the VMware Workstation "Edit Virtual Networks" feature.

Hope this info helps the next person. :-) Thanks.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-02-14 21:25:47 -0600

Seen: 298 times

Last updated: Feb 17 '16