Page 1 of 1

Non-existent bridged adapter

Posted: 12. Jul 2015, 20:03
by socratis
I finally bit the bullet and upgraded to 10.9.5 from 10.6.8. So far, so good (iSync and PPC apps do not work, but this is not the forum for this). I did a fresh installation and I migrated my files from my previous system (yes, I did the installation on another drive for safety). Now for the VBox problem/bug:

Since this was a fresh install, OSX renamed my wireless connection from "Airport" to "Wi-Fi". Since all of my VMs include 4 network adapters (Host, Internal, Bridged, NAT), one of which is Bridged to the old "Airport" interface, VBox comes up with a warning during any VM starting that "the following physical network interfaces were not found: Airport". So far, so good... (makes sense if you think about it).
NetworkAdapterNotFound.png
NetworkAdapterNotFound.png (65.43 KiB) Viewed 956 times
BUT, (and here's the bug), when I click on "Change Network Settings", VBox presents me a network settings dialog which comes up ... empty. No adapter is enabled (remember, I have 4 enabled), the network adapter is not attached, the type is the default PCnet-II (no matter the guest adapter), the cable is disconnected, etc.
NetworkSettingsEmpty.png
NetworkSettingsEmpty.png (95.12 KiB) Viewed 956 times
The second part of the "bug" is that if I click on Cancel, the VM starts fine, with all of its network settings untouched. INCLUDING the bridged adapter, which is automagically assigned to "Wi-Fi" and getting IPs and everything is peachy. But it's NOT visible in the settings.

??? Any thoughts ??? Should I file a bug report? I can easily search and replace all the instances of "Airport" to "Wi-Fi" with a simple replace in all of my .vbox files, but that's not the issue.

On a second thought, if anyone is brave enough to try it, you could theoretically edit the .vbox file and change your bridged adapter to something non-existent. Any brave souls out there?

Re: Non-existent bridged adapter

Posted: 12. Jul 2015, 20:06
by socratis
I just noticed in my own post that the tabs are labeled "Adapter 0". All 4 of them...

Re: Non-existent bridged adapter

Posted: 13. Jul 2015, 10:21
by mpack
I assume this is with VBox5? You should certainly raise a bug report. Don't forget the log file.

One thing that would be good to know: yes, you could easily work around this, but can you easily reproduce it (even in a new VM)? I.e. is this a glitch in one .vbox file, or a systemic bug?