NAT and Bridged adapter

[gmanigault]

I am running Centos 7 host and Ubuntu 16.04.2 LTS. I have several VM's which are running. I can set them up to use NAT and they have full access to the network and the internet. If i set it up with Bridged adapters then all network access and internet access is lost. My current version of Virtualbox is 5.0.32 r112930. The only other thing I should add is that this is being done over wifi access point which I have total control over. I am wondering if I were wired tot he network if that would be different? I will try that and add more here later.

Now if I run dhclient -v p3p1 and it wil do a dhcpdiscover over the network. It will fail if you are using Bridged Adapters but NAT but succeeds and gets offered and ip. There seems to be a lot of chatter about this issue. I am assuming there is a bug in the app on this issue? Can anyone confirm this? If there is when and will there be a fix and what is the fix?


GWShark

[socratis]

If i set it up with Bridged adapters then all network access and internet access is lost... this is being done over wifi access point

Bridged and wireless don't always play nice. Bridged networking is outside the WLAN specification. Bridging to wireless is not really bridging. The guest shares the MAC of the host and the host does a sort of MAC-NAT translation based on IP addresses. Promiscuous mode doesn't exist in the official WLAN specifications. It may or may not work. Some combinations of Routers/Access Points, WLAN cards and drivers work, some don't. See: Bridging & Wifi - Supported hardware and add your experience. For example, it works fine in my home, but not in my office. Same laptop, same VM. Try to see if it works either with Bridged over wired.

For a more detailed, more technical explanation, with a potential workaround, please read comment #19 from "vushakov" in ticket #10019.

There seems to be a lot of chatter about this issue.

Not really, the problem and its explanation are quite clear as far as I know, over several posts on the forums.

I am assuming there is a bug in the app on this issue?

The problem, if you've read so far, is not with VirtualBox.

what is the fix?

A new router, an updated WiFi driver or a combination of these two. Unfortunately it occurs at a level that VirtualBox has no control over.