Custom Query (16363 matches)
Results (1360 - 1362 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9461 | worksforme | Bridged network stopped working on fedora 15 kernel 2.6.40 | ||
| Description |
I have configured virtual bridge interface (virbr1) using libvirtd for communication between the virtual machines. All the virtual machines are configured with bridged network interface on virbr1. After upgrading to kernel 2.6.40 on fedora 15 (64-bit), bridged networking stopped working on all virtual machines. Reverting back to kernel 2.6.38 fixes the bridged networking. The problem exists for Virtualbox versions 4.0.12 and 4.1.0/4.1.2. |
|||
| #8256 | obsolete | Bridged network: packages shown only from guest to host | ||
| Description |
I'm using VirtualBox 4.0.2 (r69518) on Ubuntu Lucid (64bit, kernel: 2.6.32-27-generic) host. The guest is an Ubuntu based os. (64bit, kernel: 2.6.22), has one network adapter, which is bridged (PCnet-FAST III). The eth0 interface on host is in promiscuous mode. When I send 'ping' from host to guest or from guest to host, on the host tcpdump shows only the incoming packets, although on guest it shows packages in both directions. I've read a similar problem in bug #8076, and applied the patch to file VBoxNetFlt-linux.c, but the patch did not correct the problem, moreover now on the guest os too: tcpdump does not show packages from guest to host. Using VirtualBox 3.2.12 (r68302) this problem not exists, packages from both directions are shown. |
|||
| #5949 | fixed | Bridged networking broken in Virtualbox 3.1.2 for Windows 2003 R2 host (similar: Ticket #5924) | ||
| Description |
After upgrading from VirtualBox 3.1.0 to 3.1.2 (no further system changes) the bridged network has broken.
Related:
Config:
Problem:
|
|||

