Bad password using WPA2 with wicd v1.7.0

Bug #720439 reported by verdant
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd
New
Undecided
Unassigned

Bug Description

When using wicd v1.7.0 in MintPPC 9 and Linux Mint LXDE 9 to connect wirelessly to a WPA2 Personal-AES (CCMP) secured wifi network using a Broadcom 4306 v2 or v3 chipset PCMCIA card with b43-legacy and b43 driver, respectively, the connection attempt would fail with the "Bad Passord" error message.
Workaround is to remove all v1.7.0 pacakges and rollback to wicd v1.6.2.2 by running
sudo dpkg -i wicd_1.6.2.2-1~bpo50+1_all.deb
sudo apt-get install python-urwid
in the case of MintPPC 9, and for Linux Mint LXDE 9 by installing wicd_1.6.2.2-3_all.deb installed using the Linux Mint LXDE default GDebi Package Installer.......

Wicd log file from when error occurred is not currently available as I applied the above workaround without saving a copy of the log file......I do not know if this bug has already been reported...............

Revision history for this message
Diederen (jjhdiederen) wrote :

I experience

Revision history for this message
Diederen (jjhdiederen) wrote :

I experience the same problem with an Airport classic card (0001:11:00.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)) with the b43 driver. I am not sure whether it has to do with wicd. I had it working with the latest version of wicd (1.7.0+ds1-5). I am not sure what happened after that but it stopped working after a while.

Revision history for this message
Diederen (jjhdiederen) wrote :

I made a mistake in my last post. I was referring to my airport extreme card which works fine still. The airport classic is driven by the airport/orinoco kernel module. This airport classic card does not work at the moment in Debian Squeeze / sid.

[ 15.033047] airport 0.15 (Benjamin Herrenschmidt <email address hidden>)
[ 15.033196] airport: Physical address 80030000
[ 16.289008] airport 0.00030000:radio: Hardware identity 0001:0004:0005:0000
[ 16.295227] airport 0.00030000:radio: Station identity 001f:0001:0008:0048
[ 16.301083] airport 0.00030000:radio: Firmware determined as Lucent/Agere 8.72
[ 16.348812] airport 0.00030000:radio: firmware: requesting agere_sta_fw.bin
[ 16.726018] airport 0.00030000:radio: Hardware identity 0001:0004:0005:0000
[ 16.732066] airport 0.00030000:radio: Station identity 001f:0002:0009:0030
[ 16.737844] airport 0.00030000:radio: Firmware determined as Lucent/Agere 9.48
[ 16.743653] airport 0.00030000:radio: Ad-hoc demo mode supported
[ 16.749420] airport 0.00030000:radio: IEEE standard IBSS ad-hoc mode supported
[ 16.755115] airport 0.00030000:radio: WEP supported, 104-bit key
[ 16.760705] airport 0.00030000:radio: WPA-PSK supported

Really don't know what's going on. In network-manager-gnome I can't get this card to work either.

Revision history for this message
Diederen (jjhdiederen) wrote :

I got a little more insight in this problem. It's kernel related. Sometimes I have my airport card working and then I receive a kernel oops:
[ 256.069813] ------------[ cut here ]------------
[ 256.069854] Badness at /build/buildd-linux-2.6_2.6.32-30-powerpc-wZZD8S/linux
-2.6-2.6.32/debian/build/source_powerpc_none/net/wireless/core.c:614
[ 256.069876] NIP: e1e5a664 LR: e1e5a640 CTR: c03755ac
[ 256.069894] REGS: df85be80 TRAP: 0700 Not tainted (2.6.32-5-powerpc)
[ 256.069906] MSR: 00029032 <EE,ME,CE,IR,DR> CR: 24000028 XER: 20000000
[ 256.069941] TASK = df849bc0[5] 'events/0' THREAD: df85a000
[ 256.069951] GPR00: c21cf800 df85bf30 df849bc0 00000000 00000000 00000000 0000
2b80 0000003b
[ 256.069982] GPR08: 00000000 00000001 df803300 d51ba880 24000022 00000000 0181
2550 018126bc
[ 256.070012] GPR16: 018124c4 c042301c c0423054 c045e098 00000001 c0508410 0000
0000 c05083a0
[ 256.070042] GPR24: df85bf58 df85a000 df803308 e1e5a60c df849bc0 c21cf00c c21c
fb60 c21cf000
[ 256.070148] NIP [e1e5a664] wdev_cleanup_work+0x58/0xfc [cfg80211]
[ 256.070179] LR [e1e5a640] wdev_cleanup_work+0x34/0xfc [cfg80211]
[ 256.070190] Call Trace:
[ 256.070218] [df85bf30] [e1e5a640] wdev_cleanup_work+0x34/0xfc [cfg80211] (unr
eliable)
[ 256.070254] [df85bf50] [c005dcdc] worker_thread+0x1b4/0x22c
[ 256.070279] [df85bfc0] [c0061aec] kthread+0x74/0x78
[ 256.070302] [df85bff0] [c0014adc] kernel_thread+0x4c/0x68
[ 256.070313] Instruction dump:
[ 256.070328] 3be9ff40 7fa3eb78 4801541d 817f0078 39200000 2f8b0000 419e0018 81
2b0018
[ 256.070373] 801e0010 7d290278 7d290034 5529d97e <0f090000> 2f890000 41be0018
38000001

If I rmmod airport and orinoco and modprobe them again, I can connect normally again.

Revision history for this message
David Paleino (dpaleino) wrote :

Thank you for your comments and investigation Didieren.

However, before marking the bug as invalid, I'll wait for a reply from verdant.

Have a nice day,
David

Revision history for this message
verdant (pandixiong) wrote : Re: [Bug 720439] Re: Bad password using WPA2 with wicd v1.7.0

Hi David,

What further actions/information do you require from me?

Regards
verdant

On 20 February 2011 15:47, David Paleino <email address hidden> wrote:

> Thank you for your comments and investigation Didieren.
>
> However, before marking the bug as invalid, I'll wait for a reply from
> verdant.
>
> Have a nice day,
> David
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/720439
>
> Title:
> Bad password using WPA2 with wicd v1.7.0
>
> Status in wicd:
> New
>
> Bug description:
> When using wicd v1.7.0 in MintPPC 9 and Linux Mint LXDE 9 to connect
> wirelessly to a WPA2 Personal-AES (CCMP) secured wifi network using a
> Broadcom 4306 v2 or v3 chipset PCMCIA card with b43-legacy and b43 driver,
> respectively, the connection attempt would fail with the "Bad Passord" error
> message.
> Workaround is to remove all v1.7.0 pacakges and rollback to wicd v1.6.2.2
> by running
> sudo dpkg -i wicd_1.6.2.2-1~bpo50+1_all.deb
> sudo apt-get install python-urwid
> in the case of MintPPC 9, and for Linux Mint LXDE 9 by installing
> wicd_1.6.2.2-3_all.deb installed using the Linux Mint LXDE default GDebi
> Package Installer.......
>
> Wicd log file from when error occurred is not currently available as I
> applied the above workaround without saving a copy of the log
> file......I do not know if this bug has already been
> reported...............
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/wicd/+bug/720439/+subscribe
>

Revision history for this message
Joseph J. Gunn (armadefuego) wrote :

Just guessing here.

He may wish you to verify that there is no kernel ooops error message in your logs.

If there is an error message there then it may be the same as the problem experienced by Diederen.

Otherwise its still outstanding.

Thanks
Joe

Revision history for this message
verdant (pandixiong) wrote :

I tried the commands suggested by Diederen as follows

sudo rmmod airport
sudo rmmod orinoco
sudo modprobe orinoco
sudo modprobe airport

because I get

FATAL: Error inserting orinoco (/lib/modules/2.6.32-5-powerpc/kernel/drivers/net/wireless/orinoco/orinoco.ko): Unknown symbol in module, or unknown parameter (see dmesg)

if I type sudo modprobe orinoco airport............

Then lsmod gives

airport 6597 0
orinoco 61223 1 airport

A refresh and connect attempt with wicd 1.7.0 still generates "Connection Failed: Bad Password", while a refresh and connect attempt with wicd 1.6.2.2 still does not restore the dropped connection.....

So, it appears that the problem with (a) wicd 1.6.2.2 not connecting and/or not maintaining a wireless connection to a non-broadcast ESSID WPA2 Personal-AES WiFi network and (b) wicd 1.7.0 generating a "Connection Failed: Bad Password" error message when attempting to connect wirelessly to a a non-broadcast ESSID WPA2 Personal-AES WiFi network, may not be due to the same cause as the problem being experienced by Diederen.......

I have attached a zipped folder containg the 1.6.2.2 and 1.7.0 dmesg files, the wicd.log and the kern.log containing both wicd 1.6.2.2 and 1.7.0 operation............I saw no kernel oops (badness) messages in my logs.......

Revision history for this message
Diederen (jjhdiederen) wrote :

It seems that the problem which verdant faces is similar to another old bug report:
https://bugs.launchpad.net/wicd/+bug/594676

Revision history for this message
Shane H (shane.h) wrote :

Comment #18 has fixed the problem for me.

Revision history for this message
Shane H (shane.h) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.