Custom Query (16363 matches)
Results (2356 - 2358 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7649 | fixed | bridged networking does not work starting with 2.6.36 on TAP-devices => Fixed in SVN | ||
| Description |
As you can read on http://amailbox.org/mailarchive/linux-netdev/2010/10/23/6288128/thread VBox stops working with bridged Networking and TAP devices since 2.6.36. I don't think VBox.log will help you much, the only thing which might help is that transmits are ok, but recv is completely dead. A short test with #include <fcntl.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sys/ioctl.h>
#include <sys/stat.h>
#include <sys/types.h>
#include <net/if.h>
#include <linux/if_tun.h>
int main(int argc, const char **argv)
{
struct ifreq ifr;
char *p;
int fd;
if (argc < 2) {
fprintf(stderr, "Need tun name\n");
return EXIT_FAILURE;
}
fd = open("/dev/net/tun", O_RDWR);
if (fd < 0) {
perror("open");
return EXIT_FAILURE;
}
memset(&ifr, 0, sizeof(ifr));
ifr.ifr_flags = IFF_TAP | IFF_NO_PI;
p = strncpy(ifr.ifr_name, argv[1], sizeof(ifr.ifr_name) - 1);
if (ioctl(fd, TUNSETIFF, &ifr) < 0) {
perror("ioctl");
return EXIT_FAILURE;
}
while (true)
sleep(3600);
return EXIT_SUCCESS;
}
results in a positive fix. I think the problem is, that vboxnetflt simply transmits via skb->dev=tapX and doesn't open the tap/tun fd. The upstream (kernel) patch is suboptimal for vbox in a way that it actually needs to open the file descriptor - otherwise the interface has status NO-CARRIER and packets will not be accepted by core kernel. |
|||
| #3750 | fixed | bridged network hangs the second guest | ||
| Description |
Vbox 2.2 on linux (ubuntu) host: |
|||
| #1847 | fixed | bridge networking on Mandriva fails on reboot | ||
| Description |
The system is Mandriva 2008.1 x86_64, using vbox 1.6.2. The problem is during boot. The vbox0 device fails. The error is vbox0 doesn't exist. There is a device created named vbox??, whose suffice varies. The "cure" seems to be to remove the unwanted/unneeded vbox?? and the vbox0 files from /etc/sconfig/network-scripts. Remove the vbox0 line from interfaces. Run VBoxAddif for vobx0, restart the network. The same error is reproduced on a different machine running 2008.1, but is only 32 bit. |
|||

