Page 1 of 1

Only bridge available when "Add a New Network" in lab

Posted: Mon Dec 23, 2024 1:13 pm
by rkoloj
Hello all. I have a unique problem I have been googling and getting nowhere. I recently updated my motherboard to a ASUS TUF Gaming Z790-Plus WIFI. It has an Ethernet NIC Intel(R) Ethernet Controller I226-V. I have previously used VMWare Workstation 14 for my EVE-NG VM, and upgraded to 17. I have not updated the EVE-NG VM in any way since upgrading Workstation.

I did run into an issue where EVE told me that there was some compatibility error or something when I turned the VM on.
intel error.png
So I did the following:
Make sure any Windows feature relating to Hyper-V or Hypervisor Platform(s) are turned off.

Disable Memory Integrity/VBS settings: Windows Security -> Device Security -> Core Isolation and turn off the "Memory Integrity" slider

Disable any Hyper-V activity by launching a command prompt as administrator and executing bcdedit /set hypervisorlaunchtype off
I cannot connect a node (Linux VM) in my lab to the internet. The only choice I have when creating a Network Node is ONLY Bridged. There is NO Management(cloud 0), pnet1, pnet2, etc. Here is a screenshot of "ADD A NEW NETWORK" in EVE:
wlconYT.png
Troubleshooting I have tried.


-I have check Virtual Network Editor and VMNet0 is set to Automatic (But I only chose the physical NIC I226-V that I'm using)

-I can ping google.com from the Eve-NG VM

-My eth0 on Eve VM has an IP 192.168.1.105, which is the web GUI for EVE. My home network PC which is on the I226-V NIC is on the 192.168.1.0/24 network

Please help!

Re: Only bridge available when "Add a New Network" in lab

Posted: Mon Dec 23, 2024 9:54 pm
by rkoloj
Can someone help please?

Re: Only bridge available when "Add a New Network" in lab

Posted: Tue Dec 24, 2024 8:38 am
by Uldis (UD)
It is because you edited and deleted content of interfaces file !
Re-install EVE and dont touch it anymore

Re: Only bridge available when "Add a New Network" in lab

Posted: Tue Dec 24, 2024 12:44 pm
by rkoloj
Thanks Uldis. To anyone reading this, I ran these commands to do fresh setup. The fix is as follows:
rm -f /opt/ovf/.configured
su -
This allowed me to gain access to the interface again.