It's my first post here and to be honest I haven't read all topics to be sure that my problem hasn't been discussed yet.
In the latest VirtualBox version (5.0. 10 r104061) I can no longer bridge adapters that don't have the TCP/IP protocol enabled.
Basicly, until this version I was allowed for example to disable the TCP/IPv4 protocol and connect to a Wireless network without an IP address being assigned to the Host, and select the adapter from the dropdown and get an IP address in the Guest.
In the last version, if I disable the TCP/IPv4 from the Hosts Adapter Setting (in Windows), I no longer see the adapter in dropdown - therefore I can no longer bridge it (and get an IP only in guest, not in host).
Is there a way to solve this issue easily?
Or - are the developers aware of this bug? ('cause it's a bug, not a feature )
/*
Meanwhile I found a go-around:
1. Enable TCP/IP to the Host adapter, connect to wireless network, get a host IP
2. Select the WiFi Adapter as bridged.
3. Start the guest machine, let the guest get an IP from the network.
4. Go back in host, disable TCP/IPv4
(but when you restart/save the machine, it won't start again b/c it won't find the adapter anymore).
*/
...but still - bit tricky. I don't understand why the host adapter shouldn't be displayed if it doesn't have TCP/IP enabled.
[Additional info: Windows 7 Host, Windows 8 Guest]
