RaLink RT2860 won't connect to D-Link DI-624 router with WPA2 encryption anymore (openSUSE 11.1)

ginkobonsai · February 24, 2010, 11:27pm

Hi!

I searched this forum and the net for a solution for the last few days but I seem to be utterly stuck - I’m hoping for some input now

I have an Eeee 1000H with openSUSE 11.1 (i586) with a RaLink RT2860 WiFi card and want to connect to my D-Link DI-624 router (latest firmware). I had the exact same hardware working together in the past but apparently I updated some package or other I wasn’t supposed to while I didn’t have access to the router (so I didn’t immediately notice).

Anyway, it stopped working.

I use the NetworkManager and the gnome nm-applet (on a KDE 3.5 desktop - I just like the gnome applet better and I’d like to keep on using it. I also tried the KDE applet - to no avail)

I can “see” the router, I can connect if I disable encryption or if I use WEP - but WPA and WPA2 won’t work anymore.

I also tried wicd - doesn’t work either.
The wired connection works fine.

Some info:

uname -a

Linux myeee 2.6.27.42-0.1-pae #1 SMP 2010-01-06 16:07:25 +0100 i686 i686 i386 GNU/Linux

lspci

01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
03:00.0 Ethernet controller [0200]: Attansic Technology Corp. L1 Gigabit Ethernet Adapter [1969:1026] (rev b
0)

hwinfo

24: PCI 100.0: 0282 WLAN controller
  Model: "RaLink RT2860"
  Vendor: pci 0x1814 "RaLink"
  Device: pci 0x0781 "RT2860"
  SubVendor: pci 0x1814 "RaLink"
  SubDevice: pci 0x2790
  Driver: "rt2860"
  Driver Modules: "rt2860sta"
  Device File: ra0
  Link detected: yes
    Driver Status: rt2860sta is active
    Driver Activation Cmd: "modprobe rt2860sta"

rpm -qi rt2860-1.8.0.0-2.7

Name        : rt2860                       Relocations: (not relocatable)
Version     : 1.8.0.0                           Vendor: openSUSE
Release     : 2.7                           Build Date: Wed 03 Dec 2008 11:10:10 CET

**
iwconfig**

ra0       RT2860 Wireless  ESSID:""  Nickname:"RT2860STA"
          Mode:Auto  Frequency=2.412 GHz  Bit Rate=1 Mb/s
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality=100/100  Signal level:-88 dBm  Noise level:-97 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

iwlist scan

ra0       Scan completed :
          Cell 01 - Address: 00:11:95:07:FD:00
                    ESSID:"myssid"
                    Mode:Managed
                    Channel:1
                    Quality:100/100  Signal level:-48 dBm  Noise level:-97 dBm
                    Encryption key:on
                    Bit Rates:36 Mb/s
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                       Preauthentication Supported

part of /var/log/NetworkManager

Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 1 of 5 (Device Prepare) scheduled...
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 1 of 5 (Device Prepare) started...
Feb 24 22:16:56 myeee NetworkManager: <info>  (ra0): device state change: 6 -> 4
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 2 of 5 (Device Configure) scheduled...
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 1 of 5 (Device Prepare) complete.
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 2 of 5 (Device Configure) starting...
Feb 24 22:16:56 myeee NetworkManager: <info>  (ra0): device state change: 4 -> 5
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0/wireless): connection 'Auto myssid' has security, and secrets exist.  No new secrets needed.
Feb 24 22:16:56 myeee NetworkManager: <info>  Config: added 'ssid' value 'myssid'
Feb 24 22:16:56 myeee NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Feb 24 22:16:56 myeee NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb 24 22:16:56 myeee NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Feb 24 22:16:56 myeee NetworkManager: <info>  Activation (ra0) Stage 2 of 5 (Device Configure) complete.
Feb 24 22:16:56 myeee NetworkManager: <info>  Config: set interface ap_scan to 1
Feb 24 22:16:56 myeee NetworkManager: <info>  (ra0): supplicant connection state:  disconnected -> scanning
Feb 24 22:17:01 myeee NetworkManager: <info>  (ra0): supplicant connection state:  scanning -> associating
Feb 24 22:17:11 myeee NetworkManager: <info>  (ra0): supplicant connection state:  associating -> disconnected
Feb 24 22:17:11 myeee NetworkManager: <info>  (ra0): supplicant connection state:  disconnected -> scanning
Feb 24 22:17:16 myeee NetworkManager: <info>  (ra0): supplicant connection state:  scanning -> associating
Feb 24 22:17:21 myeee NetworkManager: <info>  Activation (ra0/wireless): association took too long.
Feb 24 22:17:21 myeee NetworkManager: <info>  (ra0): device state change: 5 -> 6
Feb 24 22:17:21 myeee NetworkManager: <info>  Activation (ra0/wireless): asking for new secrets

part of /var/log/wpa_supplicant.log


CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:11:95:07:fd:01 (SSID='myssid' freq=2412 MHz)
Authentication with 00:11:95:07:fd:01 timed out.

So the only clue I have right now is
Feb 24 22:17:21 myeee NetworkManager: <info> Activation (ra0/wireless): association took too long.
But so far it got me nowhere…

Also I’m pretty sure its not the router but the client because my boyfriend has no problems connecting to the router with his own Eee 90x (Ubuntu).

I’m running out of things to try - could somebody please tell me where to continue my investigation?

ginkobonsai · February 28, 2010, 5:44pm

OK, I have hunch that it might be the kernel module for the rt2860 (which apparently comes in the kernel-xxx-extra packages) - so I downgraded the kernel (read something of kernel downgrading for a similar problem on the net) - but that didn’t get me anywhere either…

How do I verify it is or it isn’t the kernel module that is the problem?

ginkobonsai · March 1, 2010, 8:09pm

this seriously pisses me off… why the **** does a perfectly working wifi setup stop working? what kind of package update would cause that? why can’t i connect to wpa2 networks any longer but can to unencrypted wlans?

ginkobonsai · March 8, 2010, 10:48am

@Moderators: Did I violate some code of conduct / netiquette here?

prhunt · March 8, 2010, 1:18pm

“@Moderators: Did I violate some code of conduct / netiquette here?”

Doubt it. More likely that no-one know the answer your Q. Including me…

If you can connect to unencrypted wlans, but not to wpa2 wlans, then that might suggest a problem with wpa_supplicant - either a configuration problem or some issue/incompatibility with the wpa_supplicant executable.

Oh, and one little anomaly - but I don’t know if it is significant…

your iwlist scan shows this:

Cell 01 - Address: 00:11:95:07:FD:00

while your wpa_supplicant log shows this:

Trying to associate with 00:11:95:07:fd:01 (SSID=‘myssid’ freq=2412 MHz)
Authentication with 00:11:95:07:fd:01 timed out.

Note that the MAC strings are different. Maybe significant?

By the way, it might help if you posted the content of your wireless config file - might be something like /etc/sysconfig/network/ifcfg-ra0. Your wpa passphrase will be there, so don’t forget to obscure it…

Paul

ginkobonsai · March 8, 2010, 10:04pm

Hey, thanks for the reply I was beginning to think that I have to go back to Windows because the problem can’t be fixed

Yeah, that was one of my guesses (but then I’m just a noob here) - but I don’t know what would cause that and what would fix it (as I said: I had it working on the same system, before).
The wpa_supplicant rpm apparently was last updated/installed on my system last year in July and it definitely worked after that.


# rpm -qi wpa_supplicant-0.6.4-15.13.1
Name        : wpa_supplicant               Relocations: (not relocatable)
Version     : 0.6.4                             Vendor: openSUSE
Release     : 15.13.1                       Build Date: Fri 24 Apr 2009 15:55:52 CEST
Install Date: Wed 01 Jul 2009 18:33:29 CEST      Build Host: portia

I tried installing the supplicant gui to see if I could use it to set up the network but it won’t connect to the wpa_supplicant


# wpa_gui
Failed to open control connection to wpa_supplicant.
PING failed - trying to reconnect
...

I also tried re-installing wpa_supplicant and NetworkManager. After doing that I get a bunch of new error messages in /var/log/wpa_supplicant.log when I try to connect:


CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:11:xx:07:fd:xx (SSID='myssid' freq=2412 MHz)
Associated with 00:11:xx:07:fd:xx
WPA: Invalid TKIP key length 16 (src=00:11:xx:07:fd:xx)
WPA: Invalid TKIP key length 16 (src=00:11:xx:07:fd:xx)
WPA: Invalid TKIP key length 16 (src=00:11:xx:07:fd:xx)
WPA: Invalid TKIP key length 16 (src=00:11:xx:07:fd:xx)
CTRL-EVENT-SCAN-RESULTS
Authentication with 00:11:xx:07:fd:xx timed out.
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Etc. etc.
The “invalid tkip key length” I haven’t seen before - although I’m not sure what it’s trying to tell me, as my key isn’t 16 characters long and I’m sure to have it entered correctly in the nm-applet

Oh, and one little anomaly - but I don’t know if it is significant…
[snip]

No, unfortunately not significant, just me failing at obscuring my router’s mac address in a consistent manner

By the way, it might help if you posted the content of your wireless config file - might be something like /etc/sysconfig/network/ifcfg-ra0. Your wpa passphrase will be there, so don’t forget to obscure it…

I have no such file for my wireless device. I got the impression that this is how it’s supposed to be if you use NetworkManager and not ifup/down to set up your network?

lwfinger · March 8, 2010, 10:34pm

On 03/08/2010 03:06 PM, ginkobonsai wrote:

> Yeah, that was one of my guesses (but then I’m just a noob here) - but
> I don’t know what would cause that and what would fix it (as I said: I
> had it working on the same system, before).
> The wpa_supplicant rpm apparently was last updated/installed on my
> system last year in July and it definitely worked after that.

Have you deleted the WPA2 connection and remade it? Perhaps your kwallet got
corrupted. I am assuming that you are using NM.

prhunt · March 8, 2010, 10:39pm

Ah, of course… NetworkManager…

Can I suggest, then, that you try - at least temporarily - switching to the “traditional” ifup/ifdown network management? I have generally found it easier to troubleshoot my network issues this way.

I take it no settings have been altered in the router? Can you use WPA (as opposed to WPA2)?

Paul

ginkobonsai · March 9, 2010, 11:01am

I assume you mean deleting and remaking the connection to the router in the nm-applet? Countless times.
(But to rule that out completely: would remaking the connection in the applet include rebooting or restarting nm?)

@kwallet: I’m not using the kde applet but the gnome applet (which in turn seems to use the gnome keyring thingy).

Hehe

Can I suggest, then, that you try - at least temporarily - switching to the “traditional” ifup/ifdown network management?

Sure. Not that I didn’t try it already (no luck), but at the very least it will probably generate the file you were asking for. I’ll do so later when I’m home and post the config.

I take it no settings have been altered in the router? Can you use WPA (as opposed to WPA2)?

Of course, the settings have been altered I played around with switching on and off ssid broadcast (currently on) and different types of encryption (none, wep, …).
But I’m pretty confident I reset the thing to how it was before.

Oh and I can’t connect to a friend’s network anymore either - which also worked fine before. He also uses wpa2 for encryption. So I’m assuming it’s not the router…

@Different types of encryption: So the connection works with no encryption and also with wep but not with wpa2. With all the stuff I did I’m a bit confused but I THINK I also tried wpa and that didn’t work either. But I’ll verify that later, just to be sure.

So if it works with wep and no encryption, does that mean that the problem is NOT with the driver?
Because I found another strange message in the wpa_supplicant log:


Failed to disable WPA in the driver.

Is that just a warning or a serious error?
Google doesn’t throw up anything conclusive for me

prhunt · March 9, 2010, 11:53am

I started using Suse at 9.0. I’ve only ever used ifup/ifdown for network management so NetworkManager is outside my comfort zone. The “old” method is my personal preference.

Now, apart from that, the level of tweakage available from the network config files is pretty high. If you haven’t done so, the file /etc/sysconfig/network/ifcfg.template makes an interesting read.

There’s lots of wireless parameters to play with. Of interest, for example, may be the scan mode settings? The template is well commented,so there is lots to learn.

Paul

lwfinger · March 9, 2010, 5:12pm

On 03/09/2010 04:06 AM, ginkobonsai wrote:
> Code:
> --------------------
>
> Failed to disable WPA in the driver.
>
> --------------------
>
> Is that just a warning or a serious error?
> Google doesn’t throw up anything conclusive for me

Who knows? You do know that the RT2860 driver is the one written by the vendor,
and is not “kernel quality”. There are routines in the code for AES and WPA,
thus WPA and WPA2 should be supported, and your previous experience showed that
it did.

Too bad you do not know which update broke it for you. The NetworkManager log
shows that the key exchange broke down.

For further analysis, please switch to ifup control. Please review
/etc/sysconfig/network/ifcfg-ra0 (I think that is the correct file.) to make
sure that it has the correct information. In addition, turn off MAC filtering in
the AP and do not hide your SSID. We do not want this to be any harder than
necessary.

Once those steps are complete, issue the ifup command and then a ‘ps ax | grep
wpa’ command. You should see a line for wpa_supplicant. Following the “-c” will
be a file name. Check that for correct info and fix if necessary. Now use the
“killproc wpa_supplicant” command to stop the supplicant. Manually start
wpa_supplicant using the line that you found in the ps step, but remove any “-B”
switch, and add a “-ddd” to the options. The first change will keep it from
becoming a daemon, and the second will turn on verbose debugging. Then open a
second terminal and reissue the ifup. Post the output from the window where the
supplicant is running.

ginkobonsai · March 9, 2010, 10:02pm

OK, so here comes /etc/sysconfig/network/ifcfg-ra0, as produced by YaST:


BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
INTERFACETYPE='wlan'
IPADDR=''
MTU=''
NAME='RT2860'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='psk'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='myssid'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='xxxxxxxxxx'

I shortened the key to 10 chars (also in the router, of course). No connection so far.

On ifup ra0, here’s whats in /var/log/messages


Mar  9 22:01:11 myeee ifup:     ra0       device: RaLink RT2860
Mar  9 22:01:11 myeee ifup-wireless:     ra0       warning: WPA configured but may be unsupported
Mar  9 22:01:11 myeee ifup-wireless:     ra0       warning: by this device
Mar  9 22:01:11 myeee ifup-wireless:     ra0       starting wpa_supplicant
Mar  9 22:01:11 myeee kernel: RX DESC f485e000  size = 2048
Mar  9 22:01:11 myeee kernel: <-- RTMPAllocTxRxRingMemory, Status=0
Mar  9 22:01:11 myeee kernel: I/F(ra0) Key1Str is Invalid key length! KeyLen = 0!
Mar  9 22:01:11 myeee kernel: I/F(ra0) Key2Str is Invalid key length! KeyLen = 0!
Mar  9 22:01:11 myeee kernel: I/F(ra0) Key3Str is Invalid key length! KeyLen = 0!
Mar  9 22:01:11 myeee kernel: I/F(ra0) Key4Str is Invalid key length! KeyLen = 0!
Mar  9 22:01:11 myeee kernel: 1. Phy Mode = 9
Mar  9 22:01:11 myeee kernel: 2. Phy Mode = 9
Mar  9 22:01:11 myeee kernel: RTMPSetPhyMode: channel is out of range, use first channel=1
Mar  9 22:01:11 myeee kernel: 3. Phy Mode = 9
Mar  9 22:01:11 myeee kernel: MCS Set = ff ff 00 00 01
Mar  9 22:01:11 myeee kernel: <==== RTMPInitialize, Status=0
Mar  9 22:01:11 myeee kernel: 0x1300 = 00064300
Mar  9 22:01:12 myeee ifup-dhcp: Starting DHCP4 client on ra0
Mar  9 22:01:12 myeee dhcpcd[1426]: ra0: dhcpcd 3.2.3 starting
Mar  9 22:01:12 myeee dhcpcd[1426]: ra0: hardware address = 00:15:af:dc:e8:07
Mar  9 22:01:12 myeee dhcpcd[1426]: ra0: broadcasting for a lease
Mar  9 22:01:13 myeee ifup-dhcp: .
Mar  9 22:01:16 myeee ifup-dhcp: .
Mar  9 22:01:17 myeee kernel: ===>rt_ioctl_giwscan. 1(1) BSS returned, data->length = 113
Mar  9 22:01:17 myeee kernel: ==>rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Mar  9 22:01:19 myeee ifup-dhcp: .
Mar  9 22:01:22 myeee ifup-dhcp: .
Mar  9 22:01:26 myeee ifup-dhcp: .
Mar  9 22:01:29 myeee kernel: ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
Mar  9 22:01:29 myeee ifup-dhcp: .
Mar  9 22:01:32 myeee ifup-dhcp: .
Mar  9 22:01:32 myeee dhcpcd[1426]: ra0: timed out
Mar  9 22:01:32 myeee dhcpcd[1426]: ra0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-ra0.info'
Mar  9 22:01:32 myeee dhcpcd[1426]: ra0: broadcasting for a lease
Mar  9 22:01:34 myeee kernel: ===&gt;rt_ioctl_giwscan. 1(1) BSS returned, data-&gt;length = 113
Mar  9 22:01:34 myeee kernel: ==&gt;rt_ioctl_siwfreq::SIOCSIWFREQ[cmd=0x8b04] (Channel=1)
Mar  9 22:01:35 myeee ifup-dhcp: .
Mar  9 22:01:37 myeee ifup-dhcp:
Mar  9 22:01:37 myeee ifup-dhcp:     ra0       DHCP4 continues in background
Mar  9 22:01:45 myeee kernel: ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!

ginkobonsai · March 9, 2010, 10:25pm

Well, I’ll gladly take any other module, as long as it works
Can you recommend any?

Too bad you do not know which update broke it for you.

Yeah
I tried reverting the kernel updates (as that might have changed the driver) but no luck…

For further analysis, please switch to ifup control. Please review
/etc/sysconfig/network/ifcfg-ra0 (I think that is the correct file.) to make
sure that it has the correct information.

Well, what I posted above kinda looks correct to me, but as I don’t know much about wlan configuration that doesn’t mean much

In addition, turn off MAC filtering in
the AP and do not hide your SSID. We do not want this to be any harder than
necessary.

Sure, has been the case the whole time

Once those steps are complete, issue the ifup command and then a ‘ps ax | grep
wpa’ command. You should see a line for wpa_supplicant.

I see two of them:


 1398 ?        Ss     0:00 wpa_supplicant -ira0 -c/var/run/wpa_supplicant-ra0.conf -Dwext -P/var/run/wpa_supplicant/ra0.pid -B
 3114 ?        S      0:00 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log

After that, I shut down the interface and killed the wpa process that was still running. Then I restarted the if, and now:


# ps ax | grep wpa
 2907 ?        Ss     0:00 wpa_supplicant -ira0 -c/var/run/wpa_supplicant-ra0.conf -Dwext -P/var/run/wpa_supplicant/ra0.pid -B

The info in the conf seems correct to me…


# cat /var/run/wpa_supplicant-ra0.conf
ctrl_interface=/var/run/wpa_supplicant
network={
  scan_ssid=1
  ssid="myssid"
  key_mgmt=WPA-PSK
  psk="xxxxxxxxxx"
}

Following the “-c” will
be a file name. Check that for correct info and fix if necessary. Now use the
“killproc wpa_supplicant” command to stop the supplicant. Manually start
wpa_supplicant using the line that you found in the ps step, but remove any “-B”
switch, and add a “-ddd” to the options. The first change will keep it from
becoming a daemon, and the second will turn on verbose debugging. Then open a
second terminal and reissue the ifup. Post the output from the window where the
supplicant is running.c

I’ll post the log as soon as I figure out how to attach files here

ginkobonsai · March 9, 2010, 10:33pm

Right, this is not all of it but I can’t post the full log, as the forum software then complains.


ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Initializing interface 'ra0' conf '/var/run/wpa_supplicant-ra0.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/var/run/wpa_supplicant-ra0.conf' -> '/var/run/wpa_supplicant-ra0.conf'
Reading configuration file '/var/run/wpa_supplicant-ra0.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 2 - start of a new network block
scan_ssid=1 (0x1)
ssid - hexdump_ascii(len=5):
     6c 65 6d 6f 6e                                    myssid           
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='myssid'
Initializing interface (2) 'ra0'
Interface ra0 set UP - waiting a second for the driver to complete initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=14 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf flags 0x0
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:15:af:dc:e8:07
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
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
Added interface ra0
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
     6c 65 6d 6f 6e                                    myssid           
Trying to get current scan results first without requesting a new scan to speed up initial association
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
Scan timeout - try to get results
Received 113 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS 
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:11:xx:07:fd:xx ssid='myssid' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
   selected WPA AP 00:11:xx:07:fd:xx ssid='myssid'
Try to find non-WPA AP
Trying to associate with 00:11:xx:07:fd:xx (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 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - 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
WPA: clearing AP RSN IE
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
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8c07 len=49
AssocReq IE wireless event - hexdump(len=41): 00 05 6c 65 6d 6f 6e 01 08 82 84 8b 96 0c 18 30 48 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:11:xx:07:fd:xx
Association info event
req_ies - hexdump(len=41): 00 05 6c 65 6d 6f 6e 01 08 82 84 8b 96 0c 18 30 48 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: set own WPA/RSN IE - 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
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:11:xx:07:fd:xx
No keys have been configured - skip key clearing
Associated with 00:11:xx:07:fd:xx
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:11:xx:07:fd:xx
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
  EAPOL-Key type=254
  key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
  key_length=32 key_data_length=0
  replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
  key_nonce - hexdump(len=32): c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85
  key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:11:xx:07:fd:xx (ver=1)
WPA: Renewed SNonce - hexdump(len=32): c9 cf eb c7 a2 08 78 90 2f 60 f9 ea b2 af 07 c8 4c ee 5f cc c0 76 bb 85 2d f0 c5 d5 08 1d 8a f5
WPA: PTK derivation - A1=00:15:af:dc:e8:07 A2=00:11:xx:07:fd:xx
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - 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
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 c9 cf eb c7 a2 08 78 90 2f 60 f9 ea b2 af 07 c8 4c ee 5f cc c0 76 bb 85 2d f0 c5 d5 08 1d 8a f5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 01 71 a4 7c 75 ea 65 25 59 a4 68 78 89 95 44 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RX EAPOL from 00:11:xx:07:fd:xx
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 35 75 8f db f7 c3 69 5f d8 4a 2e ba a4 70 e0 33 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
  EAPOL-Key type=254
  key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
  key_length=32 key_data_length=24
  replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
  key_nonce - hexdump(len=32): c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85
  key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
  key_mic - hexdump(len=16): 35 75 8f db f7 c3 69 5f d8 4a 2e ba a4 70 e0 33
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 c0 24 19 fb c8 de 86 86 9f d4 24 88 ec b6 47 fd 06 de 23 ef d0 b3 aa e2 ce 86 5e a1 83 73 10 85 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 35 75 8f db f7 c3 69 5f d8 4a 2e ba a4 70 e0 33 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:11:xx:07:fd:xx (ver=1)
WPA: IE KeyData - 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
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe c0 e8 92 9f c9 86 f0 53 08 e3 6b 8e ac f4 02 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
EAPOL: startWhen --> 0
EAPOL: disable timer tick
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: enable timer tick
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
Authentication with 00:11:xx:07:fd:xx timed out.
Added BSSID 00:11:xx:07:fd:xx into blacklist
wpa_driver_wext_disassociate
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
State: GROUP_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=5):
     6c 65 6d 6f 6e                                    myssid           
Scan requested (ret=0) - scan timeout 5 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'ra0' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 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
State: SCANNING -> DISCONNECTED

lwfinger · March 9, 2010, 10:59pm

It failed step 4/4 of the 4-way handshake. If you are sure that the psk value is
correct, then the driver seems not to support WPA2. I have no idea how to fix
it. Sorry.

There are no other drivers for your device - only the vendor one.

prhunt · March 9, 2010, 11:31pm

I think it might be possible to force a WPA (as opposed to WPA2) connection by hand-tweaking the config file. There’s information on this in the ifcfg.template mentioned earlier. I’ll check back later in the day (work intervenes now) and will suggest some settings if you’ve made no progress.

Of course, none of this explains why what used to work, now doesn’t…

I wonder if ndiswrapper could be worth trying?

ginkobonsai · March 10, 2010, 10:30am

Hm, I’m pretty sure - but is there some point where it can go wrong? Like putting an ASCII key where a hex key is expected or somesuch? I’m assuming I can enter a 8-63 char plain ascii passphrase into the box that YaST offers me… (or into the config file)

then the driver seems not to support WPA2.

Now THAT seems really weird. Because I had it working before, so either

the driver that is used by the system somehow got switched to one that doesn’t work or
the driver used was updated and wpa2 support was dropped (why would that happen?) or broken or
I inadvertently screwed up some config without realising it…

@2: The strange thing is that I tried reverting the kernel update (and the kernel-extra package) but that didn’t help either… Which kinda points to the fact that it isn’t the module…

The last time I had problems like that, the NM applet (kde) couldn’t connect to wireless networks anymore and it took me a while to figure out that this was because the kde4 applet was also installed and somehow disturbed the kde3 applet %-)
(Yeah, I already checked that this time ;))

Thanks, I really appreciate your help

Of course, none of this explains why what used to work, now doesn’t…

Yeah, that’s really weird

I wonder if ndiswrapper could be worth trying?

Hm, as a last resort, yeah - and if it doesn’t work with ndiswrapper either, then this would point to some other place than the driver as the source of the problem.

ginkobonsai · March 10, 2010, 12:01pm

Concerning ndiswrapper: I’m trying to use the windows driver downloaded from here:

Ralink corp.

But I can’t get a the inf file. Could you tell me how to unpack/extract the driver files from the exe? (unzip doesn’t do the job)

lwfinger · March 10, 2010, 4:28pm

On 03/10/2010 03:36 AM, ginkobonsai wrote:
>
> lwfinger;2133681 Wrote:
>> It failed step 4/4 of the 4-way handshake. If you are sure that the psk
>> value is
>> correct
> Hm, I’m pretty sure - but is there some point where it can go wrong?
> Like putting an ASCII key where a hex key is expected or somesuch? I’m
> assuming I can enter a 8-63 char plain ascii passphrase into the box
> that YaST offers me… (or into the config file)

In the ifcfg-wlanX file, the ASCII passphrase should be listed in the
WIRELESS_WPA_PSK entry. Only WEP needs to use the Hex key. All systems use the
same method to convert a WPA/WPA2 phrase to the key, whereas in WEP there are at
least two. As one never knows if the STA and the AP are using the same one, the
only safe way is to use the WEP hex key.

>> then the driver seems not to support WPA2.
> Now THAT seems really weird. Because I had it working before, so
> either
> 1) the driver that is used by the system somehow got switched to one
> that doesn’t work or
> 2) the driver used was updated and wpa2 support was dropped (why would
> that happen?) or broken or
> 3) I inadvertently screwed up some config without realising it…
>
> @2: The strange thing is that I tried reverting the kernel update (and
> the kernel-extra package) but that didn’t help either… Which kinda
> points to the fact that it isn’t the module…
>
> The last time I had problems like that, the NM applet (kde) couldn’t
> connect to wireless networks anymore and it took me a while to figure
> out that this was because the kde4 applet was also installed and somehow
> disturbed the kde3 applet %-)
> (Yeah, I already checked that this time ;))
>
>
> prhunt;2133695 Wrote:
>> I think it might be possible to force a WPA (as opposed to WPA2)
>> connection by hand-tweaking the config file. There’s information on
>> this in the ifcfg.template mentioned earlier. I’ll check back later in
>> the day (work intervenes now) and will suggest some settings if you’ve
>> made no progress.
> Thanks, I really appreciate your help
>
>>
>> Of course, none of this explains why what used to work, now doesn’t…
> Yeah, that’s really weird
>
>>
>> I wonder if ndiswrapper could be worth trying?
> Hm, as a last resort, yeah - and if it doesn’t work with ndiswrapper
> either, then this would point to some other place than the driver as the
> source of the problem.

As I do not do ndiswrapper, I will be ignoring that part of the thread. The
other component that could have been updated and causing the failure is
ndiswrapper. What version are you running? Use the command

/usr/sbin/wpa_supplicant

and post the first line of the output. My system shows v0.6.9.

prhunt · March 12, 2010, 12:42am

If you haven’t made any headway, here are a couple of manual hacks to try.

In your ifcfg-ra0 config file, you need to change or add the following as appropriate:

For WPA:

WIRELESS_WPA_PROTO='wpa"
WIRELESS_CIPHER_PAIRWISE='tkip'
WIRELESS_CIPHER_GROUP='tkip'

For WPA2:

WIRELESS_WPA_PROTO='rsn"
WIRELESS_CIPHER_PAIRWISE='ccmp tkip'
WIRELESS_CIPHER_GROUP='ccmp tkip'

You could try different scan mode settings:

WIRELESS_AP_SCANMODE='x'

where x = 0, 1 (default) or 2

Try the above manual hacks first. If you cant extract the XP drivers for ndiswrapper, then PM me.

Paul