WPA2 suddenly stopped working

allbluedream · 2009-05-22 02:17:11

I had been able to connect to the office network via wpa2 fine up to the day before yesterday, and it all stopped working yesterday...
I was using wicd, and since the problem I tried various ways described in the wiki. Currently I am using gnome network manager, but connection gets stuck forever at the authentication stage. Wicd output shows that the connection's being dropped, and network manager is forever asking for the passphrase.

I don't exactly remember what I'd changed during these days... Probably nothing concerning networking, so I have no clue at all and feel really frustrated. Please someone give me some tip on hard to start diagnose the problem.

(I'm currently posting in Vista... I can see the connection type as WPA2-private, and the encryption is AES)

litemotiv · 2009-05-23 16:51:52

did you check your pacman logs if anything related to wireless was updated?

allbluedream · 2009-05-25 01:00:53

I did...currently on Windows, so I'm posting it shortly

Last time I checked, there was nothing related to wireless in the pacman log.

allbluedream · 2009-05-25 07:58:49

pacman.log

[2009-05-19 07:29] synchronizing package lists
[2009-05-19 07:29] starting full system upgrade
[2009-05-19 07:30] starting full system upgrade
[2009-05-19 09:15] installed libvc (003-1)
[2009-05-19 09:15] installed rolo (011-2)
[2009-05-19 11:04] removed ncmpcpp-git (20090324-1)
[2009-05-19 11:04] Example configuration files can be found in
[2009-05-19 11:04] /usr/share/doc/ncmpcpp
[2009-05-19 11:04] installed ncmpcpp (0.3.3-1)
[2009-05-19 11:08] installed zziplib (0.13.49-2)
[2009-05-19 11:13] removed mpd (0.14.2-1)
[2009-05-19 11:13] ==> mpd: Create a config under /etc/mpd.conf before using MPD (Example: /etc/mpd.conf.example)
[2009-05-19 11:13] installed mpd-devel (0.15_beta2-1)
[2009-05-19 15:08] synchronizing package lists
[2009-05-19 15:16] starting full system upgrade
[2009-05-19 15:19] starting full system upgrade
[2009-05-19 15:23] installed live-media (2009.02.23-1)
[2009-05-19 16:36] upgraded vlc-embeddedvideo (0.9.9-3 -> 0.9.9-3)
[2009-05-19 16:36] starting full system upgrade
[2009-05-19 16:36] upgraded curl (7.19.4-1 -> 7.19.5-1)
[2009-05-19 16:36] upgraded x264 (20090216-1 -> 20090416-1)
[2009-05-19 16:36] upgraded ffmpeg (20090217-1 -> 0.5-1)
[2009-05-19 16:36] upgraded gstreamer0.10-bad-plugins (0.10.11-5 -> 0.10.11-6)
[2009-05-19 16:36] upgraded mplayer (28347-4 -> 29188-2)
[2009-05-19 16:36] upgraded xine-lib (1.1.16.3-2 -> 1.1.16.3-3)
[2009-05-20 07:27] synchronizing package lists
[2009-05-20 07:28] starting full system upgrade
[2009-05-20 07:29] starting full system upgrade
[2009-05-20 07:54] upgraded vlc-embeddedvideo (0.9.9-3 -> 0.9.9a-2)
[2009-05-20 09:23] ==> SGML support in gtk-doc is no longer maintained, only very old projects
[2009-05-20 09:23] ==> still use SGML. Install (open)jade for SGML support. 
[2009-05-20 09:23] installed gtk-doc (1.11-1)
[2009-05-20 09:29] installed gnome-main-menu-svn (561-1)
[2009-05-20 09:33] installed djview4 (4.4-3)
[2009-05-20 09:46] installed djvulibre-nogui (3.5.21-1)
[2009-05-20 10:02] installed pdf2djvu (0.5.0-1)
[2009-05-20 14:36] synchronizing package lists
[2009-05-20 14:43] starting full system upgrade
[2009-05-20 15:21] starting full system upgrade
[2009-05-20 15:22] synchronizing package lists
[2009-05-20 15:22] starting full system upgrade
[2009-05-20 15:39] synchronizing package lists
[2009-05-20 15:49] synchronizing package lists
[2009-05-20 15:49] starting full system upgrade
[2009-05-20 15:51] synchronizing package lists
[2009-05-20 15:57] synchronizing package lists
[2009-05-20 15:59] starting full system upgrade
[2009-05-20 15:59] starting full system upgrade
[2009-05-21 11:00] installed netcfg (2.1.3-3)
[2009-05-21 11:08] synchronizing package lists
[2009-05-21 11:26] starting full system upgrade
[2009-05-21 11:26] upgraded anki (0.9.9.7.9-1 -> 0.9.9.7.9b-1)
[2009-05-21 11:26] upgraded cpio (2.9-4 -> 2.9-5)
[2009-05-21 11:26] upgraded dmapi (2.2.9-1 -> 2.2.10-1)
[2009-05-21 11:26] warning: /etc/sysctl.conf installed as /etc/sysctl.conf.pacnew
[2009-05-21 11:26] upgraded procps (3.2.7-5 -> 3.2.8-1)
[2009-05-21 11:26] upgraded psmisc (22.6-2 -> 22.7-1)
[2009-05-21 11:26] upgraded xfsprogs (3.0.0-1 -> 3.0.1-1)
[2009-05-21 11:27] installed autowifi (0.2-2)
[2009-05-21 12:26] installed wpa_supplicant_gui (0.6.9-1)
[2009-05-21 15:42] upgraded networkmanager (0.7.1-1 -> 0.7.1-1)
[2009-05-22 07:26] synchronizing package lists
[2009-05-22 09:49] >>> Updating module dependencies. Please wait ...
[2009-05-22 09:49] >>> MKINITCPIO SETUP
[2009-05-22 09:49] >>> ----------------
[2009-05-22 09:49] >>> If you use LVM2, Encrypted root or software RAID,
[2009-05-22 09:49] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-05-22 09:49] >>> More information about mkinitcpio setup can be found here:
[2009-05-22 09:49] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-05-22 09:49] 
[2009-05-22 09:49] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2009-05-22 09:49] ==> Building image "default"
[2009-05-22 09:49] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-05-22 09:49] :: Begin dry run
[2009-05-22 09:49] :: Parsing hook [base]
[2009-05-22 09:49] :: Parsing hook [udev]
[2009-05-22 09:49] :: Parsing hook [autodetect]
[2009-05-22 09:49] :: Parsing hook [sata]
[2009-05-22 09:49] :: Parsing hook [keymap]
[2009-05-22 09:49] :: Parsing hook [filesystems]
[2009-05-22 09:50] :: Generating module dependencies
[2009-05-22 09:50] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-05-22 09:50] ==> SUCCESS
[2009-05-22 09:50] ==> Building image "fallback"
[2009-05-22 09:50] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-05-22 09:50] :: Begin dry run
[2009-05-22 09:50] :: Parsing hook [base]
[2009-05-22 09:50] :: Parsing hook [udev]
[2009-05-22 09:50] :: Parsing hook [sata]
[2009-05-22 09:50] :: Parsing hook [keymap]
[2009-05-22 09:50] :: Parsing hook [filesystems]
[2009-05-22 09:50] :: Generating module dependencies
[2009-05-22 09:50] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-05-22 09:50] ==> SUCCESS
[2009-05-22 09:50] upgraded kernel26 (2.6.29.3-1 -> 2.6.29.4-1)
[2009-05-22 09:52] installed wireless-regdb (2009.04.17-2)
[2009-05-22 09:52] installed iw (0.9.11-1)
[2009-05-22 09:52] Uncomment the right regulatory domain in /etc/conf.d/wireless-regdom.
[2009-05-22 09:52] It will automatically be set when necessary.
[2009-05-22 09:52] installed crda (1.0.1-2)
[2009-05-25 14:38] synchronizing package lists
[2009-05-25 15:02] upgraded iwlwifi-3945-ucode (15.28.2.8-1 -> 15.32.2.9-1)
[2009-05-25 15:02] upgraded kernel-headers (2.6.29.1-1 -> 2.6.29.3-1)
[2009-05-25 15:02] upgraded ppp (2.4.4-7 -> 2.4.4-8)
[2009-05-25 15:02] upgraded mplayer (29188-2 -> 29318-1)
[2009-05-25 15:02] upgraded poppler (0.10.6-1 -> 0.10.7-1)
[2009-05-25 15:02] upgraded ncmpcpp (0.3.3-1 -> 0.3.4-1)

Just updated iwlwifi-3945-ucode, didn't help though.

litemotiv · 2009-05-25 08:48:07

i don't know what the cause could be, sorry. what you can try to narrow down the problem:

- can you connect to unsecured networks?
- can you connect to other wpa networks?
- can you reboot/reset this specific router?

allbluedream · 2009-05-25 08:59:58

Thanks anyway

I can connect to unsecured networks (wicd with madwifi only, while wicd with wext does not work)
I cannot connect to other wpa networks on campus...
Perhaps I can try to reset the router, but I don't want to screw it up so everyone else in the office can no longer use the net

litemotiv · 2009-05-25 09:58:37

why are you using madwifi/wext? shouldn't you be using iwlwifi these days?

http://intellinuxwireless.org/

allbluedream · 2009-05-26 01:56:28

There are: wext, hostap, madwifi, atmel, ndiswrapper, ipw, ralink legacy, and only madwifi works with unsecured networks... I don't see an option in wicd to use iwlwifi though...

And wpa_supplicant does not know the iwlwifi as a driver... Strange.

allbluedream · 2009-05-28 01:10:07

Look at the kernel.log I see something *interesting*

May 20 19:39:19 arch kernel: wlan0: authenticate with AP **:**:**:**:**:**
May 20 19:39:19 arch kernel: wlan0: authenticate with AP **:**:**:**:**:**
May 20 19:39:19 arch kernel: wlan0: authenticated
May 20 19:39:19 arch kernel: wlan0: associate with AP **:**:**:**:**:**
May 20 19:39:19 arch kernel: wlan0: RX ReassocResp from **:**:**:**:**:** (capab=0x411 status=0 aid=3)
May 20 19:39:19 arch kernel: wlan0: associated
May 20 20:25:39 arch kernel: wlan0 (iwl3945): not using net_device_ops yet
May 21 07:25:12 arch kernel: wlan0 (iwl3945): not using net_device_ops yet
May 21 07:27:03 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** try 1
May 21 07:27:03 arch kernel: wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
May 21 07:27:03 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** try 1
May 21 07:27:03 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** try 1
May 21 07:27:03 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** try 2
May 21 07:27:03 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** try 3
May 21 07:27:04 arch kernel: wlan0: direct probe to AP **:**:**:**:**:** timed out

It happened on May 21. Never able to connect to my office network since then.

I might have switched the hardware wireless switch on my Dell Vostro 1400 off on May 20...but I'm not sure. Of course the switch has always been on when I did all my wireless tests these days.

Last edited by allbluedream (2009-05-28 02:41:45)

litemotiv · 2009-05-28 08:30:39

it might be a good idea to start with a clean slate, especially remove your current configs and wpa stuff and start from scratch.

someone on another forum fixed a similar problem by setting a driver option which you could try:

sudo rmmod -f iwl3945
sudo modprobe iwl3945 disable_hw_scan=1

allbluedream · 2009-05-31 06:45:44

Thank you. I tried your method, but it doesn't work. I also tried the noapic boot option, doesn't work either.

BTW, the stock Chakra livecd cannot connect, either.

allbluedream · 2009-06-02 07:02:13

I am on my way of solving this problem! I just booted my machine with the Linux Mint Elyssa LiveCD, and I was able to connect to my office network with the TKIP encryption method. With networkmanager 0.6.6, I am able to select the security type (WPA, WPA2 and LEAP) as well as the encryption type (default, AES-CCMP and TKIP). Default and AES-CCMP always result in endless queries for password, but to my surprise, TKIP works! It is strange, because under Vista I can see that the encryption type is AES...

Anyway, my task remains as how to do the same thing with Arch. I haven't noticed any encryption options in wicd, and in the current networkmanager such options does not exist. Definitely a regression for me.

edit----------------
I tried again with Windows, and it turns out that the encryption type I see under the connection property dialogue doesn't really mean anything...
So TKIP it is!

Last edited by allbluedream (2009-06-02 07:19:06)

iphitus · 2009-06-02 09:03:56

allbluedream wrote:

There are: wext, hostap, madwifi, atmel, ndiswrapper, ipw, ralink legacy, and only madwifi works with unsecured networks... I don't see an option in wicd to use iwlwifi though...
And wpa_supplicant does not know the iwlwifi as a driver... Strange.

wext = wireless extensions = 'standard'. iwlwifi uses wext.

1) Give netcfg from [testing] a go, try modifying the configuration in /etc/network.d/examples/wireless-wpa.
Documentation for netcfg on the wik: http://wiki.archlinux.org/index.php/Network_Profiles

If that fails...
2) create your own wpa_supplicant configuration. Something along the lines of this:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

network={
        ssid="example"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
        psk="not so secure passphrase"
}

Save it wherever you like, then make a copy of and modify "/etc/network.d/examples/wireless-wpa-config" as appropriate.

Hope one of those works. If you want a GUI, search on the AUR and there's some netcfg compatible gui's.

James

allbluedream · 2009-06-02 11:18:37

Thanks for the help. However, when I issue the netcfg command, e.g.

netcfg /etc/network.d/examples/wpa.example

it complains that "Profile "/etc/network.d/examples/wpa.example" does not exist"
I get this result with every profile I throw at netcfg...

My wpa_supplicant.conf looks like this:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
ap_scan=1
fast_reauth=1
network={
        ssid="PHOAIB104"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
        psk="a silly password"
}

And it isn't working. I have no idea while network works with a one-year-old Mint LiveCD but not the state-of-the-art installation on my machine (both Arch and Ubuntu).

iphitus · 2009-06-02 11:40:55

The correct way to connect to use netcfg is netcfg <profilename>, where the <profilename> is the name of the file in /etc/network.d. For example, you'd copy one out of the example folder into /etc/network.d, modify it and it would end up as /etc/network.d/myhomenetwork. Then netcfg myhomenetwork.

That said, if wpa_supplicant on it's own doesnt work, netcfg probably wont either. Try removing the ap_scan and fast_reauth lines in that wpa_supplicant.conf.

If none of that gets you anywhere. run wpa_supplicant with -d. It's pretty verbose and long, but post that and I might be able to find why its not connecting.

Last edited by iphitus (2009-06-02 11:41:18)

broch · 2009-06-03 02:32:25

it looks like you are the next victim of linux AP connectivity (this is a problem that pops up one in a while). A lot of problems with this irrelevant of network card used.

see here:
http://bbs.archlinux.org/viewtopic.php?id=73234

since I don't have problems (iwl3945/iwlwifi + wpa2 + +wpa_supplicant + dhcpd + wireless assistant) with connecting to ssid, it seems that this is related to AP.

I use dhcpcd 3.2.1-1 though as anything later is simply crappy (not Arch fault)

allbluedream · 2009-06-10 08:07:10

wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
        ssid="myssid"
        proto=WPA
        key_mgmt=WPA-PSK
        pairwise=TKIP
        group=TKIP
        psk="a silly password"
}

sudo wpa_supplicant -i wlan0 -dd -c /etc/wpa_supplicant.conf
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=9):
     50 48 4f 41 49 42 31 30 34                        myssid       
proto: 0x1
key_mgmt: 0x2
pairwise: 0x8
group: 0x8
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='myssid'
Initializing interface (2) 'wlan0'
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1b:77:b9:5f:12
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 6b e3 c7 d4 e8 05 59 e6 b3 d1 64 9e 1b 0c 39 75
WPS: Build Beacon and Probe Response IEs
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Version
WPS:  * Wi-Fi Protected Setup State (0)
WPS:  * Response Type (2)
WPS:  * UUID-E
WPS:  * Manufacturer
WPS:  * Model Name
WPS:  * Model Number
WPS:  * Serial Number
WPS:  * Primary Device Type
WPS:  * Device Name
WPS:  * Config Methods (0)
WPS:  * RF Bands (3)
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
ctrl_interface_group=10 (from group name 'wheel')
Added interface wlan0
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 517 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS 
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: **:**:**:**:**:** ssid='myssid' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   selected based on WPA IE
   selected WPA AP **:**:**:**:**:** ssid='myssid'
Trying to associate with **:**:**:**:**:** (SSID='myssid' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=30): dd 1c 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 0c 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID **:**:**:**:**:** into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: disable timer tick
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b19 len=8
Received 2269 bytes of scan results (5 BSSes)
CTRL-EVENT-SCAN-RESULTS 
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS: attr type=0x104a len=1
WPS: attr type=0x1044 len=1
WPS-AP-AVAILABLE 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: **:**:**:**:**:** ssid='myssid' wpa_ie_len=28 rsn_ie_len=24 caps=0x11
   selected based on WPA IE
   selected WPA AP **:**:**:**:**:** ssid='myssid'
Trying to associate with **:**:**:**:**:** (SSID='myssid' freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 24 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=30): dd 1c 00 50 f2 01 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 0c 00
WPA: set AP RSN IE - hexdump(len=26): 30 18 01 00 00 0f ac 02 02 00 00 0f ac 04 00 0f ac 02 01 00 00 0f ac 02 0c 00
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_psk
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID **:**:**:**:**:** blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATING -> DISCONNECTED

It seems that wpa_supplicant is blacklisting my AP after previous (too many) failures.

And the recently updated Wicd (1.6) would always reports back "bad password" after each try.

I might as well just give up

allbluedream · 2009-06-10 23:42:12

broch wrote:

it looks like you are the next victim of linux AP connectivity (this is a problem that pops up one in a while). A lot of problems with this irrelevant of network card used.
see here:
http://bbs.archlinux.org/viewtopic.php?id=73234
since I don't have problems (iwl3945/iwlwifi + wpa2 + +wpa_supplicant + dhcpd + wireless assistant) with connecting to ssid, it seems that this is related to AP.
I use dhcpcd 3.2.1-1 though as anything later is simply crappy (not Arch fault)

I don't know if I can blame the AP, since I can connect with the same computer using a Linux Mint LiveCD which is a year old now. Regression, it seems to me.

allbluedream · 2009-06-24 23:44:34

I'm not marking this one solved, because I don't know what happened, but today WPA2 started to work for me again, while wicd would always fail to get an IP address from insecure networks. WPA2 is more important to me at this stage so I'm happy, at least for now. Maybe it's because of the new kernel.

Arch Linux

#1 2009-05-22 02:17:11

WPA2 suddenly stopped working

#2 2009-05-23 16:51:52

Re: WPA2 suddenly stopped working

#3 2009-05-25 01:00:53

Re: WPA2 suddenly stopped working

#4 2009-05-25 07:58:49

Re: WPA2 suddenly stopped working

#5 2009-05-25 08:48:07

Re: WPA2 suddenly stopped working

#6 2009-05-25 08:59:58

Re: WPA2 suddenly stopped working

#7 2009-05-25 09:58:37

Re: WPA2 suddenly stopped working

#8 2009-05-26 01:56:28

Re: WPA2 suddenly stopped working

#9 2009-05-28 01:10:07

Re: WPA2 suddenly stopped working

#10 2009-05-28 08:30:39

Re: WPA2 suddenly stopped working

#11 2009-05-31 06:45:44

Re: WPA2 suddenly stopped working

#12 2009-06-02 07:02:13

Re: WPA2 suddenly stopped working

#13 2009-06-02 09:03:56

Re: WPA2 suddenly stopped working

#14 2009-06-02 11:18:37

Re: WPA2 suddenly stopped working

#15 2009-06-02 11:40:55

Re: WPA2 suddenly stopped working

#16 2009-06-03 02:32:25

Re: WPA2 suddenly stopped working

#17 2009-06-10 08:07:10

Re: WPA2 suddenly stopped working

#18 2009-06-10 23:42:12

Re: WPA2 suddenly stopped working

#19 2009-06-24 23:44:34

Re: WPA2 suddenly stopped working

Board footer