From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DqJKR-0002Ek-MD
	for qemu-devel@nongnu.org; Wed, 06 Jul 2005 19:29:20 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DqJKN-0002C0-At
	for qemu-devel@nongnu.org; Wed, 06 Jul 2005 19:29:16 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DqJJn-0001e4-So
	for qemu-devel@nongnu.org; Wed, 06 Jul 2005 19:28:40 -0400
Received: from [128.8.10.162] (helo=po0.wam.umd.edu)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DqJ6r-0005eA-42
	for qemu-devel@nongnu.org; Wed, 06 Jul 2005 19:15:17 -0400
Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180])
	by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j66N8gae021564
	for <qemu-devel@nongnu.org>; Wed, 6 Jul 2005 19:08:43 -0400 (EDT)
Date: Wed, 6 Jul 2005 19:08:42 -0400
From: "Jim C. Brown" <jma5@umd.edu>
Message-ID: <20050706230842.GA14066@jbrown.mylinuxbox.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="C7zPtVaVf+AK4Oqc"
Content-Disposition: inline
Subject: [Qemu-devel] make qemu use tap0 instead of tun0
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="vl.c.patch"

--- 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");

--C7zPtVaVf+AK4Oqc--