From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MQiSe-0004CQ-FV
	for qemu-devel@nongnu.org; Tue, 14 Jul 2009 09:54:24 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MQiSZ-0004Br-Fl
	for qemu-devel@nongnu.org; Tue, 14 Jul 2009 09:54:23 -0400
Received: from [199.232.76.173] (port=58138 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MQiSZ-0004Bo-CC
	for qemu-devel@nongnu.org; Tue, 14 Jul 2009 09:54:19 -0400
Received: from fwil.voltaire.com ([193.47.165.2]:52774 helo=exil.voltaire.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <ogerlitz@voltaire.com>) id 1MQiSY-0000AC-OF
	for qemu-devel@nongnu.org; Tue, 14 Jul 2009 09:54:19 -0400
Message-ID: <4A5C8DFD.6070804@voltaire.com>
Date: Tue, 14 Jul 2009 16:54:05 +0300
From: Or Gerlitz <ogerlitz@voltaire.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] net: add raw backend
References: <Pine.LNX.4.64.0907011844470.32248@zuben.voltaire.com>	<20090701162115.GA4555@shareable.org>
	<4A4CA747.1050509@Voltaire.com>	<20090703023911.GD938@shareable.org>
	<4A534EC4.5030209@voltaire.com>	<20090707145739.GB14392@shareable.org>
	<4A54B0F1.3070201@voltaire.com>
In-Reply-To: <4A54B0F1.3070201@voltaire.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Jamie Lokier <jamie@shareable.org>
Cc: Herbert Xu <herbert.xu@redhat.com>, Jan Kiszka <jan.kiszka@web.de>, qemu-devel@nongnu.org

Or Gerlitz wrote:
> Jamie Lokier wrote:
>> The problem is simply what the guest sends goes out on the network 
>> and is not looped backed to the host network stack, and vice versa [...]
> I wasn't sure to follow if your example refers to the case when 
> networking uses the bridge or NAT. If its bridge, then through which 
> bridge interface the packet arrives the host stack? say you have a 
> bridge whose attached interfaces are tap1(VM1), tap2(VM2) and 
> eth0(NIC), in your example did you mean that the host IP address is 
> assigned to the bridge interface? or you were referring a NAT based 
> scheme?
Hi Jamie,

Can you comment on my email?

Or.