Hello:
Total newbie here trying to set up a pentest lab. Read a few related threads but still cannot figure out what is wrong
I'm Using a Win10 Host with two Linux VM (one Kali, one target) using VirtualBox, trying to set up an internal network for the two VMs to communicate. Tried using Win10 Host CLI to enter Vboxmanage DHCP string but vboxmanage was not recognized, so I added vbox to the path:
SET PATH=%PATH%;C:\Program Files\Oracle\VirtualBox (which seemed to work after running vboxmanage)
Then entered:
vboxmanage dhcpserver add --netname testnetwork --ip 10.10.10.1 --netmask 255.255.255.0 --lowerip 10.10.10.2 --upperip 10.10.10.12 --enable
Not sure if it worked, but there was no error message
Then went into each VM setting set network to internal with netname of testnetwork, full promiscuity, no cable connected.
Used ifconfig in Kali but no ip info was returned:
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 08:00:27:db:96:6a txqueuelen 1000 (Ethernet)
RX packets 10 bytes 3420 (3.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 65 bytes 11725 (11.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Not sure if the network was actually established or if the problem is the VM network settings. Any advice would be greatly appreciated. Thanks!
DHCP internal network problems
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: DHCP internal network problems
1. Please run these command in the host command prompt, and provide the output:
vboxmanage list dhcpservers
vboxmanage list intnets
2. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
3. Go to C:\Users\{youraccount}, and zip & post the '.Virtualbox' folder (note the period in the name) using the forum's Upload Attachment tab.
4. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)
vboxmanage list dhcpservers
vboxmanage list intnets
2. Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.
3. Go to C:\Users\{youraccount}, and zip & post the '.Virtualbox' folder (note the period in the name) using the forum's Upload Attachment tab.
4. Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. Zip the VM's .vbox file (not the .vbox-prev file), and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)