From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EMX09-0005sc-4z
	for qemu-devel@nongnu.org; Mon, 03 Oct 2005 16:33:33 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EMX05-0005qN-1C
	for qemu-devel@nongnu.org; Mon, 03 Oct 2005 16:33:31 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EMX04-0005lt-He
	for qemu-devel@nongnu.org; Mon, 03 Oct 2005 16:33:28 -0400
Received: from [144.85.15.72] (helo=mail.eclis.ch)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1EMWwQ-0002V0-M6
	for qemu-devel@nongnu.org; Mon, 03 Oct 2005 16:29:42 -0400
Message-ID: <434194AF.9060504@eclis.ch>
Date: Mon, 03 Oct 2005 22:29:35 +0200
From: Jean-Christian de Rivaz <jc@eclis.ch>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] tun/tap networking: patch for existing tun
References: <20050930221321.C7BED31C14@ravel.n2.net>	<20051001131215.GB28444@jbrown.mylinuxbox.org>	<433EF5C4.2030801@eclis.ch>	<Pine.LNX.4.61.0510020441150.21519@filer.marasystems.com>	<433F92CB.1060600@eclis.ch>
	<43402ABC.3040805@us.ibm.com>	<20051002193912.GB13825@jbrown.mylinuxbox.org>	<Pine.LNX.4.61.0510031449500.24889@filer.marasystems.com>	<20051003151425.GC27327@jbrown.mylinuxbox.org>	<43417879.5020106@bellard.org>
	<46d6db660510031222y70cb7257u7f32f823474c8917@mail.gmail.com>
In-Reply-To: <46d6db660510031222y70cb7257u7f32f823474c8917@mail.gmail.com>
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

Christian MICHON a =E9crit :
> to do so, does that mean we would need to launch a 1st qemu
> instance which would contain the dhcp server, and next qemu
> instances would connect to it ?
>=20
> if so, 'qemu -server' and 'qemu -client -connect_to server' could
> be useful...

As I understand and with what I know, you can do that now using a=20
virtual network (VDE for example). What matter is that fact that two=20
qemu instances are connected on the same network. DHCP protocol (like=20
any others netowrk protocol) is over that network and is not visible to=20
qemu.

To do what you wants, you have to use to different operating system=20
image, one that contains a DHCP server, and the second that contain a=20
DHCP client.

1) create a virtual switch: "vde_switch -s /tmp/my_switch.ctl"

2) start a virtual server: "vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda=20
dhcp-server.bin [...]"

3) start a virtual client: "vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda=20
dhcp-client.bin [...]"

--=20
Jean-Christian de Rivaz