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/
Home Products Support Community News


RE: [Xen-devel] Re: VIF Interfaces not transparent to all ethernet proto

To: "Armin Kemper" <Armin.Kemper@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: VIF Interfaces not transparent to all ethernet protocols?
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 12 Nov 2004 08:28:09 -0000
Delivery-date: Fri, 12 Nov 2004 08:53:54 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Thread-index: AcTIjSoLQaMJdKzvQxC/afBjb6cyDwAA09kA
Thread-topic: [Xen-devel] Re: VIF Interfaces not transparent to all ethernet protocols?
> eth0 is the interface I used for connecting to the lan, I can 
> see packets passing, if I do that.
> If I do 'tcpdump -i eth1' I can see the PPPoE packets inside 
> domain 1, too.
> If I put an IP address on that interface in domain 1 and ping 
> something on that subnet, I see exactly the same output on
> tcpdump -i eth1    in domain 1
> and
> tcpdump -i vif1.1  in domain 0
> but not for PPPoE traffic FROM domain 1, the other direction 
> works fine.

This does point toward either the netfront/back dropping the traffic,
but it's rather unlikely that this would happen without one of the
error/drop counters being bumped. 

Perhaps the easiest way of tracking this down would be to add some
tracing to the receive interrupt of netback. printk a "*" whenever a
packet is received and see if it gets that far. If not, add something to
the start_xmit function in netfront.


This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
Xen-devel mailing list