I configured two DHCP-enabled NAT network adapters for a Ubuntu 22.04 Guest OS. But only one network interface gets an IP address correctly and the other does not get one, which is supposed to get from 10.0.2.x/24
Here is the output of the $ip a command.
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:36:c9:00 brd ff:ff:ff:ff:ff:ff
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 08:00:27:d8:09:15 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.6/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s8
valid_lft 533sec preferred_lft 533sec
inet6 fe80::ff06:8c09:d5a4:8ae3/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Is it possible for a single VM to have multiple DHCP-enabled NAT network adapters? If not, why not?
A Single Ubuntun Guest OS with Two DHCP-enabled NAT Networks --> Possible?
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: A Single Ubuntun Guest OS with Two DHCP-enabled NAT Networks --> Possible?
I don't know why they shouldn't both get IP addresses. Let's take a look at the host & VM's settings:
1. 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.)
2. Also, for the host, open a Command Prompt/Terminal and run ipconfig /all for Windows or ip address for Linux. Post the command output.
3. Start the VM from full normal shutdown, not save-state. Run until you see the network problem happen, then shut down the VM from within the VM's OS. Right-click each VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log to the desktop, naming each log so we know which VM it came from. Zip all the logs, and post the zip file, using the forum's Upload Attachment tab.
4. On the host, run these in the command prompt/terminal:
cd "C:\Program Files\Oracle\Virtualbox" < this one only for a Windows host
vboxmanage list natnets
vboxmanage list dhcpservers
1. 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.)
2. Also, for the host, open a Command Prompt/Terminal and run ipconfig /all for Windows or ip address for Linux. Post the command output.
3. Start the VM from full normal shutdown, not save-state. Run until you see the network problem happen, then shut down the VM from within the VM's OS. Right-click each VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log to the desktop, naming each log so we know which VM it came from. Zip all the logs, and post the zip file, using the forum's Upload Attachment tab.
4. On the host, run these in the command prompt/terminal:
cd "C:\Program Files\Oracle\Virtualbox" < this one only for a Windows host
vboxmanage list natnets
vboxmanage list dhcpservers