From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1ELozV-0003r6-5i
	for qemu-devel@nongnu.org; Sat, 01 Oct 2005 17:33:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1ELozK-0003mV-Fa
	for qemu-devel@nongnu.org; Sat, 01 Oct 2005 17:33:47 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1ELozK-0003et-2a
	for qemu-devel@nongnu.org; Sat, 01 Oct 2005 17:33:46 -0400
Received: from [144.85.15.72] (helo=mail.eclis.ch)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1ELojl-0003O9-9F
	for qemu-devel@nongnu.org; Sat, 01 Oct 2005 17:17:41 -0400
Message-ID: <433EFCF3.5070103@eclis.ch>
Date: Sat, 01 Oct 2005 23:17:39 +0200
From: Jean-Christian de Rivaz <jc@eclis.ch>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] tun/tap networking
References: <20050930221321.C7BED31C14@ravel.n2.net>	<20050930230149.GA20433@jbrown.mylinuxbox.org>	<433E44F9.8040501@eclis.ch>	<20051001131215.GB28444@jbrown.mylinuxbox.org>	<433EF063.3080101@eclis.ch>
	<20051001210926.GA553@jbrown.mylinuxbox.org>
In-Reply-To: <20051001210926.GA553@jbrown.mylinuxbox.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
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

Jim C. Brown a =E9crit :
> On Sat, Oct 01, 2005 at 10:24:03PM +0200, Jean-Christian de Rivaz wrote=
:
>=20
>>>And qemu already supports that, via the -tun-fd option.
>>
>>Can you please give me an exemple how to use the -tun-fd option to open=
=20
>>an existing tun (i.e: tun-alice) ? This option only work for already=20
>>opened tap/tun interface as I understand.
>>
>=20
>=20
> I see what you mean now. qemu itself has no direct support for persiste=
nt tuntap
> devices.
>=20
> However, I imagine that one could modify tundev.c or tapdev.c to open a=
 persistent
> tuntap device (by name) and then pass the fd to qemu via -tun-fd. It wo=
uld be
> better if qemu had direct support for them of course.

Where are this tundev.c or tapdev.c files ? I just updated qemu from CVS=20
and I found no files named like this.

jcdr@talla:~/qemu/qemu$ cvs -qz9 update -AdP
? tun2.patch
M qemu-doc.texi
M vl.c
jcdr@talla:~/qemu/qemu$ find . -type f -name "t*dev*"
jcdr@talla:~/qemu/qemu$

--=20
Jean-Christian de Rivaz