Custom Query (16363 matches)
Results (1366 - 1368 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9512 | obsolete | Bridged networking problem with 4.1.2 | ||
| Description |
Running ClearOS as a virtual gateway, nic 1 controlled by guest and connects to internet, nic 2 is bridged for local network and host connections. I currently have no computers connected to nic 2 except the host. Under vbox 4.0.12 host could connect to internet without issues. Under vbox 4.1.2 host connection is only available if another computer is connected to nic 2 as well. Only workaround I've found so far is to revert back to version 4.0.12. host: OpenSUSE 11.4, kernel version 2.6.37.6-0.7-Desktop guest: ClearOS 5.2 sp 1 (based on Centos Linux distro) |
|||
| #17186 | fixed | Bridged over WiFi networking: no IP assigned on Win hosts, with a variety of guests/WiFi cards. => Fixed in SVN | ||
| Description |
A variety of Windows Hosts report failure in getting the Bridged over WiFi to successfully get an IP address. The same setup works fine with any 5.1.x VirtualBox version, even 5.1.30 that was released 2 days before 5.2.0. Reporters have been using any Windows version from Win7 to the latest fast-ring pre-release of Win10. Guests can be virtually anything, so can be the affected WiFi cards. The only common denominator seems to be a Windows host and VirtualBox 5.2.0. The VBox.log shows absolutely no signs of anything going wrong. Almost identical logs between successful 5.1.30 runs and failed 5.2.0 runs. I believe that lower level debugging must be enabled, if the developers cannot reproduce the issue (highly unlikely). More about the discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=85083 |
|||
| #14404 | invalid | Bridged to wifi failure | ||
| Description |
Im having an issue where my Guest VM's lost the ability to connect to the default gateway or beyond, when using a bridged to wifi adapter. (NAT still works as expected). I can access (tried ping) to other guest's on the the same (bridged) network, as well as the host OS on the same network. This used to work, but stopped at some point in time for unknown reasons. I can reproduce it with VirtualBox 4.3.28, 4.3.30 and 5.0 (havent tried other releases). The guest OS is CentOS 7 in all cases. My host is Windows 8.1. NB: After some troubleshooting, including a manual install of a debug build of 5.0 (r101573), I am now at a point with a regular 5.0 install where I can create new guest vm's with a bridged to wifi adapter that works as expected, while the older guest vm's bridged to wifi adapter still fail. Also, see these two threads on the mailing list for more details : https://www.virtualbox.org/pipermail/vbox-dev/2015-July/013335.html https://www.virtualbox.org/pipermail/vbox-dev/2015-August/013366.html |
|||

