Closed coffeegist closed 2 years ago
Hi @coffeegist - I think you may be able to use fix-second-network.ps1 to assign an address to the interface you create, but yeah, it looks like it's not possible to do via the Vagrantfile in Big Sur.
However, also realize a lot of the IPs in the lab are hardcoded to those values to take the guesswork out of DNS and DHCP reservations from my end. Changing IP addresses will more than likely break stuff - it's a tradeoff I had to make between flexibility and stability.
A bit more history on this here: https://github.com/clong/DetectionLab/issues/269
My work around:
VNET_1_HOSTONLY_SUBNET
from /Library/Preferences/VMware Fusion/networking
VNET_1_HOSTONLY_SUBNET
within the Vagrant directorycfg.vm.network :private_network, ip: *
with cfg.vm.network :private_network
only in Vagrantfilescripts/fix-second-network.ps1
to assign static IP within VNET_1_HOSTONLY_SUBNET
Change list of files:
modified: Vagrantfile modified: logger_bootstrap.sh modified: resources/guacamole/user-mapping.xml modified: scripts/configure-ou.ps1 modified: scripts/install-microsoft-ata.ps1 modified: scripts/install-osquery.ps1 modified: scripts/install-splunkuf.ps1 modified: scripts/install-velociraptor.ps1 modified: scripts/join-domain.ps1 modified: scripts/provision.ps1
Added as a wishlist item: https://www.detectionlab.network/customization/feature_requests/
Hi all,
I failed to understand that this issue crops up even on brand new installs of VMware fusion. I thought this was only happening for people who were trying to run DetectionLab on custom (e.g. not 192.168.56.x/24) subnets. However, the good news is that I have a fix! This happens is if there is no pre-existing VMNET adapter mapped to the 192.168.56.x network -- the fix is simply to create one. On MacOS:
In this example, I'll be creating a vmnet2 interface, but if you already have one, change "2" to a different number (e.g. 7).
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_7_DHCP no
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_HOSTONLY_SUBNET 192.168.56.0
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_HOSTONLY_NETMASK 255.255.255.0
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_VIRTUAL_ADAPTER yes
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
I just tested this and it seems to be working great. Sorry for the misunderstanding!
Hi all,
I failed to understand that this issue crops up even on brand new installs of VMware fusion. I thought this was only happening for people who were trying to run DetectionLab on custom (e.g. not 192.168.56.x/24) subnets. However, the good news is that I have a fix! This happens is if there is no pre-existing VMNET adapter mapped to the 192.168.56.x network -- the fix is simply to create one. On MacOS:
In this example, I'll be creating a vmnet2 interface, but if you already have one, change "2" to a different number (e.g. 7).
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_7_DHCP no sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_HOSTONLY_SUBNET 192.168.56.0 sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_HOSTONLY_NETMASK 255.255.255.0 sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cfgcli vnetcfgadd VNET_2_VIRTUAL_ADAPTER yes sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --configure sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start
I just tested this and it seems to be working great. Sorry for the misunderstanding!
I guess first line VNET_7 is a typo, otherwise works great
Description of the issue:
When bringing the machines up, while "Verying vmnet devices are healthy", the following error is generated:
To clarify, VMWare Fusion version is 12.1.0. I believe it's related to this issue: https://github.com/hashicorp/vagrant/issues/12052
A work around can be found here: https://www.vagrantup.com/docs/providers/vmware/known-issues#big-sur-related-issues
Modifying all
cfg.vm.network
lines in the Vagrantfile allows things to stand up. Example below:However, the obvious issues here are that static IPs don't seem possible at a first glance