Obtaining wireless connection inside VirtualMachine/VirtualBox

[Bee La]

I am currently using VirtualBox in a corporation that has network restrictions, and everything goes through a proxy.

The Attempts I have made:
- manually configured the proxies manually through VirtualBox's preferences.
- adding a Host-only Network
- Changing VirtualBox settings Network Adapter 1 to Bridged adapter and "Allow All" with desktop adapter type and Cable Connected checked
- Manually added the proxies inside the virtual machine itself.
- Using Ubuntu and RedHat (With CentOS)
- Tried using CentOS GUI to connect through wirelessly (but cannot click on wireless tab)

--- Though this list may seem small, this has been an issue that has taken over 24 hours.

[Bee La]

Log:

[scottgus1]

Virtualbox emulates only wired ethernet cards for your guests to use. You can only get an actual Wi-Fi adapter in your guest if you buy a USB Wi-Fi adapter and use the Virtualbox USB filters to insert the USB Wi-Fi adapter into your guest instead of the host.

[Bee La]

So the only solution to this is to have a USB that connects to my physical computer and have the VM use it?
There has to be a wireless method... Because USBs are not allowed at my company.

[socratis]

There has to be a wireless method...

None that we know of. Unless you know something that we don't, the answer is no.

[scottgus1]

If you can explain why you need Wi-Fi, we may be able to offer a different solution.

[Bee La]

Well... What if we were trying to connect to the company's LAN? would that still require a USB wifi adapter?

[Bee La]

I don't know if I particularly need WIFI, but I'm trying to install certain Apache software that uses Linux (so that I may code some things), but cannot do so because the VM has no network connections.

[scottgus1]

You will need a network in your guest. Here's Socratis' famous VirtualBox network table:

• +-----------+-------------+-------------+----------------+----------------+
  |           | VM <-> Host | VM1 <-> VM2 | VM -> Internet | VM <- Internet |
  +-----------+-------------+-------------+----------------+----------------+
  | HostOnly  |     Yes     |     Yes     |      No        |       No       |
  | Internal  |     No      |     Yes     |      No        |       No       |
  | Bridged   |     Yes     |     Yes     |      Yes       |       Yes      |
  | NAT       |     No      |     No      |      Yes       |  Port forward  |
  | NATService|     No      |     Yes     |      Yes       |  Port forward  |
  +-----------+-------------+-------------+----------------+----------------+

Compare the kind of connection you want and find a setting that will accomplish it. Also see section 6 in the manual. Note that if your company's IT has locked down your network you may have to convince them why a Virtualbox guest on your work PC is needed. Then they can open the network to the guest.

[Bee La]

Thank you both, I will research more into Bridge Adapters in the manual and hope for the best.

[socratis]

To me from the little of your description about your actual project, it seems that you need internet access (in the VM) to be able to download/install/update Apache and the other parts of the project. For that you could have one adapter in the VM tied to NAT.

After that, you need access from your host only to access the VM. For that you could have a second adapter in the VM tied to HostOnly.

And you could forget all about Bridged, for which given your description about company policies, might be difficult to have an unknown computer in the network. I mean you don't even allow USB devices. you would allow an unknown computer?