Opened 11 years ago
Closed 10 years ago
#12077 closed defect (fixed)
Ubuntu 12.04 Guest fails to get IP Address from NAT, Bridged Adapter works fine
| Reported by: | capitrium | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 4.2.16 |
| Keywords: | NAT, DHCP, Ubuntu 12.04 | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
Running VirtualBox v4.2.16 on Windows 7 x64 Home Edition, with an Ubuntu Server 12.04 guest using a single Network Adapter attached to NAT, the guest fails to get an ip address.
I am able to set a static ip from within the guest to the default that it should be getting via DHCP, however this appears to be entirely superficial since the guest still boots without a full networking configuration, hence I am still unable to get an internet connection.
It is worth noting that using a Bridged Adapter works perfectly fine, both via DHCP and with a static ip. See https://forums.virtualbox.org/viewtopic.php?f=6&t=57211 for additional details.
Attachments (6)
Change History (10)
by , 11 years ago
| Attachment: | LATIUM-2013-09-06-23-04-11.log added |
|---|
by , 11 years ago
| Attachment: | ifconfig-static.log added |
|---|
ifconfig -a with manually configured static ip
comment:2 by , 11 years ago
Replying to Hachiman:
What is output of ifconfig -a for your guest in NAT mode?
I've attached the output of ifconfig -a with the interface configured for both dhcp and a static ip.
I was originally having this issue on VB 4.1.16, and after upgrading to 4.2.16 the behaviour is slightly different. When configured using a static ip, I ran a few ping commands to prove that the connection wasn't working when it should have been; I've attached the output of these commands as well. The first two commands were ping -c 5 www.google.ca and ping -c 5 8.8.8.8 (Google's DNS). Both of these commands failed to resolve Google's address and reported 100% packet loss, which is exactly what I expected given the bug I seem to have encountered.
I then ran the same commands directing the output to a log file, as I forgot to do this the first time I ran them. The ping -c 5 www.google.ca command had the same result, however ping -c 5 8.8.8.8 ended up successfully sending and receiving all packets! Not sure why it didn't work the first time, but I thought I'd add this extra info to the bug report.
comment:3 by , 11 years ago
Is this still an issue with recent 4.3? Works for me on both Windows and Linux hosts.
VM log session