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

Re: [Xen-users] unstable network problem


  • To: Nivedita Singhvi <niv@xxxxxxxxxx>
  • From: Tim Durack <tdurack@xxxxxxxxx>
  • Date: Wed, 10 Aug 2005 10:16:39 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 10 Aug 2005 14:14:59 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=didPApr8CP8uQcioZ6QZLzXtr/0EOWUcXaLRF4wM1Jh1pltX1q2mURA+S8CZCVdT89ThX3fo9bF8i778nwj1ARY/2XCmtMMxRViRXmBaTK1At5qyqYo4l17kqgo3z9U9QjQ23x4q5HDr9MpQEiNTQi2ZxZSMS7G6w5cmtW+vcqU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Tried "ethtool -K eth0 tx off" for both guest domains (doesn't work in Dom0.)

Still the same problem. The capture shows TCP checksum problems, so I
assume that is the root of the problem.

Tim:>

On 8/9/05, Nivedita Singhvi <niv@xxxxxxxxxx> wrote:
> Tim Durack wrote:
> > txqueuelen didn't work here either.
> >
> > For what it's worth, here's what the capture looks like for Dom0 -> guest:
> 
> For a temporary workaround, could you disable checksumming:
> 
> ethtool -K tx off
> 
> in each domain?
> 
> thanks,
> Nivedita
> 
> 
> > tethereal -i eth0
> > device eth0 entered promiscuous mode
> > Capturing on eth0
> >   0.000000  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [SYN] Seq=0
> > Ack=0 Win=5840 Len=0 MSS=1460 TSV=122820 TSER=0 WS=2
> >   0.002181  192.168.1.2 -> 192.168.1.1  TCP ssh > 59135 [SYN, ACK]
> > Seq=0 Ack=1 Win=5792 Len=0 MSS=1460 TSV=115220 TSER=122820 WS=1
> >   0.003497  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [ACK] Seq=1
> > Ack=1 Win=5840 Len=0 TSV=122820 TSER=115220
> >   0.010001  192.168.1.2 -> 192.168.1.1  SSH Server Protocol:
> > SSH-2.0-OpenSSH_4.1p1 Debian-6
> >   0.010472  192.168.1.1 -> 192.168.1.2  TCP 59135 > ssh [ACK] Seq=1
> > Ack=32 Win=5840 Len=0 TSV=122821 TSER=115221
> >   0.010478  192.168.1.1 -> 192.168.1.2  SSH Client Protocol:
> > SSH-2.0-OpenSSH_4.1p1 Debian-6
> >   0.215968  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Client: Unknown (46)[Unreassembled Packet [incorrect TCP checksum]]
> >   0.635966  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Client: Unknown (46)
> >   1.475967  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Client: Unknown (46)
> >   3.155992  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Client: Unknown (46)
> >   5.466528  192.168.1.2 -> fe:ff:ff:ff:ff:ff ARP Who has 192.168.1.1?
> > Tell 192.168.1.2
> >   5.466572  192.168.1.1 -> 192.168.1.2  ARP 192.168.1.1 is at 
> > fe:ff:ff:ff:ff:ff
> >   6.515988  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Encrypted request packet len=31
> >  13.235996  192.168.1.1 -> 192.168.1.2  SSHv2 [TCP Retransmission]
> > Encrypted request packet len=31
> >
> >
> > Interestingly if I build two guests I can ssh between them just fine.
> >
> > Tim:>
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >
> 
>

_______________________________________________
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®.