From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Drh51-0005ij-14
	for qemu-devel@nongnu.org; Sun, 10 Jul 2005 15:03:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Drh4z-0005hr-5T
	for qemu-devel@nongnu.org; Sun, 10 Jul 2005 15:03:06 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Drh0J-0003uh-Kn
	for qemu-devel@nongnu.org; Sun, 10 Jul 2005 14:58:15 -0400
Received: from [209.204.185.216] (helo=gate.bitblocks.com)
	by monty-python.gnu.org with esmtp
	(TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1Drge0-00031L-6v
	for qemu-devel@nongnu.org; Sun, 10 Jul 2005 14:35:12 -0400
Received: from bitblocks.com (localhost [127.0.0.1])
	by gate.bitblocks.com (8.13.3/8.13.1) with ESMTP id j6AIRg2F038020
	for <qemu-devel@nongnu.org>; Sun, 10 Jul 2005 11:27:43 -0700 (PDT)
	(envelope-from bakul@bitblocks.com)
Message-Id: <200507101827.j6AIRg2F038020@gate.bitblocks.com>
Subject: Re: [Qemu-devel] Connecting vde and LAN 
In-reply-to: Your message of "Sun, 10 Jul 2005 18:42:30 +0200."
	<Pine.LNX.4.61.0507101834520.9759@filer.marasystems.com>
Date: Sun, 10 Jul 2005 11:27:42 -0700
From: Bakul Shah <bakul@BitBlocks.com>
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

> DHCP is Ethernet broadcast based, not IP.

Not that it matters in this case but strictly speaking DHCP
is an IP protocol, using UDP as its transport and the request
goes to IP broadcast address of 255.255.255.255.

> You could also run a local DHCP server on tap0, configured with the 
> address scope you have set up proxy-arp for.

You can run a local DHCP server and NAT.

On FreeBSD I assign an IP address like 172.20.0.1 to the
*bridge* interface on the host on startup so that samba and
dhcpd can bind to it.  When qemu is started /etc/qemu-ifup
makes the new tap device a bridge member.  I imagine Linux
has something similar....