From owner-freebsd-mobile@FreeBSD.ORG Thu Aug 10 15:58:45 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6ED0F16A4DE for ; Thu, 10 Aug 2006 15:58:45 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A98243D53 for ; Thu, 10 Aug 2006 15:58:45 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k7AFwhHN082128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Aug 2006 08:58:44 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44DB57B3.6060506@errno.com> Date: Thu, 10 Aug 2006 08:58:43 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.4 (X11/20060724) MIME-Version: 1.0 To: Matthias Apitz References: <20060810120347.GA8048@rebelion.Sisis.de> In-Reply-To: <20060810120347.GA8048@rebelion.Sisis.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: 6.0-REL && iwi && garbaged TCP traffic X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2006 15:58:45 -0000 Matthias Apitz wrote: > Hello, > > I run the above mentioned combination for W-LAN, at home with > WEP and in the office with WPA-PSK. From time to time, very seldom, > I encounter damaged TCP traffic, for example: > > - a mail reaches the next SMTP hop with garbage in the body; > - fetching a page with HTTP brings up a message about 'bad HTTP > request' with some random chars; > - on 'scp' traffic it stops with a message about 'bad MAC addr'; > > Is this a known issue with the iwi driver/firmware? How is it > possible that higher layer (TCP) does not detect this problem > in the TCP-checksum stored in the header? > > Thx in advance for any hint It's a bug fixed since 6.0. Sam