search

clong / DetectionLab

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

DC Network Adapter (missing) issue #170

Closed DonMVB closed 5 years ago

DonMVB commented 5 years ago

On the DC - there are no network adapters, even though they are visible from the VBox menu, settings menus, in Device Manager, etc. Meaning that Windows dev manager identifies 2 ethernet controollers but neither of the are identified and get IP addresses (IPconfig returns no results). When I run a "vagrant reload dc" AFTER I changed the NIC to an Intel 1000 MT nic, same problem, even though the base VM boots properly and sees the NIC, and the NIC gets addresses on the LAN.

Or to put another way - by default w/ no intervention, the DC image does not get functional network adapters. When I change the network adapters to something that works (intel 1000 mt), the vagrant reload dc command appears to reset the NIC to a non-working one, "paravirtualized nic", and the end result of that is no IP addresses are defined so the DC can't "talk" on the network.

DonMVB commented 5 years ago

I also went into the Vagrantfile, and set the NIC to one of the Intel types following the Vagrant article here: https://www.vagrantup.com/docs/virtualbox/configuration.html

When the DC books, the Windows network icon has a red indicator, there is no network adapter to configure in the Network Connections dialog.

I get an error saying "the vm has entered a paused" state. Very odd, that.

Cyb3r-Monk commented 5 years ago

I had the same problem and solved by the same steps as you did. for example, for win10: (you should do it for every machine except logger. logger is OK without this parameter)

cfg.vm.provider "virtualbox" do |vb, override|
  vb.gui = true
  vb.name = "win10.windomain.local"
  vb.default_nic_type = "82545EM"
vdog90 commented 5 years ago

I had the same problem and setting the default_nic_type as described above fixed the problem.

clong commented 5 years ago

@mergene @vdog90 did either of you reproduce this problem with Virtualbox on Windows? I'm testing it now and seeing both adapters:

image

clong commented 5 years ago

Hey folks - can anyone who is experiencing these issues chime in with:

And possibly provide a debug log for via vagrant up dc --debug &> vagrant_up_dc_debug.log

I'm unable to repro on my CI build environment, but it sounds like multiple people are having this issue.

dmi3mis commented 5 years ago

Operating System Version: Windows 10 1803 Provider (VirtualBox/VMWare): VirtualBox 5.2.22 (latest) Vagrant Version: 2.2.1 (recently updated, last successful build was 2.1.8) Packer Version: 1.2.4 Is the issue reproducible or intermittent? Reproducible

I repro exacly this issue. DC was built with virtio-net network adapters. Inside of VM there is no drivers for it. Oracle VM VirtualBox Guest additions v5.2.16 is installed inside a vm.

screenshot_38

vagrant_up_dc_debug.log

PS: Recently i has updated your repo. ( I see that you had added vb.default_nic_type = "82545EM" in Vagrantfile) Problem has been gone.

clong commented 5 years ago

Fixed in https://github.com/clong/DetectionLab/commit/52faea3e67e7cfa0eed0029fec4e760d9348b131