From owner-freebsd-current@FreeBSD.ORG Thu Jul 19 23:17:20 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5356916A41B for ; Thu, 19 Jul 2007 23:17:20 +0000 (UTC) (envelope-from redchin@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id CD10913C481 for ; Thu, 19 Jul 2007 23:17:19 +0000 (UTC) (envelope-from redchin@gmail.com) Received: by ug-out-1314.google.com with SMTP id o4so700562uge for ; Thu, 19 Jul 2007 16:17:18 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JqK22chjez7cVQEk86Jck0rx1lmfQDw5axNtAytL3Xh/7SJL2/KYOTPoRlinA36/P0mdu0edAWtVdEXmvHjYLPmdjRXk6FV1idDi2rIH3YCKHzU6laa4q2jTr/ALVpE0crQ+pOOhXT25PVuR1e8MRMo5GG2T8Ade7TFUOmDTPc4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TxXvNpUC44011sL12++Mr38BY3yRhhkDyTgaQC+kVG3C6bPqCWHjLBpO38MseNF/xQhmbqmKkHX2qF6YC5zqThlkcvqDu3v5wGV7VR4p3FTtX8Kca+VnbLtNrACubuDJzMC7FcD8BpaNx63fBrAN8QrOy0XoolVWVw1w2XllRDE= Received: by 10.78.118.5 with SMTP id q5mr871605huc.1184885532761; Thu, 19 Jul 2007 15:52:12 -0700 (PDT) Received: by 10.78.45.18 with HTTP; Thu, 19 Jul 2007 15:52:12 -0700 (PDT) Message-ID: <1d3ed48c0707191552g7f804257ya9f4791ff22ffa36@mail.gmail.com> Date: Thu, 19 Jul 2007 15:52:12 -0700 From: "Kevin Downey" To: "Kevin Oberman" In-Reply-To: <20070719191639.B8A5845045@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <469ED8F1.2070409@errno.com> <20070719191639.B8A5845045@ptavv.es.net> Cc: current@freebsd.org Subject: Re: Problems connecting to public WiFi with latest 80211 code 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: Thu, 19 Jul 2007 23:17:20 -0000 On 7/19/07, Kevin Oberman wrote: > > Date: Wed, 18 Jul 2007 20:22:25 -0700 > > From: Sam Leffler > > > > Kevin Oberman wrote: > > > I had not seen this problem because I do not use the wpa_supplicant to > > > connect to open networks when at home, but I am on travel this week and > > > it has been a real pain. > > > > > > System is current as of this afternoon and is running on a ThinkPad T43 > > > with an Atheros 5212 mini-PCI card. > > > > mac+phy revs for card are always important; dmesg|grep ath > > > > > > > > When the system comes up, the wpa_supplicant starts, but the system > > > never scans except with 'authmode WPA1+WPA2/802.11i privacy ON' and > > > never tries to associate with an open AP even though I have an entry in > > > wpa_supplicant.conf for that network. I have to issue a 'ifconfig > > > wepmode off' to get it to associate. > > > > I don't see a log from wpa_supplicant or console debug msgs as obtained > > with wlandebug. > > > > > > > > Even then, it still won't always associate until I ifconfig the > > > interface down and up. Once I do this, it seems to associate rather > > > quickly. > > > > > > I suspect that the problem reported on mobile by Matthias Apitz and jhb > > > may be a part of the problem, but I think the inability to get to > > > authmode OPEN is different. > > > > > > I use the supplicant at home and it works fine, but that is NOT an open > > > network, so I don't need the interface to run in OPEN mode. > > > > > > Any idea what is going on and if it can be fixed or worked around? > > > > I can't help w/o the usual info: what os, card info (mac+phy), and how > > to reproduce (e.g. wpa_supplicant.conf and cmd line). > > Sorry, this was a really bad report. > > Here is the dmesg part: > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > ath0: mem 0xb4000000-0xb400ffff irq 11 at device 2.0 on pci11 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:14:a4:60:f2:e3 > ath0: mac 5.9 phy 4.3 radio 3.6 > > Do the following: > Boot up a current kernel WITHOUT 'device ath' > kldload if_ath > Interface continues to report 'authmode WPA1+WPA2/802.11i privacy ON' > and never associates. > /etc/rc.d/wpa_supplicant restart ath0 > > This fixes it all. I didn't realize that restarting wpa_supplicant > corrected the problem when I sent the initial message. > > Because of the way this is working, I failed to get anything from > 'wpa_supplicant -d' as any attempt to re-start the supplicant cause > things to work. > > I did run wlandebug and I am attaching the output. The supplicant was > restarted at the point where the DHCP client exited. > > I see the same behavior when I 'boot -s', 'kldload if_ath' and 'exit'. > > Due to an IRQ issue that I have not had time to try to track down, I > can't load it from the loader and I don't want it in my kernel fro a > variety of reasons. > > I might also mention that I am also seeing frequent drops in > associations that are working fine, but this has been reported by > others and so this is just a "me, too". But is annoying. I lost it > twice entering this message. > -- > R. Kevin Oberman, Network Engineer > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0x90000000-0x9000ffff irq 22 at device 1.0 on pci7 I see similar behavior. I get a "ath0: device timeout" message then I lose my connection. If I bounce the interface with '/etc/rc.d/netif restart ath0' ifconfig shows ath0 with 'authmode WPA1+WPA2/802.11i privacy ON' and it no longer associates with my ap. Sometimes if I bounce it a few times it will "unstick" and go back to "authmode OPEN privacy ON" other times it requires a reboot. I am using wpa_supplicant, but not WPA just WEP. 'ifconfig ath0 authmode open' doesn't change anything when its stuck on "authmode WPA1+WPA2/802.11i" This happens a few times a week. -- i'll unhook my oily pink mini-kimono, you kill him in honolulu