biggiesmallsAG / nightHawkResponse

Incident Response Forensic Framework
599 stars 139 forks source link

Lack of interfaces #18

Open Gaz494 opened 7 years ago

Gaz494 commented 7 years ago

Hi,

I cannot access the web interface on nightHawk from my analysis machine. I have checked in the settings of the VM, and when running ifconfig -athe only interface it returns is lo. I currently have 3 nics assigned to the VM.

I have tried to activate the interfaces with ifup eth0 yet this returns the message

no suitable device found for this connection

Any help you could give would be greatly appreciated.

Gaz

Gaz494 commented 7 years ago

After speaking to some people on the CentOS support forum, it's an issue that CentOS deprecated loads of ethernet cards. The way to get this working in VMWare is to modify the config file "ServerName.vmx" Add a new line at line 15 and add ethernet0.virtualDev = "e1000"

This has resolved the issue and I now have a working eth0 and can access the web console.

biggiesmallsAG commented 7 years ago

wow good find sir.. im assuming you were setting the adapter to VMXnet adapter before? if not which were you trying?

Gaz494 commented 7 years ago

It was set as default, so can only imagine it was on VMXnet. There wasn't an entry for ethernetN.virtualDev in the nighthawk.vmx file at all, simply adding it in resolved the issue.

AliLazy commented 7 years ago

I also stuck on same point. can you please share actual entry for nighthawk.vmx.

Gaz494 commented 7 years ago

The exact entry is posted above, with details of which line to put it in.