From owner-freebsd-net@FreeBSD.ORG Sat Feb 24 15:13:59 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 2793116A40B for ; Sat, 24 Feb 2007 15:13:59 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id BB96513C4B9 for ; Sat, 24 Feb 2007 15:13:58 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 68D1535B77 for ; Sat, 24 Feb 2007 16:13:57 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id DCDBB9BE05 for ; Sat, 24 Feb 2007 15:15:49 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id BDBC84087; Sat, 24 Feb 2007 16:15:49 +0100 (CET) Date: Sat, 24 Feb 2007 16:15:49 +0100 From: Jeremie Le Hen To: freebsd-net@FreeBSD.org Message-ID: <20070224151549.GJ2479@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="d8Lz2Tf5e5STOWUP" Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: TCP connection stalls on LAN X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 15:13:59 -0000 --d8Lz2Tf5e5STOWUP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > --d8Lz2Tf5e5STOWUP Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="tcp.dump" 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 --d8Lz2Tf5e5STOWUP--