search

Marshall-Hallenbeck / red_team_attack_lab

Red Team Attack Lab for TTP testing & research
https://github.com/Marshall-Hallenbeck/red_team_attack_lab
GNU General Public License v3.0
541 stars 75 forks source link

Known Issue: Windows hosts sometimes timeout after Vagrant boot and during Ansible provision #2

Open Marshall-Hallenbeck opened 3 years ago

Marshall-Hallenbeck commented 3 years ago

This is an intermittent issue that Windows (10 & 2019) hosts will sometimes just timeout during a Vagrant boot (after changing hostname) or an Ansible provision (specifically after the ADCS installation/configuration).

I'm not sure why this is happening, but the fix for this is just to run vagrant provision $host and it should provision fine.

Unsure why this happens for now.

emaragkos commented 2 years ago

win10-dev failed to join the domain. vagrant provision win10-dev resulted in the same error image win7-1 and metasploitable3-ub1404 seem to fail also image image

Marshall-Hallenbeck commented 2 years ago

@emaragkos that seems unrelated to this issue and unfortunately happens sometimes. Whenever that happened to me I just rebuilt the environment.

jt0dd commented 2 years ago

Any way to solve this on Windows? This whole project seems to run fine from a Windows host except I get the issue described here. But Ansible doesn't work on Windows, so I can't run vagrant provision.

==> dc01: Running provisioner: ansible...
Windows is not officially supported for the Ansible Control Machine.
Please check https://docs.ansible.com/intro_installation.html#control-machine-requirements
    dc01: Running ansible-playbook...
The Ansible software could not be found! Please verify
that Ansible is correctly installed on your host system.

If you haven't installed Ansible yet, please install Ansible
on your host system. Vagrant can't do this for you in a safe and
automated way.
Please check https://docs.ansible.com for more information.

I tried booting in Ubuntu just for this project, bought a flash drive, etc etc, didn't provision enough space on the main disk (have plenty on other disks) and even setting Virtual Box's machine installation location doesn't stop this build pipeline from running out of space on the primary disc.

So frustrated, not feeling like re-installing Ubuntu, I tried it on Windows. I don't see anything about this that shouldn't work on Windows. Everything seems to build, until the Windows loading / booting circle icon shows up and just freezes. Tried removing, re-installing, everything. We also tried DetectionLab and had other issues across multiple boxes. In other words, there doesn't seem to be any reliable project compatible with Windows. So it would be cool if this project would work on Windows instead of having to figure out booting into another OS.

jt0dd commented 2 years ago

I created an issue about this on Vagrant: https://github.com/hashicorp/vagrant/issues/12743

Marshall-Hallenbeck commented 2 years ago

@jt0dd I finally got around to finishing #15 and have Windows instructions here: https://github.com/Marshall-Hallenbeck/red_team_attack_lab/blob/main/docs/windows_setup.md

It's quite finnicky due to WSL being... not the best, but it at least works for me on several different machines.

Marshall-Hallenbeck commented 1 year ago

@jt0dd Were you able to get this running on your side? I have had it running on Windows for a while now, but I'm still running into ADCS issues (working on fixing those now).