Hey,
On Wednesday 18 January 2006 16:27, Jan Niehusmann wrote:
> This very much looks like the bad tcp checksum problem. You can verify
> this with tcpdump -vv, which should show you if the checksum is
> invalid.
Nope, the checksum is OK:
09:11:53.042543 IP (tos 0x0, ttl 64, id 41457, offset 0, flags [DF], length: 
60) 172.16.2.253.2834 > 172.16.2.254.22: S [tcp sum ok] 2415494891:2415494891
(0) win 5840 <mss 1460,sackOK,timestamp 10010 0,nop,wscale 2>
09:11:53.042619 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 60) 
172.16.2.254.22 > 172.16.2.253.2834: S [tcp sum ok] 2400049154:2400049154(0) 
ack 2415494892 win 5792 <mss 1460,sackOK,timestamp 4294909055 
10010,nop,wscale 2>
09:11:53.043082 IP (tos 0x0, ttl 64, id 41458, offset 0, flags [DF], length: 
52) 172.16.2.253.2834 > 172.16.2.254.22: . [tcp sum ok] 1:1(0) ack 1 win 1460 
<nop,nop,timestamp 10010 4294909055>
09:11:53.044739 IP (tos 0x0, ttl 64, id 50300, offset 0, flags [DF], length: 
93) 172.16.2.254.22 > 172.16.2.253.2834: P 1:42(41) ack 1 win 1448 
<nop,nop,timestamp 4294909055 10010>
09:11:53.045249 IP (tos 0x0, ttl 64, id 41459, offset 0, flags [DF], length: 
52) 172.16.2.253.2834 > 172.16.2.254.22: . [tcp sum ok] 1:1(0) ack 42 win 
1460 <nop,nop,timestamp 10010 4294909055>
09:11:53.045262 IP (tos 0x0, ttl 64, id 41460, offset 0, flags [DF], length: 
93) 172.16.2.253.2834 > 172.16.2.254.22: P 1:42(41) ack 42 win 1460 
<nop,nop,timestamp 10010 4294909055>
09:11:53.245937 IP (tos 0x0, ttl 64, id 41461, offset 0, flags [DF], length: 
93) 172.16.2.253.2834 > 172.16.2.254.22: P 1:42(41) ack 42 win 1460 
<nop,nop,timestamp 10061 4294909055>
....
Any other ideas?
Mosu
-- 
LINET Services GbR
Gotenweg 15 Tel.: 0531-280 191 71
38106 Braunschweig Fax.: 0531-280 191 72
http://www.linet-services.de
mailto:info@xxxxxxxxxxxxxxxxx

Attachment: pgpuB7AiQqYDD.pgp
Description: PGP signature

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