From owner-freebsd-net@FreeBSD.ORG Sat Feb 24 16:48:38 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5603616A402 for ; Sat, 24 Feb 2007 16:48:38 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: from smtpout04-04.prod.mesa1.secureserver.net (smtpout04-04.prod.mesa1.secureserver.net [64.202.165.199]) by mx1.freebsd.org (Postfix) with SMTP id 32B9F13C491 for ; Sat, 24 Feb 2007 16:48:37 +0000 (UTC) (envelope-from Stephen.Clark@seclark.us) Received: (qmail 10497 invoked from network); 24 Feb 2007 16:48:37 -0000 Received: from unknown (24.144.77.243) by smtpout04-04.prod.mesa1.secureserver.net (64.202.165.199) with ESMTP; 24 Feb 2007 16:48:37 -0000 Message-ID: <45E06C64.6010705@seclark.us> Date: Sat, 24 Feb 2007 11:48:36 -0500 From: Stephen Clark User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeremie Le Hen References: <20070224151549.GJ2479@obiwan.tataz.chchile.org> In-Reply-To: <20070224151549.GJ2479@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: TCP connection stalls on LAN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stephen.Clark@seclark.us List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Feb 2007 16:48:38 -0000 Jeremie Le Hen wrote: >Hi, > >I'm running a quite recent -CURRENT. > >I don't understand what's happening. According to tcpdump(1) it seems >the two peers both keep acknowledging the same segment for ever. >(See the file attached.) > >The peer is a Linksys router that have worked correctly for a while. >The problem arises only with it, I can successfully connect to a >NetBSD and a Windows host. > >I've attached the dump output. Feel free to ask me for more infos. > >Note that automatic TCP socket buffer sizing is disabled (the same >happens when enabled). I've also disabled rxcsum and txcsum on >my network adapter to narrow the possible sources of the problem. > >Regards, > > >------------------------------------------------------------------------ > >09:14:57.593729 IP (tos 0x0, ttl 64, id 27791, offset 0, flags [DF], proto: TCP (6), length: 64) 192.168.1.3.56556 > 192.168.1.1.80: S, cksum 0xe59c (correct), 487760288:487760288(0) win 65535 >09:14:57.597224 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) 192.168.1.1.80 > 192.168.1.3.56556: S, cksum 0xe603 (correct), 2303804549:2303804549(0) ack 487760289 win 5792 >09:14:57.597306 IP (tos 0x0, ttl 64, id 2460, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x2a62 (correct), 1:1(0) ack 1 win 260 >09:14:57.601590 IP (tos 0x0, ttl 64, id 48542, offset 0, flags [DF], proto: TCP (6), length: 488) 192.168.1.3.56556 > 192.168.1.1.80: P 1:437(436) ack 1 win 260 >09:14:57.602390 IP (tos 0x0, ttl 64, id 26779, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0x108d (correct), 1:1(0) ack 437 win 6432 >09:14:57.605968 IP (tos 0x0, ttl 64, id 26780, offset 0, flags [DF], proto: TCP (6), length: 308) 192.168.1.1.80 > 192.168.1.3.56556: P 1:257(256) ack 437 win 6432 >09:14:57.613414 IP (tos 0x0, ttl 64, id 26781, offset 0, flags [DF], proto: TCP (6), length: 1500) 192.168.1.1.80 > 192.168.1.3.56556: . 257:1705(1448) ack 437 win 6432 >09:14:57.613465 IP (tos 0x0, ttl 64, id 38624, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x21fb (correct), 437:437(0) ack 1705 win 254 >09:14:57.816442 IP (tos 0x0, ttl 64, id 26782, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0x09c4 (correct), 1704:1704(0) ack 437 win 6432 >09:14:57.816489 IP (tos 0x0, ttl 64, id 4315, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x212a (correct), 437:437(0) ack 1705 win 260 >09:14:58.236395 IP (tos 0x0, ttl 64, id 26783, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0x08cf (correct), 1704:1704(0) ack 437 win 6432 >09:14:58.236448 IP (tos 0x0, ttl 64, id 48004, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x1f86 (correct), 437:437(0) ack 1705 win 260 >09:14:59.076354 IP (tos 0x0, ttl 64, id 26784, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0x06d7 (correct), 1704:1704(0) ack 437 win 6432 >09:14:59.076403 IP (tos 0x0, ttl 64, id 4302, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x1c3e (correct), 437:437(0) ack 1705 win 260 >09:15:00.756298 IP (tos 0x0, ttl 64, id 26785, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0x02e7 (correct), 1704:1704(0) ack 437 win 6432 >09:15:00.756344 IP (tos 0x0, ttl 64, id 47006, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x15ae (correct), 437:437(0) ack 1705 win 260 >09:15:04.116021 IP (tos 0x0, ttl 64, id 26786, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.1.80 > 192.168.1.3.56556: ., cksum 0xfb06 (correct), 1704:1704(0) ack 437 win 6432 >09:15:04.116068 IP (tos 0x0, ttl 64, id 63692, offset 0, flags [DF], proto: TCP (6), length: 52) 192.168.1.3.56556 > 192.168.1.1.80: ., cksum 0x088e (correct), 437:437(0) ack 1705 win 260 > > > > looks like the 1500 byte packet is not making it thru the network. Lower your mtu and see if this helps. Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson)