WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

R: Re: [Xen-users] bridge and tcpdump

To: <nice@xxxxxxxxxxxxxxx>, xen <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: R: Re: [Xen-users] bridge and tcpdump
From: "rmarfisi@xxxxxxxxx" <rmarfisi@xxxxxxxxx>
Date: Wed, 17 Sep 2008 18:10:26 +0200 (CEST)
Cc:
Delivery-date: Wed, 17 Sep 2008 09:11:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: "rmarfisi@xxxxxxxxx" <rmarfisi@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>If you listen on dom1 and the ping dom3 from dom2 then you mustn't see
>that 
traffic, because xen networking is not based on virtual hubs (which
>simly 
relay every packet to every port), but it's based on virtual
>switches, and 
switches intelligently forward the packets, only for the
>recipient. In this 
case dom1 is neither the sender nor the recipient

thank
if i want capture all 
traffic form a domU, how to do it?


>Try to listen on dom2 (e.g. with "tcpdump 
-n -i eth0") and then ping
>dom2 from dom3. Now you should really see 
something.

yes, i osserved it in the past

thanks a lot for yours attenction

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>