[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] bridge and tcpdump



2008. 09. 17, szerda keltezÃssel 17.40-kor rmarfisi@xxxxxxxxx ezt Ãrta:
> i have a problem with bridge
> 
> i can create a bridge, ant it work fine
> i have a 
> bridge with 3 domU and they can ping any other
> 
> but when i run 'tcpdump -n' in 
> for example dom1 and do ping from dom2 to dom3
> tcpdump don't capture anithing
> 
> 
> why?

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


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.