search

clong / DetectionLab

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

Solved: Change network in VirtualBox for logger #870

Closed LasseKrache closed 1 year ago

LasseKrache commented 1 year ago

Description of the issue:

Vagrant seems to setup the system "logger" with the wrong network in VirtualBox.

After fixing my first problem (https://github.com/clong/DetectionLab/issues/866) I can't connect from the windows systems to the logger. I noticed know, that the network adapter no.2 is connected to "internal network" only. After switching it manually to "host-only network" it seems, that logger uses the correct ip address (192.168.56.105). But (of course) the necessary services are not started now: fleet, splunk, etc.

My question: how/where can I modify the wrong setting so that the vagrant script connects to the "host-only network"?

(Sorry for this stupid question, but I have never used vagrant before.)

Lasse

LasseKrache commented 1 year ago

Solved it (I guess) with a change in Vagrantfile:

before: virtualbox__intnet: true now: virtualbox__intnet: false