From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 04:39:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C07C16A41F for ; Wed, 20 Jul 2005 04:39:08 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE0B343D45 for ; Wed, 20 Jul 2005 04:39:07 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.94] ([66.127.85.94]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j6K4cVms027099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 19 Jul 2005 21:38:47 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42DDD568.4030706@errno.com> Date: Tue, 19 Jul 2005 21:39:04 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Johann Hugo References: <20050719094905.F15510@fledge.watson.org> <42DCC637.2050103@FreeBSD.org> <200507191212.36044.jhugo@icomtek.csir.co.za> In-Reply-To: <200507191212.36044.jhugo@icomtek.csir.co.za> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Recent fragility with if_wi, 802.11 adhoc/wep, and Tiger 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: Wed, 20 Jul 2005 04:39:08 -0000 Johann Hugo wrote: > On Tuesday 19 July 2005 11:21, Alex Dupre wrote: > >>Robert Watson wrote: >> >>>I fairly regularly use 802.11 adhoc with WEP to communicate between my >>>6.x/7.x FreeBSD notebook using if_wi, and my Apple PowerBook running Mac >>>OS X Tiger. A few days ago, when I updated from a June to a July HEAD >>>revision, this became quite "fragile". >>>I was wondering if anyone else has seen this problem, though. >> >>I have a (not so) similar problem with my atheros based D-Link DWL-G650 >>card with late CURRENTs. The problem is very strange: I can connect >>stablily to my neighbor's 11g wireless network (even if the signal is >>lower than my D-Link DI-624 AP) and I hardly can connect to my AP. When >>it happens, the connection goes down after few seconds (no carrier) and >>I cannot reconnect anymore. This used to work with older current (about >>a month ago). I though the AP was broken, but I have a 11b device (voip >>phone) that can connect without problems (yes, I tried to connect the >>card in 11b mode, w/ & w/o wep, but it's the same). >>Anyone seeing this? > > > I am also getting problems with my atheros cards. When the connection goes > down I'm seeing a lot of "rx failed 'cuz of PHY err" and "CCK timing" errors. wi != ath I cannot tell if you're operating in adhoc mode as you've provided no details. Last note I recall from you regarded ap mode operation. > > lab3# athstats > 8894 tx management frames > 5 tx frames discarded prior to association > 887 tx failed 'cuz too many retries > 13077 long on-chip tx retries > 7 tx frames with no ack marked > 9969 rx failed 'cuz of bad CRC > 138910 rx failed 'cuz of PHY err > 138888 CCK timing > 22 CCK restart > 1 beacons transmitted > 39 periodic calibrations > 1180 rate control checks > 25 rate control dropped xmit rate > rssi of last ack: 15 > avg recv rssi: 44 > 1 switched default/rx antenna > Antenna profile: > [1] tx 7720 rx 29817 > [2] tx 292 rx 37 > > With tcpdump -y IEEE802_11 I can see the packets, but without -y IEEE802_11 > there is nothing. "1 beacons transmitted" is very odd. Is your athstats out of sync w/ the driver? Try providing basic info if you want help. Sam