Bridged network on Ubuntu is not working

[leon88]

Hi,

I have a Win7 hosts w VBOX 4.3.26. I have installed a Ubuntu on it and configured eth0 for bridged network and my problem is that the guest OS is not getting IP address from my router... after a while (several connection attempts) it looks like finally it gets its IP address but when I try to connect to any webpage it is not working. I thought it maybe a DNS problem, but no, it cannot connect to webpages via ips neither.

Any ideas what is the problem?

thanks

[leon88]

Any ideas? Somebody?

[mpack]

How do you "configure eth0 for bridged" on a Windows host?

The guest OS should not be configured to bridge anything. The VM settings (Network) on the host is where you should configure bridged. VirtualBox does the bridging, the guest sees a normal Ethernet NIC.

You might find it easier to scrap that guest OS and reinstall it.

[leon88]

I did exactly you suggest The OS is freshly installed... i mean the guest one.

Anything else?

[mpack]

Anything else? I don't understand the question. The original post was "bridged network in Ubuntu is not working". If Ubuntu is no longer trying to bridge anything then that issue no longer exists. If your comms still aren't working then you'd need to provide information about the scenario you want me to consider, and what exactly you are trying to achieve.

The normal networking mode for any guest should be NAT - that should be enough for basic internet browsing.

If you need something greater than you can use bridged networking. Typically in that case the guest would be configured to request an IP address assignment automatically, and the network you are bridging to would need some kind of DHCP server on it, i.e. a server or router.

[scottgus1]

Keep in mind, Leon, when folks in the Virtualbox forum say use "NAT" or "Bridged", they are referring to the Virtualbox GUI Network Settings for the guest, not within the guest itself.

[leon88]

Ok, so let me summarize the issue once again, maybe I was not clear.

So I have VBOX 4.3.26 running on Windows 7 host, and installed an Ubuntu virtual machine freshly.
After that I have configured the Networking settings in virtual box (not in Ubuntu) instead of NAT to Bridged network - I know what is the difference.

The question is not that why I don't use NAT (btw the answer is that I want to access the vm over ssh from different computers also ) the question rather is that why Ubuntu is not getting IP address over a bridged virtual box network? I think that is a virtual box bug.

If something is not clear yet please let me know... I would like to solve the issue.

Thanks in advance.

[scottgus1]

Thanks, Leon, for clarifying things. I think what threw us off was this: "configured eth0 for bridged network" Since "eth0" is a Linux way of describing a network card and your host OS is Windows, it sounded like you set the guest network card to bridged inside the guest, whereas the place you have to Bridge the network is in Virtualbox GUI on the host. Thus all the seemingly unnecessary explanations of bridging, NAT, etc.

But you have the guest's network Bridged in Virtualbox: "Networking settings in virtual box (not in Ubuntu) instead of NAT to Bridged network". Good. When the network is Bridged, the guest appears to your network to be another PC on the network, as far as IP addresses and communication go. The guest's IP address comes from the DHCP server on the network (usually a network router in home and small business networks, or a domain controller in a business situation). Is there such a thing in your network?

If you have a working DHCP server, there have been a few network glitches in more recent versions of Virtualbox, starting around 4.3.22 Try either running 4.3.12 as a test, or the test build of 4.3.27 found here: viewtopic.php?f=6&t=66639

One other thing, is your host network a wi-fi card? If so, you should know that some wi-fi card drivers are not written well and don't allow Bridging, meaning Virtualbox's bridging may not work. If you are running wi-fi and have a wired network port on your host you can use, try connecting to the wired one and see if things start working.

[leon88]

Thanks for the help, using LAN instead of WiFi helped... is that (Wifi-bridge) working w 4.3.12 or 4.3.27 by any chance?

[scottgus1]

Only way to know is to try. Fortunately trying only costs time...
The issue with Bridged and wi-fi adapters sems to be the fault of the wi-fi driver. See here: viewtopic.php?f=1&t=56236 for more info

[leon88]

Unfortunatelly, 4.3.12 didn't help, i will try 4.3.27 once it's released.

[scottgus1]

if 4.3.12 didn't work, I would doubt 4.3.27 will. It's likely the wi-fi card's driver, not anything in Virtualbox. Did you check the wi-fi or computer manufacturer's website for new drivers?

[leon88]

Updated my Qualcomm Atheros AR946x to the latest (10.0.0.313) version, didn't help. I need LAN cable to solve this...thanks for help

[scottgus1]

One other thing you can do if you really want wireless and your guest at the same time is to get a USB wireless adapter and use Virtualbox's USB filters to connect the adapter to the guest. The host won't see it while the guest is running, and the host would use its own wireless adapter simultaneously. The guest would see the USB wireless adapter and get its own connection to the network independent of the host.