From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LlZpK-0005wT-Sx
	for qemu-devel@nongnu.org; Sun, 22 Mar 2009 22:23:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LlZpF-0005vL-GQ
	for qemu-devel@nongnu.org; Sun, 22 Mar 2009 22:23:45 -0400
Received: from [199.232.76.173] (port=57826 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LlZpF-0005vC-AP
	for qemu-devel@nongnu.org; Sun, 22 Mar 2009 22:23:41 -0400
Received: from yw-out-1718.google.com ([74.125.46.156]:49273)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1LlZpF-00072j-23
	for qemu-devel@nongnu.org; Sun, 22 Mar 2009 22:23:41 -0400
Received: by yw-out-1718.google.com with SMTP id 9so1124258ywk.82
	for <qemu-devel@nongnu.org>; Sun, 22 Mar 2009 19:23:40 -0700 (PDT)
Message-ID: <49C6F2AA.40408@codemonkey.ws>
Date: Sun, 22 Mar 2009 21:23:38 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Add pcap-based host network bridge
References: <49C0BFCD.1040304@siemens.com>
In-Reply-To: <49C0BFCD.1040304@siemens.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
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

Jan Kiszka wrote:
> This introduces bridged networking via pcap. Both Unix and Windows
> platforms are supported.
>
> While tap-based bridging provides basically the same support pcap does,
> the latter is often more handy to set up. Under Linux, it doesn't
> require to configure a bridge and it is able to bypass the ebtables if
> this is desired. Also under Windows, the bridge setup can be lengthy
> procedure compared to using the pcap interface.
>
> Signed-off-by: Klaus Wenninger <klaus.wenninger@siemens-enterprise.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>   

The previous version of this had a fundamental flaw wrt guest->host 
communication on Linux.  My understanding was that this was an intrinsic 
limitation of pcap.

That's a blocker IMHO because it will invariably lead to many folks 
asking why ping to the host doesn't work (just like slirp).  Since it 
still requires root privileges, I don't think it improves a lot on tap.

Regards,

Anthony Liguori