From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Qyoe7-0006ge-Ov for garchives@archives.gentoo.org; Wed, 31 Aug 2011 17:32:16 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F2DD021C121; Wed, 31 Aug 2011 17:32:03 +0000 (UTC) Received: from mail-ey0-f171.google.com (mail-ey0-f171.google.com [209.85.215.171]) by pigeon.gentoo.org (Postfix) with ESMTP id 7F60B21C0FB for ; Wed, 31 Aug 2011 17:30:58 +0000 (UTC) Received: by eyg24 with SMTP id 24so828448eyg.16 for ; Wed, 31 Aug 2011 10:30:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=4E1+pZunw36DsQ7ZPxk4UBf+7Not6N8oLU2+dVHUt40=; b=Bx7Byl/pRpPZJefkQvADDQHXfHkBx3kiH5U2NHxnFkbL43vgDaZkHZN759DX1FpaWE N2KptJWFYO+5TlIMyRy0HHyq6xC+fAuNM6S6c10+TYY7NBkeSYFedv9rIu/BJObyjCBV PxK1BefwzVC8vcWr/0dViu8Mw2xHcL4mSk+n8= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.2.75 with SMTP id 51mr392033eee.196.1314811857629; Wed, 31 Aug 2011 10:30:57 -0700 (PDT) Received: by 10.14.95.75 with HTTP; Wed, 31 Aug 2011 10:30:57 -0700 (PDT) Date: Wed, 31 Aug 2011 10:30:57 -0700 Message-ID: Subject: [gentoo-user] Wireless: deauthenticating by local choice From: Grant To: Gentoo mailing list Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: X-Archives-Hash: a913af8760d6014736c35f55be194868 I'm on the road connecting to various wireless access points and sometimes I'm unable to connect and I get the (try 1) (try 2) (try 3) (timed out) messages in dmesg which makes sense. Other times I get a different series of messages in dmesg when I'm unable to connect which don't make sense to me. The interface connects, then disconnects, then connects, then disconnects, over and over until it finally decides to fail permanently. I can run iwconfig throughout this process and see that the interface periodically becomes fully associated with a good bitrate. I've tried iwconfig and wicd. The log looks like this: wlan2: authenticate with 40:4a:03:d2:f5:71 (try 1) wlan2: authenticated wlan2: associate with 40:4a:03:d2:f5:71 (try 1) wlan2: RX AssocResp from 40:4a:03:d2:f5:71 (capab=0x471 status=0 aid=2) wlan2: associated wlan2: deauthenticating from 40:4a:03:d2:f5:71 by local choice (reason=3) cfg80211: Calling CRDA to update world regulatory domain wlan2: authenticate with 40:4a:03:d2:f5:71 (try 1) wlan2: authenticated wlan2: associate with 40:4a:03:d2:f5:71 (try 1) wlan2: RX AssocResp from 40:4a:03:d2:f5:71 (capab=0x471 status=0 aid=2) wlan2: associated wlan2: deauthenticated from 40:4a:03:d2:f5:71 (Reason: 7) cfg80211: Calling CRDA to update world regulatory domain wlan2: authenticate with 40:4a:03:d2:f5:71 (try 1) wlan2: authenticated wlan2: associate with 40:4a:03:d2:f5:71 (try 1) wlan2: RX AssocResp from 40:4a:03:d2:f5:71 (capab=0x471 status=0 aid=2) wlan2: associated wlan2: deauthenticating from 40:4a:03:d2:f5:71 by local choice (reason=3) cfg80211: Calling CRDA to update world regulatory domain wlan2: authenticate with 40:4a:03:d2:f5:71 (try 1) wlan2: authenticated wlan2: associate with 40:4a:03:d2:f5:71 (try 1) wlan2: RX AssocResp from 40:4a:03:d2:f5:71 (capab=0x471 status=0 aid=2) wlan2: associated wlan2: deauthenticated from 40:4a:03:d2:f5:71 (Reason: 7) cfg80211: Calling CRDA to update world regulatory domain wlan2: authenticate with 40:4a:03:d2:f5:71 (try 1) wlan2: authenticated wlan2: associate with 40:4a:03:d2:f5:71 (try 1) wlan2: RX AssocResp from 40:4a:03:d2:f5:71 (capab=0x471 status=0 aid=2) wlan2: associated wlan2: deauthenticating from 40:4a:03:d2:f5:71 by local choice (reason=3) cfg80211: Calling CRDA to update world regulatory domain Does anyone know why this happens? - Grant