I am kind of banging my head here because i don't understand why a Virtualbox network that I set up with CentOS 7 using a bridged adapter works perfectly fine if I use an Ethernet cable, but if i use WiFi, the network is unreachable.

But my real problem is that I cannot find a way to make it work with WiFi. During the installation process, when you choose a disk, keyboard and etc. I can never establish a connection, wether I use NAT or bridged.

Is this an actual network configuration problem, or just bad installation process?

What I do with this VM is use it's SFTP connection on Windows so I can have a Linux distro to work on, it all works until i unplug that cable.

  • i suppose bridged connection will not always work, but the problem is that if i change to NAT i still can't get any network during installation. – Daniel Jul 28 '18 at 13:49
  • 1
    It is a know limitation and vbox is full of bugs. Hyper V is a slightly better alternative, I prefer VmWare – Rui F Ribeiro Jul 28 '18 at 14:48
  • That is a good tip, i might give one of those a try. I remember a while back, a friend of mine made wifi connection work on VB and also set up a DHCP server because bridged connection was not possible, the source of the problem could be something we might never find it, wether a firewall, a driver or just a virtualization of hardware, issue who knows. My knowledge of networking is on the script kiddie level so this is all confusing to me, thanks for the replies. – Daniel Jul 28 '18 at 14:53
  • On this link the second note is very relevant: virtualbox.org/manual/ch06.html#network_bridged – Daniel Jul 28 '18 at 15:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.