[Fixed] 5.2.0 Bridged fails w/ only VBox Bridged Driver selected (#17543)

Discussions related to using VirtualBox on Windows hosts.

Re: 5.2.0 Bridged fails w/ only VBox Bridged Driver selected

Postby msabin » 6. Dec 2017, 02:23

Running: Version 5.2.2 r119230

I'm able to get it to work on a repeatable basis:
Turn IPv4 on for the WLAN NIC on the host
Start Virtualbox
Set guest NIC to wired bridge
Start guest
Confirm guest has IP address on wired network
Change guest NIC to WLAN bridged
Confirm guest has new IP address in WLAN (may have to reset the adapter from the guest's OS)
Disable IPv4 for the WLAN NIC on the host

After that sequence the guest will work correctly even through a restart, the sequence must be repeated each time Virtualbox starts.
msabin
 
Posts: 13
Joined: 26. Oct 2017, 22:41

Re: 5.2.0 Bridged fails w/ only VBox Bridged Driver selected

Postby socratis » 6. Dec 2017, 07:20

These kinds of problems that are reproducible, should be reported to the bug tracker. Either search for an appropriate bug, or open a new bug report where you'll attach your logs and other vital information.

It would also help if you can post the bug report number here so other can see the progress, add information, or see the final resolution.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 17090
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: 5.2.0 Bridged fails w/ only VBox Bridged Driver selected (#17543)

Postby socratis » 15. Feb 2018, 10:49

If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 17090
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: [Fixed] 5.2.0 Bridged fails w/ only VBox Bridged Driver selected (#17543)

Postby socratis » 17. Apr 2018, 22:22

Problem is fixed with the release of 5.2.10.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 17090
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Re: [Fixed] 5.2.0 Bridged fails w/ only VBox Bridged Driver selected (#17543)

Postby HazardTugs » 29. Apr 2018, 00:28

I'm still struggling with this issue, despite having installed 5.2.10:

- Intel Dual Band Wireless AC-8265 - latest driver
- Only NDIS Bridged Adapter selected

Symptoms are as described by others: Wireshark traces on the host show DHCP requests coming from the guest, but these DHCP requests are never received by the DHCP server.

I've tried the following:

- Installing the latest development version of Virtualbox
- Completely uninstalling the NDIS driver and Virtualbox, and reinstalling.

I haven't yet tried installing Virtualbox 5.1, or enabling IPv4 on the wifi adaptor, and then subsequently disabling it.

Any hints gratefully received. I can provide logs if needed.
HazardTugs
 
Posts: 4
Joined: 29. Apr 2018, 00:24

Re: [Fixed] 5.2.0 Bridged fails w/ only VBox Bridged Driver selected (#17543)

Postby socratis » 29. Apr 2018, 01:18

Please open a new thread, do not hijack other people's threads, especially if they're marked as [Fixed].

We're going to need a complete VBox.log, from a complete VM run:

  • Gathering the necessary information:
    1. Start the VM from cold-boot (not from a paused or saved state).
    2. Observe the error.
    3. Shutdown the VM (force close it if you have to).
  • With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".

  • Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
socratis
Site Moderator
 
Posts: 17090
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

Previous

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 35 guests