From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 16:58:17 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 514C21065670 for ; Mon, 8 Mar 2010 16:58:17 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 051B78FC14 for ; Mon, 8 Mar 2010 16:58:16 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id o28GwNwF007883; Mon, 8 Mar 2010 16:58:23 GMT (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id ixf7bt487enwntw3f6vx7pkmf2; Mon, 08 Mar 2010 16:58:22 +0000 (UTC) (envelope-from kientzle@freebsd.org) Message-ID: <4B952CEC.7000501@freebsd.org> Date: Mon, 08 Mar 2010 08:59:24 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16 MIME-Version: 1.0 To: Luigi Rizzo References: <4B9425C4.5060309@freebsd.org> <07C6C4E7-3512-4003-BDDE-DEDB549F6EA8@mac.com> <20100308075733.GA24644@onelab2.iet.unipi.it> In-Reply-To: <20100308075733.GA24644@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "'freebsd-current@freebsd.org'" Subject: Re: Wireless TCP aborts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Mar 2010 16:58:17 -0000 Luigi Rizzo wrote: > On Sun, Mar 07, 2010 at 03:08:38PM -0800, Chuck Swiger wrote: >> Hi, Tim-- >> >> On Mar 7, 2010, at 2:16 PM, Tim Kientzle wrote: >> [ ... ] >>> Corrupted MAC on input. >>> Disconnecting: Packet corrupt >>> rsync: connection unexpectedly closed ... [receiver] >>> >>> and then the rsync session is dead. >>> >> It's not TCP ... SSH adds it's own layer of data integrity checking ... >> > > long ago, with the 'iwi' driver, there was the following problem > leading the the sae problem you are seeing: > > the driver was doing WEP in software, and wrote back the result to > the original mbuf (actually, cluster). As a result, the first > transmission of a segment was correct, but in case a rxmt, data > would be encrypted twice, and the remote ssh end detected the garbage > and dropped the connection. This was fixed with Sam's help > around early 2007 if i remember well. > > An easy way to see if it is a similar problem is use ipfw to drop > some packets e.g. > ipfw add 100 prob 0.1 deny tcp out xmit wi0 // use your interface name I'll do some experimenting. Here are some more details on the current setup in case this rings any bells for anyone: * Sender: FreeBSD 8-CURRENT r193146, bge driver bge0: mem 0xe0800000-0xe080ffff irq 17 at device 0.0 on pci63 * Router: D-Link 655 * Receiver: FreeBSD 9-CURRENT r201154, ath driver ath0: mem 0x55200000-0x5520ffff irq 18 at device 0.0 on pci3 ath0: AR2425 mac 14.2 RF5424 phy 7.0 The wireless side is using WPA2-PSK. Tonight I'll try hooking up a wired connection to the receiver and see if that changes anything. Tim