-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
public_network Bridge Static IP, VMware Provider - not working as expected #4184
Comments
And just FYI, this is the
|
So nothing? Can I get a refund then? 18 days and nothing? Not even a confirmation of a bug? |
Sorry about this, we haven't been triaging Vagrant issues since we've been working on Terraform lately. For official support, please contact support@hashicorp.com in the future. If we didn't make that clear enough, it was in the original activation email we sent. VMware doesn't support static IPs on public networks right now (only private). This is actually in an upcoming free update but this hasn't been released yet. Happy to refund you if this is something you need right away and sorry about that. Just email us at support or email me directly at mitchell@hashicorp.com and I can handle that for you. |
@mitchellh do you know if VMware released the fix? It seems that it's not working yet. I'm running vagrant 1.6.5, VMware Fusion Version 6.0.5, Mac 10.10 (Yosemite). |
According to this #1269, I should be able to assign a static IP address on the public_network :bridge. Now I happen to do this frequently on Virtualbox VMs, so I assume this could be a fusion/vmware provider issue? Below is my Vagrantfile, and
ip addr show
output. What ends up happening is, I get a DHCP address (192.168.0.0/24).Then, attempting to list the IPs, we can see it was never used.
The text was updated successfully, but these errors were encountered: