When in tuntap mode, qemu creates a tap device with names like tun0, tun1,
etc. which seems to confuse some users (the smart ones who ask why qemu uses
IP frames instead of ethernet frames ... or something along those lines).
Theses should be named tap0, tap1, etc. This patch fixes qemu.
I don't think this would break anything (correct qemu-ifup scripts shouldn't
care about the name of the tuntap device that qemu uses).
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
--- vl.c.1 Wed Jul 6 19:03:45 2005
+++ vl.c Wed Jul 6 19:04:23 2005
@@ -1629,7 +1629,7 @@
}
memset(&ifr, 0, sizeof(ifr));
ifr.ifr_flags = IFF_TAP | IFF_NO_PI;
- pstrcpy(ifr.ifr_name, IFNAMSIZ, "tun%d");
+ pstrcpy(ifr.ifr_name, IFNAMSIZ, "tap%d");
ret = ioctl(fd, TUNSETIFF, (void *) &ifr);
if (ret != 0) {
fprintf(stderr, "warning: could not configure /dev/net/tun: no virtual
network emulation\n");
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
