search

clong / DetectionLab

Automate the creation of a lab environment complete with security tooling and logging best practices
MIT License
4.6k stars 980 forks source link

port forwarding issue #39

Closed viris closed 6 years ago

viris commented 6 years ago

Description of the issue:

When doing vagrant up, it stops with this error. Any help appreciated

==> dc: Setting the name of the VM: Vagrant_dc_1515109207844_92456 ==> dc: Fixed port collision for 22 => 2222. Now on port 2200. Vagrant cannot forward the specified ports on this VM, since they would collide with some other application that is already listening on these ports. The forwarded port to 8000 is already in use on the host machine.

To fix this, modify your current project's Vagrantfile to use another port. Example, where '1234' would be replaced by a unique host port:

config.vm.network :forwarded_port, guest: 8000, host: 1234

MHaggis commented 6 years ago

Hi @viris , I ran into the same issue. Each host (all 3 that are built) will prompt this. What worked for me was: Edit the Vagrantfile Change the host port on lines 8 and 9: config.vm.network :forwarded_port, guest: 8000, host: 9431 config.vm.network :forwarded_port, guest: 8412, host: 2393

You will be prompted for WEF and Win10 during the build. Perform the same function and done.

My environment is working 100%. I sadly do not know enough about Vagrant to offer a better solution.

randolpht commented 6 years ago

I adjusted lines 8-9 but still run into the same issues with any host port that I put. Any other suggestions?

clong commented 6 years ago

Port forwarding seems to be a re-occurring issue with Vagrant, and I've never been able to get to the bottom of why it consistently has issues with it for both Virtualbox and VMware. For that reason, I've removed all port forwarding from the Vagrantfile in the latest commit: https://github.com/clong/DetectionLab/commit/f0cc38f8507d2fe689093fc56ae20bac05d44704

Ususally I'm able to fix the issue by doing a vagrant reload <hostname>, but not always.

More on this here: https://github.com/hashicorp/vagrant/issues/8130#issuecomment-272963103

I'm going to go ahead and close this issue since port forwarding is no longer part of the Vagrantfile - thank you for the report!