vagrant-notify-forwarder icon indicating copy to clipboard operation
vagrant-notify-forwarder copied to clipboard

Port is not freed when used with VMWare Fusion

Open RReverser opened this issue 6 years ago • 1 comments

Whenever I restart my VM, it looks like currently used port is not freed (neither on halt nor on reload), so I'm getting the following error:

Some of the defined forwarded ports would collide with existing
forwarded ports on VMware network devices. This can be due to
existing Vagrant-managed VMware machines, or due to manually
configured port forwarding with VMware. Please fix the following
port collisions and try again:

<currently used port>

After this, each time I have to go to Vagrantfile and manually set/bump config.notify_forwarder.port to a new value to avoid that conflict, and then it works again till the next restart.

RReverser avatar Apr 23 '18 12:04 RReverser

@mhallin Any chance of taking look at this?

RReverser avatar Sep 27 '18 12:09 RReverser