From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bedc9-0008Ls-Kw for qemu-devel@nongnu.org; Sun, 27 Jun 2004 13:38:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bedc7-0008Lg-Qd for qemu-devel@nongnu.org; Sun, 27 Jun 2004 13:38:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bedc7-0008Ld-Nr for qemu-devel@nongnu.org; Sun, 27 Jun 2004 13:38:47 -0400 Received: from [38.113.3.51] (helo=snickers.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BedaD-0001LF-8X for qemu-devel@nongnu.org; Sun, 27 Jun 2004 13:36:49 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by snickers.hotpop.com (Postfix) with SMTP id 4CCFC72D71 for ; Sun, 27 Jun 2004 16:33:26 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-3.hotpop.com (Postfix) with ESMTP id 288FAFA41A3 for ; Sun, 27 Jun 2004 17:19:55 +0000 (UTC) Date: Sun, 27 Jun 2004 13:33:45 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] replies Message-ID: <20040627173345.GA32322@jbrown.mylinuxbox.org> References: <20040626184535.GA19123@jbrown.mylinuxbox.org> <200406271007.11404.a_mulyadi@telkom.net> <20040627050111.GA24787@jbrown.mylinuxbox.org> <20040627052132.GA14931@cs.unibo.it> <20040627070453.GA15311@cs.unibo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040627070453.GA15311@cs.unibo.it> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Sun, Jun 27, 2004 at 09:04:53AM +0200, Renzo Davoli wrote: > > Tap would be the more appropriate as entire packets with data-link header > > are exchanged. > I mean, tun or tap are just names, the interfaces within vde or qemu > (AFAIK) are opened as "IFF_TAP" so they are tap even when named tun. > > renzo > If that is the case, then qemu should be naming the devices as "tap0", "tap1", etc. To open a TAP device with the name of "tun0" is just plain confusing. (Unless we want to go "qemu0", "qemu1", etc.) > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.