Virtualbox problem with network bridge in guest os.

[Dalak]

I apologize for my English, translate it through Google)

Virtualbox problem with network bridge in guest Windows.
I have a laptop with a wifi adapter Killer AX1650.
In the Virtualbox program, the network bridge does not work through the Wifi adapter, the address from the router is not issued, everything is fine through Ethernet, the address is issued.

System:
Linux 19.2 Mate
Kernel - 4.15.0-72-generic
Virtualbox-tried version 5.2.18 - 6.0
PS. Addresses are issued through VMware. But I do not want to use them.

I also have an old laptop and there is a version of Virtualbox 5.1.18 and addresses are issued via cable and wifi.

I can’t understand what the problem is.

[scottgus1]

Bridged may not always work with a Wifi adapter, due to strict implementation of the Wifi protocols by either the wifi adapter driver or the access point firmware. Technically Wifi cannot Bridge, but some combinations of wifi adapter drivers and access point firmware implement these protocols in a lax fashion so Bridged can squeeze through. If it works where you are, good.

Your old laptop's wifi driver has lax wifi standards, so Bridged was able to work. The new laptop's wifi driver has stricter wifi standards, so it stops Bridged.

If you can't get a good network trying to Bridge with a wifi adapter, there are a couple choices you have available, depending on if you want full on-the-LAN access for the guest, just internet, or internet and access to the host PC storage only:

1. For full on-the-LAN access, use wired Ethernet, or get a USB wi-fi adapter for the guest to use.

2. For internet in the guest while wifi-connected, use NAT or 'NAT network'.

3. For host storage access, add another network card to the guest, set to Host-Only.

[Dalak]

The trick is that when I moved the system from an old laptop to a new one through Timeshift.
The first time it turned out and I received the address through Wifi.
Everything was good for 2-3 weeks. Then Something happened and gives out the address through Virtualbox more.
In Vmware, everything works according to configured interfaces (vmnet bridge), and therefore I assume that the problem is in Virtualbox.
I installed different systems, Elementary OS installed the drivers, nothing has changed.
On Windows, everything works too.

[socratis]

PS. Addresses are issued through VMware. But I do not want to use them.

What does that mean? Why is VMware involved here, what's your setup exactly?

[Dalak]

PS. Addresses are issued through VMware. But I do not want to use them.

What does that mean? Why is VMware involved here, what's your setup exactly?

Virtualbox Settings:
wlp3s0 - wifi adapter
enp5s0 - Ethernet

The first 2 photos are a connection via Wifi
There is no internet due to the fact that it can not get the address from the router.

wlp3s0 Linux Host

imgonline-com-ua-CompressBySize-9p4mkDR36vtg2.jpg (116.65 KiB) Viewed 4263 times

[scottgus1]

Dalak, your pictures did not come through. Use the forum's Upload Attachment tab. Crop & resize to get under the 128kB size limit. PNG is best. the [img] tags are only for images you have previously uploaded via Upload Attachment.

If the image is an error message or text command output, posting the text is better than an image. Text is translatable, searchable, and quotable.

[Dalak]

Dalak, your pictures did not come through. Use the forum's Upload Attachment tab. Crop & resize to get under the 128kB size limit. PNG is best. the [img] tags are only for images you have previously uploaded via Upload Attachment.

If the image is an error message or text command output, posting the text is better than an image. Text is translatable, searchable, and quotable.

Thanks changed.

And add another photo, because the restriction is 3 photos per message
The next 2 photos are Ethernet. It receives the address from the router.

enp5s0 Linux Host

imgonline-com-ua-CompressBySize-9p4mkDR36vtg4.jpg (124.38 KiB) Viewed 4262 times

enp5s0 Virtualhost

imgonline-com-ua-CompressBySize-9p4mkDR36vtg3.jpg (123.44 KiB) Viewed 4262 times

[Dalak]

To the question "why is VMware involved here," I answer that everything works there, like the network bridge on Wifi and Ethernet.

wlp3s0 In Vmware

imgonline-com-ua-CompressBySize-9p4mkDR36vtg5.jpg (124.19 KiB) Viewed 4262 times

[socratis]

'scottgus1' already told you, but here's one more time...

Bridged over wireless don't always play nice. Bridged networking is outside the WLAN specification. 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.

[Dalak]

Well, then the question is why does everything work on Windows?

[socratis]

I'm sorry, what do you mean "everything is working in Windows"? Which Windows, your Guest?

[Dalak]

I'm sorry, what do you mean "everything is working in Windows"? Which Windows, your Guest?

I have 2 linux and windows systems on my laptop.
I mean that in windows, virtual machines accept dhcp addresses from the router (wifi and ethernet) no matter which guest machine is installed in virtualbox.

If you use linux, then dhcp addresses are not accepted via wifi, statics too, addresses are accepted via ethernet.
The router is one.

[scottgus1]

We would not be able to say why Bridging over Wi-fi allegedly works with VMware but doesn't with Virtualbox. We tend to be somewhat Virtualbox-centric on these forums for some strange reason, and we may not be all that conversant in VMware. Perhaps VMware does their Bridging differently? Just a guess.

in windows, virtual machines accept dhcp addresses from the router (wifi and ethernet)...If you use linux, then dhcp addresses are not accepted via wifi,

This does sound different than what was originally posted:

In the Virtualbox program, the network bridge does not work through the Wifi adapter, the address from the router is not issued...Addresses are issued through VMware.

The first report says no IP addresses come through Virtualbox Bridged over Wi-fi. The second report says Bridged over Wi-Fi works to Windows guests but not to Linux guests. (Edit: I see another interpretation of this second report, see below) Looking up earlier there is a place where you mention that Windows guests are getting IP addresses.

There's a substantial difference between these two reports. Could be a language issue. I note that the Windows guests screenshots are in Cyrillic script.

But taken as written, either Virtualbox Bridged over Wi-fi is not working at your location, or it is working in Windows guests but not in Linux guests. You will need to clarify this conundrum.

Since you're already introducing vlans into the situation, it could be possible that something got messed up. I would definitely have messed something up trying to set up a vlan. I barely even know what a vlan is.

If you want to troubleshoot this in a way that clears any possibilities of user-induced oddities, start with a fresh Linux guest install. Let the New Guest Wizard set everything up and don't change anything in the guest settings. Don't do anything to the guest OS networking, no vlans, leave the OS on its default dynamic IP address, etc. Totally untouched. See if Bridged over Wi-fi gives it an IP address.

[scottgus1]

I have 2 linux and windows systems on my laptop.

Reading your last post again, I see another interpretation:

You have a dual-boot laptop, with Windows and Linux OS's.

When booting to Windows, the Virtualbox guests get IP addresses over Wi-fi.

When booting to Linux, the Virtualbox guests do not get IP addresses over Wi-fi.

First, you will need to explain things more clearly, and identify if the OS having trouble is the physical 'host' PC OS or it is installed in a virtual machine 'guest'.

Second, that Bridged over Wi-fi apparently works in Windows but not in Linux goes exactly to what Socratis and I have been pointing out:

Bridged may not always work with a Wifi adapter, due to strict implementation of the Wifi protocols by either the wifi adapter driver or the access point firmware.

Some combinations of Routers/Access Points, WLAN cards and drivers work, some don't.

There's different drivers between Linux and Windows. If the Linux driver is strict but the Windows driver is lax, then Bridged over Wi-fi will be dead in Linux and working in Windows.

[Dalak]

The first report says that through the Virtualbox Bridged via Wi-Fi does not receive IP addresses.

Via Virtualbox, connected via Wi-Fi, IP addresses are accepted on the host Linux main host, but not on the guest host.

The second report states that Bridged over Wi-Fi works for Windows guests, but not Linux guests.

In the main Windows host, dhcp addresses are issued to all guest machines.

If you look up, there is a place where you mention that Windows guests get IP addresses.

Not on guest machines, but on the main host where virtualbox is installed

If you want to troubleshoot in such a way as to eliminate any opportunities that users may have, start with a new Linux guest installation. Let the new guest’s master set everything up and change nothing in the guest’s settings. Do not do anything with the guest OS network, without vlans, leave the OS at its default dynamic IP address, etc. Completely untouched. See if Bridged over Wi-Fi gives an IP address.

I installed a clean Linux Mint 19.2 system because Linux Mint 19.1 did not want to detect ethernet in live cd mode.
I installed the driver as indicated on the website of the manufacturer of the Wi-Fi adapter. This did not solve the problem.
I tried to install different Linux kernels, it also did not work.