From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 00:17:26 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 A66FE16A41C for ; Fri, 17 Jun 2005 00:17:26 +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 7B64043D48 for ; Fri, 17 Jun 2005 00:17:26 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j5H0HPms017588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jun 2005 17:17:25 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42B21790.4060301@errno.com> Date: Thu, 16 Jun 2005 17:21:36 -0700 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: James Snow References: <20050616191450.GA98695@teardrop.org> <42B1D9D9.7040604@errno.com> <20050616200450.GB98695@teardrop.org> <42B1DD17.3000601@errno.com> <20050616204044.GC98695@teardrop.org> <42B1E97B.5070408@errno.com> <20050616210447.GD98695@teardrop.org> <20050616220327.GE98695@teardrop.org> In-Reply-To: <20050616220327.GE98695@teardrop.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: WPA Supplicant doesn't see my SSIDs? 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: Fri, 17 Jun 2005 00:17:26 -0000 James Snow wrote: > Amusing update: > > I got wpa_supplicant to put ath0 into an associated state, but the > moment I send any traffic out over ath0 - e.g., a DHCP request - I'm > promptly disassociated. wpa_supplicant will try to reconnect, dhclient > will keep sending out requests, and after a few iterations of this > process the Cisco Aironets shut off all their wireless networks, > disconnecting all their clients. > > :) > > They're Aironet 1200s running c1200-k9w7-tar.123-4.JA if anyone is > curious. > > Given the instability on that side I wouldn't place too much credence in > any WPA problem reports coming from me for the time being. Sounds like you're using TKIP and the ap detects MIC errors in the frames you are sending. When this happens it is required to enable countermeasures that include dropping traffic for a period of time. Check if your station negotiated WME; there have been problems with using h/w TKIP together with WME that require doing the MIC calculations in s/w. The crypto support in current doesn't have all these changes. If there's no WME negotiated then I'm not sure what to say; TKIP works fine in both h/w and s/w use in all my testing but I brought in a number of fixes (some WPA-related) shortly before the freeze. Sam