No subject
Fri Jan 15 15:06:42 UTC 2010
sometimes think it's associated but in reality it's not. I have to
manually disconnect and reconnect for my connection to work.
I am using iwl3945.
xavier at ex5620 ~> sudo iwconfig wlan0
wlan0 IEEE 802.11 ESSID:"ulaval-wpa"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:removed
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
xavier at ex5620 ~> wpa_cli status
Selected interface 'wlan0'
bssid=00:0e:83:82:ac:41
ssid=ulaval-wpa
id=0
id_str=peap
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2/IEEE 802.1X/EAP
wpa_state=COMPLETED
Supplicant PAE state=AUTHENTICATED
suppPortStatus=Authorized
EAP state=SUCCESS
selectedMethod=25 (EAP-PEAP)
EAP TLS cipher=AES256-SHA
EAP-PEAPv1 Phase2 method=MSCHAPV2
xavier at ex5620 ~>
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.26-1-amd64
Debian Release: lenny/sid
990 testing security.debian.org
990 testing gulus.usherbrooke.ca
500 unstable gulus.usherbrooke.ca
500 hardy ppa.launchpad.net
1 experimental gulus.usherbrooke.ca
--- Package information. ---
Depends (Version) | Installed
==============================-+-==============
libc6 (>= 2.7-1) | 2.7-14
libdbus-1-3 (>= 1.1.1) | 1.2.1-3
libpcsclite1 (>= 1.4.102) | 1.4.102-1
libreadline5 (>= 5.2) | 5.2-3
libssl0.9.8 (>= 0.9.8f-5) | 0.9.8g-13
lsb-base (>= 3.0-6) | 3.2-20
adduser | 3.110
------------=_1267485489-22970-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Received: (at 505225-done) by bugs.debian.org; 1 Mar 2010 23:11:26 +0000
X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02
(2007-08-08) on rietz.debian.org
X-Spam-Level:
X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 149; neutral, 101; spammy,
2. spammytokens:0.993-1--Douville, 0.993-1--douville
hammytokens:0.000-+--Severity, 0.000-+--H*u:x86_64, 0.000-+--H*u:sk:2.6.32-,
0.000-+--H*UA:sk:2.6.32-, 0.000-+--H*UA:1.12.4
X-Spam-Status: No, score=-3.9 required=4.0 tests=BAYES_00,FOURLA autolearn=no
version=3.2.3-bugs.debian.org_2005_01_02
Return-path: <kel at otaku42.de>
Received: from venema.h4ckr.net ([217.24.1.135])
by rietz.debian.org with esmtp (Exim 4.63)
(envelope-from <kel at otaku42.de>)
id 1NmElq-0005ap-7O
for 505225-done at bugs.debian.org; Mon, 01 Mar 2010 23:11:26 +0000
Received: from localhost (localhost [127.0.0.1])
by venema.h4ckr.net (Postfix) with ESMTP id B9DBD33E7E1;
Mon, 1 Mar 2010 23:40:11 +0100 (CET)
Received: from venema.h4ckr.net ([127.0.0.1])
by localhost (venema.h4ckr.net [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id yPY-UklfrmoW; Mon, 1 Mar 2010 23:40:06 +0100 (CET)
Received: from nomad.localnet (CPE-58-174-132-139.mjcz1.woo.bigpond.net.au [58.174.132.139])
by venema.h4ckr.net (Postfix) with ESMTP id ED80133E69B;
Mon, 1 Mar 2010 23:40:05 +0100 (CET)
From: Kel Modderman <kel at otaku42.de>
To: Xavier Douville <debian at douville.org>
Subject: Re: [wpasupplicant] Not always in sync with wireless nic status
Date: Tue, 2 Mar 2010 08:40:03 +1000
User-Agent: KMail/1.12.4 (Linux/2.6.32-8.slh.2-sidux-amd64; KDE/4.3.4; x86_64; ; )
Cc: 505225-done at bugs.debian.org
References: <4918C309.8020302 at douville.org>
In-Reply-To: <4918C309.8020302 at douville.org>
MIME-Version: 1.0
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201003020840.04017.kel at otaku42.de>
On Tuesday 11 November 2008 09:26:01 Xavier Douville wrote:
> Package: wpasupplicant
> Version: 0.6.4-3
> Severity: normal
>
> --- Please enter the report below this line. ---
>
> >From the result of these two commands, I can see that wpasupplicant
> sometimes think it's associated but in reality it's not. I have to
> manually disconnect and reconnect for my connection to work.
> I am using iwl3945.
>
> xavier at ex5620 ~> sudo iwconfig wlan0
>
> wlan0 IEEE 802.11 ESSID:"ulaval-wpa"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=15 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:removed
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> xavier at ex5620 ~> wpa_cli status
> Selected interface 'wlan0'
> bssid=00:0e:83:82:ac:41
> ssid=ulaval-wpa
> id=0
> id_str=peap
> pairwise_cipher=CCMP
> group_cipher=TKIP
> key_mgmt=WPA2/IEEE 802.1X/EAP
> wpa_state=COMPLETED
> Supplicant PAE state=AUTHENTICATED
> suppPortStatus=Authorized
> EAP state=SUCCESS
> selectedMethod=25 (EAP-PEAP)
> EAP TLS cipher=AES256-SHA
> EAP-PEAPv1 Phase2 method=MSCHAPV2
> xavier at ex5620 ~>
Associated state does not mean your networking tools have been configured
properly or even used at all. You can be associated, authenticated and not
have any meaningful network connection, they are independent of each other.
This bug report is invalid and I am closing it.
Kel.
------------=_1267485489-22970-0--
More information about the Pkg-wpa-devel
mailing list