search

clong / DetectionLab

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

Failed to fix the broken static IP for eth1. Exiting because this will cause problems with other VMs. #835

Open rcegan opened 2 years ago

rcegan commented 2 years ago

I'm trying to build the lab using Virtualbox on a headless Ubuntu Linux VM. After running vagrant up (and verifying all green ticks in prepare.sh), I'm getting the following error from logger while bootstrap is running:

    logger: [+] python3-pip was successfully installed!
    logger: Incorrect IP Address settings detected. Attempting to fix.
    logger: [02:19:45]: Failed to fix the broken static IP for eth1. Exiting because this will cause problems with other VMs.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I've searched some of the previous issues but not able to find anything directly relevant. I've also tried creating a dummy eth1 network device with ip as my VM doesn't have one, and same issue.

hosniadnane commented 2 years ago

Hello,

just encountered the same issue with virtualbox, while using the latest version on detectionlab and virualbox.

hosniadnane commented 2 years ago
  • Operating System Version: Ubuntu 20.04.4 LTS
  • Deploying via (VirtualBox/VMWare/AWS/Azure/ESXi): Virtualbox
  • Vagrant Version (if applicable): 2.2.19

I'm trying to build the lab using Virtualbox on a headless Ubuntu Linux VM. After running vagrant up (and verifying all green ticks in prepare.sh), I'm getting the following error from logger while bootstrap is running:

    logger: [+] python3-pip was successfully installed!
    logger: Incorrect IP Address settings detected. Attempting to fix.
    logger: [02:19:45]: Failed to fix the broken static IP for eth1. Exiting because this will cause problems with other VMs.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I've searched some of the previous issues but not able to find anything directly relevant. I've also tried creating a dummy eth1 network device with ip as my VM doesn't have one, and same issue.

just did : vagrant reload logger --provision, and the issue has been solved.

clong commented 1 year ago

I just ran into this as well and I'm not totally sure why it's happening occasionally. I added a debug line to output what the script thinks the eth1 IP address is in a newer commit

security-companion commented 1 year ago

I had the same issue, another vagrant up solved the issue for me