RE: [Xen-devel] xen0=2.6.7 network problem in xenU (SOLVED)

[James Harper <JamesH@xxxxxxxxxxxxxxxx>]

a tcpdump in dom0 doesn't show any packets coming out of the vif interfaces. Not even the arp requests. The packet counts don't increment when I sent packets, although they do otherwise increment occasionally but I don't know why.

 

if i do a flood ping (ping -f), i get lots of dots but obviously it doesn't know the mac address (actually it does sometimes because it can listen and so hears some arp responses). If I add in the mac address manually, i get about 14 dots and then nothing. almost like it's filling up a queue somewhere and then stops.

 

Are you able to reproduce this at all? i'm not able to test it for a few days and I don't need ipv6 anyway.

 

James

---

From: Ian Pratt
Sent: Tue 24/08/2004 7:43 AM
To: James Harper
Cc: Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] xen0=2.6.7 network problem in xenU (SOLVED)

> I probably should clarify, I can't get xenU to talk on the network in any way (it listens but doesn't talk) when xen0 has the ipv6 module loaded.
> 
> simply having the ipv6 module there in dom0 seems to break things

What happens if you run "tcpdump -ni vifX.X" in domain 0. Do you
see any packets being sent from the other domain?

What about packet count statistics if you do "ifconfig vifX.X"?
Does the receive count go up? Are there any errors or drops?

It's really hard to imagine how either our netfront or netback
drivers could not be totally transparent to protocol.

ebtables or bridge code has to be the prime suspect. This will be
confirmed if the tcpdump'ing the vif shows packets. 

If packets aren't showing up, try enabling the debug printf's in
netback/common.h and netfront.c

Ian