Thread: [Ndiswrapper-general] wpa_supplicant fails with ndiswrapper andmadwifi driver for Atheros 802.11a/b
Status: Beta
Brought to you by:
pgiri
From: Michael R. <mic...@ci...> - 2004-11-01 06:38:53
|
I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip (5212 I think it is called). The card has a PCI id of vendor 0x168c, device 0x0013. wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial copy of driverloader and it works fine. The debug from wpa_supplicant indicates that the AP scan returns 0 bytes. No suitable AP is found. I am not sure where the problem lies except that it fails with both ndiswrapper and the madwifi drivers pulled from the madwifi project's cvs last wednesday. I am posting this to both the wpa_supplicant list and the ndiswrapper list. What debugs should I obtain in order to solve this problem? I ran wpa_supplicant with the -dd command line option and saw that the sacn failed. (Sorry I lost the log I captured. I will recreate it later and post it as a followup to this message.) I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried ndiswrapper 0.11 but the perl script prints out a number of error messages so went back to version 0.10). The access point is a Cisco 1100. Script I use to start the card - #!/bin/sh # # Startup the wireless card using ndiswrapper # # Cleanup in case there was a previous crash rm -rf /var/run/wpa_supplicant rm -f /etc/dhcpc/dhcpcd-wlan0.pid # modprobe ndiswrapper # sleep 2 ifconfig wlan0 up # wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -Dndiswrapper -B # sleep 5 /sbin/dhcpcd -d -t 300 -N wlan0 /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 # WPA-PSK - Cisco 1100/1200 APs network={ ssid="ssidPSK" proto=WPA key_mgmt=WPA-PSK pairwise=TKIP CCMP group=WEP104 TKIP CCMP # psk="Pre-shared-key" psk=hex_digits } Thanks, michael -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |
From: Wouter de J. <wo...@wi...> - 2004-11-01 07:46:20
|
On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote: > I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip > (5212 I think it is called). The card has a PCI id of vendor 0x168c, > device 0x0013. > > wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial copy > of driverloader and it works fine. Same problem here :( Does anyone else have this up and running with an Atheros-chip ? > Thanks, > > michael Greetings, -- WideXS http://www.widexs.nl Wouter de Jong System-Administrator Tel +31 (0)23 5698070 Fax +31 (0)23 5698099 Bijlmermeerstraat 62, 2131 HG HOOFDDORP, NL |
From: Jouni M. <jkm...@cc...> - 2004-11-04 03:33:12
|
On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote: > I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip > (5212 I think it is called). The card has a PCI id of vendor 0x168c, > device 0x0013. > > wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial copy > of driverloader and it works fine. Which NDIS driver are you using? > The debug from wpa_supplicant indicates that the AP scan returns 0 bytes. > No suitable AP is found. I am not sure where the problem lies except that > it fails with both ndiswrapper and the madwifi drivers pulled from the > madwifi project's cvs last wednesday. Can you get scan any results with 'iwlist wlan0 scan'? Can you use ndiswrapper in plaintext mode with the same AP? > What debugs should I obtain in order to solve this problem? I ran > wpa_supplicant with the -dd command line option and saw that the sacn > failed. (Sorry I lost the log I captured. I will recreate it later and > post it as a followup to this message.) That would be suitable log file for hostap (i.e., wpa_supplicant) mailing list. > I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried ndiswrapper > 0.11 but the perl script prints out a number of error messages so went back > to version 0.10). The access point is a Cisco 1100. Which firmware version is used in the AP? I haven't tested ndiswrapper with Cisco APs, but wpa_supplicant and Atheros-based cards have worked nicely with Cisco APs. On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote: > Does anyone else have this up and running with an Atheros-chip ? Yes, worked fine with ndiswrapper the last time I tested (a long time ago, though). -- Jouni Malinen PGP id EFC895FA |
From: Michael R. <mic...@ci...> - 2004-11-10 20:19:20
|
Sorry for the delay in responding - I was out of town for a few days. Jouni Malinen wrote: > On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote: > > >>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip >>(5212 I think it is called). The card has a PCI id of vendor 0x168c, >>device 0x0013. >> >>wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial copy >>of driverloader and it works fine. > > > Which NDIS driver are you using? The driver provided by Cisco with the card. From the log- ndiswrapper: driver net21 (,08/27/2004,1.2.0.3) added I tried with a Linksys WPC55AG card last night (also Atheros based). Same failure. The Linksys card also works fine with driverloader. The Linksys driver - ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added > > >>The debug from wpa_supplicant indicates that the AP scan returns 0 bytes. >>No suitable AP is found. I am not sure where the problem lies except that >>it fails with both ndiswrapper and the madwifi drivers pulled from the >>madwifi project's cvs last wednesday. > > > Can you get scan any results with 'iwlist wlan0 scan'? Can you use > ndiswrapper in plaintext mode with the same AP? Yes to both. I also tried a WRT54GS last night and neither card worked with ndiswrapper but both work fine with driverloader. > > >>What debugs should I obtain in order to solve this problem? I ran >>wpa_supplicant with the -dd command line option and saw that the sacn >>failed. (Sorry I lost the log I captured. I will recreate it later and >>post it as a followup to this message.) > > > That would be suitable log file for hostap (i.e., wpa_supplicant) > mailing list. > > >>I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried ndiswrapper >>0.11 but the perl script prints out a number of error messages so went back >>to version 0.10). The access point is a Cisco 1100. > > > Which firmware version is used in the AP? I haven't tested ndiswrapper > with Cisco APs, but wpa_supplicant and Atheros-based cards have worked > nicely with Cisco APs. IOS 12.3(2)JA in the Cisco. Sveasoft satori released in the WRT54GS > > > On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote: > > >>Does anyone else have this up and running with an Atheros-chip ? > > > Yes, worked fine with ndiswrapper the last time I tested (a long time > ago, though). > Something seems to have broken since you tested it. I have the same failure with ndiswrapper 0.10 and 0.11 so it has been broken at least that long. (Re-tested both last night.) michael -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |
From: Michael R. <mic...@ci...> - 2004-11-11 19:04:10
|
Just a quick follow up. I tried an 802.11a access point last night (D-Link DWL-7100AP). Same problem. Atheros based cards do not work using ndiswrapper and WPA-PSK (wpa_supplicant). Didn't try madwifi last night but it hasn't worked in past tests so I expect it fail with this AP also. Driverloader works fine using the same wireless card drivers, same wpa_supplicant with same wpa_supplicant config file. Only change was to specify ndiswrapper driver vs hostap driver (-Dndiswrapper vs -Dhostap). Anyone have any ideas how to debug this? michael Michael Reilly wrote: > Sorry for the delay in responding - I was out of town for a few days. > > Jouni Malinen wrote: > >> On Sun, Oct 31, 2004 at 10:38:39PM -0800, Michael Reilly wrote: >> >> >>> I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g >>> chip (5212 I think it is called). The card has a PCI id of vendor >>> 0x168c, device 0x0013. >>> >>> wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial >>> copy of driverloader and it works fine. >> >> >> >> Which NDIS driver are you using? > > The driver provided by Cisco with the card. From the log- > > ndiswrapper: driver net21 (,08/27/2004,1.2.0.3) added > > I tried with a Linksys WPC55AG card last night (also Atheros based). > Same failure. The Linksys card also works fine with driverloader. > > The Linksys driver - > > ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added > >> >> >>> The debug from wpa_supplicant indicates that the AP scan returns 0 >>> bytes. No suitable AP is found. I am not sure where the problem lies >>> except that it fails with both ndiswrapper and the madwifi drivers >>> pulled from the madwifi project's cvs last wednesday. >> >> >> >> Can you get scan any results with 'iwlist wlan0 scan'? Can you use >> ndiswrapper in plaintext mode with the same AP? > > > Yes to both. I also tried a WRT54GS last night and neither card worked > with ndiswrapper but both work fine with driverloader. > >> >> >>> What debugs should I obtain in order to solve this problem? I ran >>> wpa_supplicant with the -dd command line option and saw that the sacn >>> failed. (Sorry I lost the log I captured. I will recreate it later >>> and post it as a followup to this message.) >> >> >> >> That would be suitable log file for hostap (i.e., wpa_supplicant) >> mailing list. >> >> >>> I am using wpa_supplicant 2.5 and ndiswrapper 0.10 (I tried >>> ndiswrapper 0.11 but the perl script prints out a number of error >>> messages so went back to version 0.10). The access point is a Cisco >>> 1100. >> >> >> >> Which firmware version is used in the AP? I haven't tested ndiswrapper >> with Cisco APs, but wpa_supplicant and Atheros-based cards have worked >> nicely with Cisco APs. > > IOS 12.3(2)JA in the Cisco. Sveasoft satori released in the WRT54GS > >> >> >> On Mon, Nov 01, 2004 at 08:46:12AM +0100, Wouter de Jong wrote: >> >> >>> Does anyone else have this up and running with an Atheros-chip ? >> >> >> >> Yes, worked fine with ndiswrapper the last time I tested (a long time >> ago, though). >> > Something seems to have broken since you tested it. I have the same > failure with ndiswrapper 0.10 and 0.11 so it has been broken at least > that long. (Re-tested both last night.) > > michael -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |
From: Michael R. <mic...@ci...> - 2004-11-12 07:38:59
|
I was asked to post the output of 'iwlist wlan0 scan' on my Atheros card to help diagnose the problem of the card not working with ndiswrapper but working fine with driverloader. With ndiswrapper 0.11 - bash-2.05b# modprobe ndiswrapper bash-2.05b# ifconfig wlan0 up bash-2.05b# iwlist wlan0 scan wlan0 No scan results bash-2.05b# iwlist wlan0 scan wlan0 No scan results bash-2.05b# iwlist wlan0 scan wlan0 No scan results One time entering the iwlist command resulted in output. However I could not get any results other than "No scan results" no matter how many times I tried after I got this once - bash-2.05b# iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:0F:3D:FA:9E:2A ESSID:"xxxxxxxx" Protocol:IEEE 802.11g Mode:Managed Frequency:2.462GHz Quality:0/100 Signal level:-43 dBm Noise level:-256 dBm Encryption key:on Bit Rate:1Mb/s Bit Rate:2Mb/s Bit Rate:5.5Mb/s Bit Rate:11Mb/s Bit Rate:6Mb/s Bit Rate:12Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:9Mb/s Bit Rate:18Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Extra:bcn_int=100 Extra:atim=0 Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202 Cell 02 - Address: 00:40:96:A0:BE:EB ESSID:"yyyyyyyy" Protocol:IEEE 802.11b Mode:Managed Frequency:2.442GHz Quality:0/100 Signal level:-48 dBm Noise level:-256 dBm Encryption key:on Bit Rate:11Mb/s Extra:bcn_int=100 Extra:atim=0 Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2022800 Cell 03 - Address: 00:0F:3D:FA:9E:2A ESSID:"zzzzzzzz" Protocol:IEEE 802.11a Mode:Managed Frequency:5.26GHz Quality:0/100 Signal level:-25 dBm Noise level:-256 dBm Encryption key:on Bit Rate:6Mb/s Bit Rate:9Mb/s Bit Rate:12Mb/s Bit Rate:18Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Extra:bcn_int=100 Extra:atim=0 Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202 I note that the Quality is shown as 0/100. Perhaps this is not supported by ndiswrapper? For reference with driverloader 2.09 - bash-2.05b# modprobe driverloader bash-2.05b# ifconfig eth1 up bash-2.05b# iwlist eth1 scan eth1 Scan completed : Cell 01 - Address: 00:0F:3D:FA:9E:2A ESSID:"xxxxxxxx" Mode:Managed Frequency:2.462GHz Quality:100/100 Signal level:-52 dBm Noise level:-154 dBm Encryption key:on Bit Rate:1Mb/s Bit Rate:2Mb/s Bit Rate:5.5Mb/s Bit Rate:11Mb/s Bit Rate:6Mb/s Bit Rate:12Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:9Mb/s Bit Rate:18Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Extra:bcn_int=100 Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202 Cell 02 - Address: 00:40:96:A0:BE:EB ESSID:"yyyyyyyy" Mode:Managed Frequency:2.442GHz Quality:100/100 Signal level:-44 dBm Noise level:-154 dBm Encryption key:on Bit Rate:11Mb/s Extra:bcn_int=100 Extra:wpa_ie=dd180050f20101000050f20201000050f20201000050f2022800 Cell 03 - Address: 00:0F:3D:FA:9E:2A ESSID:"zzzzzzzz" Mode:Managed Frequency:5.26GHz Quality:100/100 Signal level:-27 dBm Noise level:-154 dBm Encryption key:on Bit Rate:6Mb/s Bit Rate:9Mb/s Bit Rate:12Mb/s Bit Rate:18Mb/s Bit Rate:24Mb/s Bit Rate:36Mb/s Bit Rate:48Mb/s Bit Rate:54Mb/s Extra:bcn_int=100 Extra:wpa_ie=dd160050f20101000050f20201000050f20201000050f202 Thanks, michael -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |
From: Jouni M. <jkm...@cc...> - 2004-11-21 05:04:24
Attachments:
ndiswrapper.wpa-eap.patch
|
On Wed, Nov 10, 2004 at 12:19:06PM -0800, Michael Reilly wrote: > >>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip > >>(5212 I think it is called). The card has a PCI id of vendor 0x168c, > >>device 0x0013. > >> > >>wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial > >>copy of driverloader and it works fine. > ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added I tested with another AR5212-based a/b/g card and the same driver version (2.4.2.33) using the current CVS snapshot of ndiswrapper and Linux 2.4.28. This worked in my tests with WPA-PSK. In couple of test cases with Linksys WRT54G as the AP, it took few attempts to get group key handshake completed, though. This may be some kind of timing related issue with the client not receiving encrypted frames immediately after the keys have been configured. The tests with another AP (Gateway 7001ag) were succeeded on the first try. This AP has a longer timeout for group key handshake, which could explain the behavior. WPA-RADIUS (key_mgmt=WPA+IEEE 802.1X) was not apparently implemented at all in ndiswrapper (I would assume it was just forgotten). I added support for it and this seemed to allow association and completion of IEEE 802.1X + WPA authentication. The attached patch against the ndiswrapper CVS was enough to get this working and it would be nice to see it being added to the next ndiswrapper release. I tested this with both Atheros and Broadcom based cards. There seems to be some issues with both cards as far as reliability in getting packets through during the authentication is concerned.. Some of the IEEE 802.1X packets seem to disappear and I needed to use shorter EAPOL state machine timeouts to get authentication more reliable. Another issue was the failure in getting group key handshake done in some test runs that I mentioned above. -- Jouni Malinen PGP id EFC895FA |
From: Michael R. <mic...@ci...> - 2004-11-22 03:59:32
|
I just tried 0.12rc3 with my two Atheros cards against a Cisco 1100 AP using WPA-PSK. It failed with both cards. It may be related to the timing related problems you are seeing. I have been busy at work so haven't had a chance to play with this a lot michael Jouni Malinen wrote: > On Wed, Nov 10, 2004 at 12:19:06PM -0800, Michael Reilly wrote: > > >>>>I have a Cisco CB21AG card which is based on the Atheros 802.11a/b/g chip >>>>(5212 I think it is called). The card has a PCI id of vendor 0x168c, >>>>device 0x0013. >>>> >>>>wpa_supplicant fails when I try to use WPA-PSK. I downloaded a trial >>>>copy of driverloader and it works fine. > > >> ndiswrapper: driver ar5211.sys (,12/03/2003,2.4.2.33) added > > > I tested with another AR5212-based a/b/g card and the same driver > version (2.4.2.33) using the current CVS snapshot of ndiswrapper and > Linux 2.4.28. This worked in my tests with WPA-PSK. In couple of test > cases with Linksys WRT54G as the AP, it took few attempts to get group > key handshake completed, though. This may be some kind of timing related > issue with the client not receiving encrypted frames immediately after > the keys have been configured. The tests with another AP (Gateway > 7001ag) were succeeded on the first try. This AP has a longer timeout > for group key handshake, which could explain the behavior. > > WPA-RADIUS (key_mgmt=WPA+IEEE 802.1X) was not apparently implemented at > all in ndiswrapper (I would assume it was just forgotten). I added > support for it and this seemed to allow association and completion of > IEEE 802.1X + WPA authentication. The attached patch against the > ndiswrapper CVS was enough to get this working and it would be nice to > see it being added to the next ndiswrapper release. > > I tested this with both Atheros and Broadcom based cards. There seems to > be some issues with both cards as far as reliability in getting packets > through during the authentication is concerned.. Some of the IEEE 802.1X > packets seem to disappear and I needed to use shorter EAPOL state > machine timeouts to get authentication more reliable. Another issue was > the failure in getting group key handshake done in some test runs that I > mentioned above. > -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |
From: Christian K. <chr...@gm...> - 2004-11-22 21:15:14
|
Hello, the ndiswrapper-version: v0.11 compiled with DEBUG=3D3 on kernel 2.4.26 linked against uClib26, running on rtl8180L-Chipset iwconfig -v : iwconfig Version 26 Compatible with Wireless Extension v16 or earlier, Currently compiled with Wireless Extension v16. Kernel Currently compiled with Wireless Extension v16. eth1 Recommend Wireless Extension v0 or later, Currently compiled with Wireless Extension v16. everything works fine on v0.10. This fine-working v0.10 release is an opt for the fli4l-routerproject. I've tried to port my opt to v0.11, because somebody asked for it because of his only in v0.11 suppoted usb-wireless-stick. THE PROBLEM: the last of the following commands is producing an error: iwconfig eth1 enc aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 iwconfig eth1 enc [1] aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 iwconfig eth1 enc [2] 5bd0-7914-48d1-cc3f-3dd5-a4b1-22 iwconfig eth1 enc [3] a1af-8a5b-2f56-5c13-bdde-40c4-df iwconfig eth1 enc [4] 1cfc-bf1e-9df8-fda5-a2a2-efce-f9 Error for wireless request "Set Encode" (8B2A) : SET failed on device eth1 ; Invalid argument. iwconfig of this: fli4l 2.1.8 # iwconfig eth1 eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" Mode:Managed Frequency:2.437GHz Access Point: = 00:09:5B:B1:59:D2 Bit Rate=3D11Mb/s Tx-Power:20 dBm Sensitivity=3D0/3 RTS thr=3D2432 B Fragment thr=3D2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-51 dBm Noise level:-256 = dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Setting only key 1-3 works, I see the router everything is fine. here is the output of the 'working' iwconfig eth1: fli4l 2.1.8 # iwconfig eth1 eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" Mode:Managed Frequency:2.437GHz Access Point: = 00:09:5B:B1:59:D2 Bit Rate=3D11Mb/s Tx-Power:20 dBm Sensitivity=3D0/3 RTS thr=3D2432 B Fragment thr=3D2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-51 dBm Noise level:-256 = dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 The dmesg (/tmp/syslog.txt is the dmsg-output)of:=20 echo "">/tmp/syslog.txt;iwconfig eth1 enc [3] = a1af-8a5b-2f56-5c13-bdde-40c4-df;echo = "############################">>/tmp/syslog.txt;iwconfig eth1 enc [4] = 1cfc-bf1e-9df8-fda5-a2a2-efce-f9;echo = "############################">>/tmp/syslog.txt Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 3 Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_essid:47): ssid =3D = 'TESTCK' Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_essid:56): Exit Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit ############################ Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 4 Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:633): encryption = index out of range (4) Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:634): Exit ############################ [...] what i've done wrong? Is there any missing infomation i can deliver for = solving this problem? Christian |
From: Christian K. <chr...@gm...> - 2004-11-22 21:59:53
|
Ah, sorry, i love this nice c&p-errors, the working looks like > Setting only key 1-3 works, I see the router everything is fine. > here is the output of the 'working' iwconfig eth1: fli4l 2.1.8 # iwconfig eth1 enc = aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 [1] > fli4l 2.1.8 # iwconfig eth1 eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" Mode:Managed Frequency:2.437GHz Access Point: = 00:09:5B:B1:59:D2 Bit Rate=3D11Mb/s Tx-Power:20 dBm = Sensitivity=3D0/3 RTS thr=3D2432 B Fragment thr=3D2432 B Encryption key:AA2F-2A08-0DD7-EC20-5BDC-C2CC-30 = Security mode:restricted Power Management:off Link Quality:100/100 Signal level:-50 dBm Noise = level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid = frag:0 Tx excessive retries:0 Invalid misc:0 Missed = beacon:0 BUT: it is only the first key accepted, because it is the valid one. if i do something like this for setting all three keys=20 fli4l 2.1.8 # iwconfig eth1 enc aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 = [1] fli4l 2.1.8 # iwconfig eth1 enc 5bd0-7914-48d1-cc3f-3dd5-a4b1-22 = [2] fli4l 2.1.8 # iwconfig eth1 enc a1af-8a5b-2f56-5c13-bdde-40c4-df = [3] fli4l 2.1.8 # iwconfig eth1 key [1] and after this iwconfig, i get fli4l 2.1.8 # iwconfig eth1 eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" Mode:Managed Frequency:2.437GHz Access = Point: 00:09:5B:B1:59:D2 Bit Rate=3D11Mb/s Tx-Power:20 dBm = Sensitivity=3D0/3 RTS thr=3D2432 B Fragment thr=3D2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-52 dBm = Noise level:-256 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx = invalid frag:0 Tx excessive retries:0 Invalid misc:0 = Missed beacon:0 the same for echo "">/tmp/syslog.txt;iwconfig eth1 key = aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 \ key 5bd0-7914-48d1-cc3f-3dd5-a4b1-22 \ key a1af-8a5b-2f56-5c13-bdde-40c4-df \ key [1]; echo = "############################">>/tmp/syslog.txt; \ iwconfig>>/tmp/syslog.txt;echo = "############################">>/tmp/syslog.txt; \ cp /tmp/syslog.txt /tmp/syslog.txt.test results in: cat /tmp/syslog.txt.test; Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 0 Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:47): ssid =3D = 'TESTCK' Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:56): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 0 Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:47): ssid =3D = 'TESTCK' Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:56): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 0 Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:47): ssid =3D = 'TESTCK' Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:56): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:630): index =3D 1 Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:47): ssid =3D = 'TESTCK' Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo = is at c287d6cf Nov 23 01:19:16 fli4l kernel: ndiswrapper (dosetinfo:205): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (set_essid:56): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit ############################ Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_encr:548): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_encr:553): index =3D 0 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_encr:617): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_essid:93): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_essid:107): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_ap_address:482): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (get_ap_address:464): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (get_ap_address:471): = 00:09:5b:b1:59:d2 Nov 23 01:19:16 fli4l kernel: ndiswrapper (get_ap_address:472): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_ap_address:487): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_mode:163): Enter Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (iw_get_mode:187): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:158): Enter query is = at c287ec01 Nov 23 01:19:16 fli4l kernel: ndiswrapper (doquery:175): Exit eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" Mode:Managed Frequency:2.437GHz Access Point: = 00:09:5B:B1:59:D2 Bit Rate=3D11Mb/s Tx-Power:20 dBm Sensitivity=3D0/3 RTS thr=3D2432 B Fragment thr=3D2432 B Encryption key:off Power Management:off Link Quality:100/100 Signal level:-51 dBm Noise level:-256 = dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 ############################ the driver doesn't accept the last key [1] :-( by the way the 'cat /etc/ndiswrapper/rtl8180/1799:6001:1799:6001.conf': = -> NdisVersion|0x50001 Environment|1 BusType|5 ndis_version|Realtek,04/29/2004,5.169.0429.2004 NetworkAddress|000000000000 Channel|1 PowerSaveMode|0 SSID|ANY NetworkType|1 DefaultKeyID|0 DefaultKey0| DefaultKey1| DefaultKey2| DefaultKey3| FastRoaming|0 AdHocRateAdaptive|1 ShortRetryLimit|127 LongRetryLimit|127 <- Christian |
From: Toby C. <tco...@di...> - 2004-11-23 06:51:49
|
Hi, There is actually an error in the index checking code which is failing on >= max_key instead of > (ie valid index's are 0-4, not 0-3 where 0 just means active index) Ive been meaning to post a patch for this but havent had the time to get cvs working to test it completely.. There is also another bug relating to a block of code at the end of the set function where if no key data is given (ie in the case of iwconfig wlan0 enc [1]) the key is disabled. again ive been meaning to sort a patch but havent had the time, it should be pretty easy to fix. Toby Collett Christian Kneisel wrote: >Hello, > >the ndiswrapper-version: v0.11 compiled with DEBUG=3 on kernel 2.4.26 >linked against uClib26, running on rtl8180L-Chipset >iwconfig -v : > iwconfig Version 26 > Compatible with Wireless Extension v16 or earlier, > Currently compiled with Wireless Extension v16. > Kernel Currently compiled with Wireless Extension v16. > eth1 Recommend Wireless Extension v0 or later, > Currently compiled with Wireless Extension v16. > >everything works fine on v0.10. This fine-working v0.10 release is an >opt for the fli4l-routerproject. >I've tried to port my opt to v0.11, because somebody asked for it >because of his only in v0.11 suppoted usb-wireless-stick. > >THE PROBLEM: >the last of the following commands is producing an error: > iwconfig eth1 enc aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 > iwconfig eth1 enc [1] aa2f-2a08-0dd7-ec20-5bdc-c2cc-30 > iwconfig eth1 enc [2] 5bd0-7914-48d1-cc3f-3dd5-a4b1-22 > iwconfig eth1 enc [3] a1af-8a5b-2f56-5c13-bdde-40c4-df > iwconfig eth1 enc [4] 1cfc-bf1e-9df8-fda5-a2a2-efce-f9 > Error for wireless request "Set Encode" (8B2A) : > SET failed on device eth1 ; Invalid argument. >iwconfig of this: >fli4l 2.1.8 # iwconfig eth1 >eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" > Mode:Managed Frequency:2.437GHz Access Point: 00:09:5B:B1:59:D2 > Bit Rate=11Mb/s Tx-Power:20 dBm Sensitivity=0/3 > RTS thr=2432 B Fragment thr=2432 B > Encryption key:off > Power Management:off > Link Quality:100/100 Signal level:-51 dBm Noise level:-256 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > >Setting only key 1-3 works, I see the router everything is fine. >here is the output of the 'working' iwconfig eth1: >fli4l 2.1.8 # iwconfig eth1 >eth1 IEEE 802.11b ESSID:"TESTCK" Nickname:"fli4l" > Mode:Managed Frequency:2.437GHz Access Point: 00:09:5B:B1:59:D2 > Bit Rate=11Mb/s Tx-Power:20 dBm Sensitivity=0/3 > RTS thr=2432 B Fragment thr=2432 B > Encryption key:off > Power Management:off > Link Quality:100/100 Signal level:-51 dBm Noise level:-256 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > >The dmesg (/tmp/syslog.txt is the dmsg-output)of: >echo "">/tmp/syslog.txt;iwconfig eth1 enc [3] a1af-8a5b-2f56-5c13-bdde-40c4-df;echo "############################">>/tmp/syslog.txt;iwconfig eth1 enc [4] 1cfc-bf1e-9df8-fda5-a2a2-efce-f9;echo "############################">>/tmp/syslog.txt > >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:630): index = 3 >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo is at c287d6cf >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo is at c287d6cf >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo is at c287d6cf >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_encr_mode:537): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_essid:47): ssid = 'TESTCK' >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:188): Enter setinfo is at c287d6cf >Nov 23 00:27:33 fli4l kernel: ndiswrapper (dosetinfo:205): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (set_essid:56): Exit >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:730): Exit >############################ >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:628): Enter >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:630): index = 4 >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:633): encryption index out of range (4) >Nov 23 00:27:33 fli4l kernel: ndiswrapper (iw_set_encr:634): Exit >############################ >[...] > >what i've done wrong? Is there any missing infomation i can deliver for solving this problem? > >Christian > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://productguide.itmanagersjournal.com/ >_______________________________________________ >Ndiswrapper-general mailing list >Ndi...@li... >https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > > > > |
From: Jouni M. <jkm...@cc...> - 2004-11-28 07:41:31
|
On Sun, Nov 21, 2004 at 07:59:01PM -0800, Michael Reilly wrote: > I just tried 0.12rc3 with my two Atheros cards against a Cisco 1100 AP > using WPA-PSK. It failed with both cards. It may be related to the timing > related problems you are seeing. I have been busy at work so haven't had a > chance to play with this a lot Could you please re-test ndiswrapper with the current development branch snapshot of wpa_supplicant? I did some more testing with number of different client cards, drivers, and APs. There are indeed quite many cases where the group key handshake fails because of the client not receiving the encrypted EAPOL-Key frame. I was able to improve reliablity of the key handshakes greatly by removing some of the key clearing operations. In practice, this removed the five key delete operations that were done immediately after link up (association) event. I don't know why removing keys would cause issues in receiving encrypted unicast frames _after_ new PTK is configured just some time after this. Anyway, most of the key clearing operations are not really needed, so getting rid of them should at least speed up association a bit, if nothing else. I would like to remove the unicast key for the new AP to make sure that no old key is configured during the initial 4-Way Handshake. However, even that one operation seemed to make group key handshake unreliable. -- Jouni Malinen PGP id EFC895FA |
From: Michael R. <mic...@ci...> - 2004-12-02 23:52:07
|
I copied both ndsiwrapper and wpa_supplicant from cvs and installed both. It appears that my Atheros cards now work with the APs I've tried. I haven't tried madwifi with the new wpa_supplicant but I expect it to work also. Thank you, michael Jouni Malinen wrote: > On Sun, Nov 21, 2004 at 07:59:01PM -0800, Michael Reilly wrote: > > >>I just tried 0.12rc3 with my two Atheros cards against a Cisco 1100 AP >>using WPA-PSK. It failed with both cards. It may be related to the timing >>related problems you are seeing. I have been busy at work so haven't had a >>chance to play with this a lot > > > Could you please re-test ndiswrapper with the current development branch > snapshot of wpa_supplicant? > > I did some more testing with number of different client cards, drivers, > and APs. There are indeed quite many cases where the group key handshake > fails because of the client not receiving the encrypted EAPOL-Key frame. > > I was able to improve reliablity of the key handshakes greatly by > removing some of the key clearing operations. In practice, this removed > the five key delete operations that were done immediately after link up > (association) event. > > I don't know why removing keys would cause issues in receiving encrypted > unicast frames _after_ new PTK is configured just some time after this. > Anyway, most of the key clearing operations are not really needed, so > getting rid of them should at least speed up association a bit, if > nothing else. I would like to remove the unicast key for the new AP to > make sure that no old key is configured during the initial 4-Way > Handshake. However, even that one operation seemed to make group key > handshake unreliable. > -- ---- ---- ---- Michael Reilly mic...@ci... Cisco Systems, California |