I suspect that this is a limitation of VMware Workstation. Documentation
and conf files seem to lack any mention or setting for host_ip.
-
https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-C2EC7B92-A499-4B47-95B6-0BFDDA28AC34.html
-
https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-EB85B0F7-F9BF-4CE1-9E29-E96734EB52AA.html
Am I missing anything? Is this a VMware Workstation limitation?
On Thursday, April 8, 2021 at 6:43:35 PM UTC-7 Brad wrote:
>
> According to the Vagrant documentation, I should be able to bind a port
> forward to a specific host_ip. However, the binding is being applied to all
> interfaces (0.0.0.0). Any tips on troubleshooting or resolving this issue?
> I've also tried (without success) setting host_ip to 127.0.0.1, tried
> setting a guest_ip (in case both guest_ip and host_ip needed to be set),
> and also set the protocol.Thanks.
>
> Snippet from Vagrantfile:
> config.vm.network "forwarded_port", guest: 3389, host: 3390, host_ip:
> "172.10.0.27"
>
> System/Vagrant Info:
> $ vagrant --version
> Vagrant 2.2.15
> $ vagrant plugin list
> vagrant-vmware-desktop (2.1.5, global)
> $ vmware --version
> VMware Workstation 16.1.0 build-17198959
> $ sudo ss -tulpn | grep 3390
> tcp LISTEN 0 20 0.0.0.0:3390
> 0.0.0.0:* users:(("vmnet-natd",pid=623325,fd=9))
>
>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/be5c972b-ca8f-4f6c-a0d1-9b8b5d34496fn%40googlegroups.com.
