This is a discussion on wpa supplicant help within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi y'all, i just downloaded and installed ipw2200 drivers and firmware, no problems, even scanning works. But my network ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi y'all, i just downloaded and installed ipw2200 drivers and firmware, no problems, even scanning works. But my network is protected by WPA-PSK, so i need wpa_supplicant (or is there any other way?). I downloaded the sources, created the config file like this: CONFIG_DRIVER_IPW=y CONFIG_DRIVER_WEXT=y # CONFIG_DRIVER_BSD=y # CONFIG_DRIVER_NDIS=y CONFIG_WIRELESS_EXTENSION=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MD5=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_GTC=y CONFIG_EAP_OTP=y # CONFIG_EAP_SIM=y # CONFIG_EAP_AKA=y CONFIG_EAP_PSK=y CONFIG_EAP_PAX=y CONFIG_EAP_LEAP=y and compiled it, then copied the binaries to /usr/local/bin. This is my /etc/wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 ### Associate with any open access point ### Scans/ESSID changes can be done with wpa_cli network={ ssid="ssid" scan_ssid=1 proto=WPA key_mgmt=WPA-PSK psk="topsecret" } But when i enter wpa_supplicant -B -i eth1 -c /etc/wpa_supplicant.conf -D ipw -w -dd it only prints "Daemonize.." and the command prompt appears again, while nothing is changed in iwconfig. Am i doing anything wrong? Been searching around forums, but haven't found anything else. Can someone help me pls? TIA Mahy |
| |||
| Mahy wrote: > ... when i enter > > wpa_supplicant -B -i eth1 -c /etc/wpa_supplicant.conf -D ipw -w -dd > > it only prints "Daemonize.." and the command prompt appears again, This part is normal, given that you're running wpa_supplicant as a daemon. Are you able to confirm that wpa_supplicant remains running? > while nothing is changed in iwconfig. By this, I take it to mean that you see no sign of successful association with the access point, correct? Can you run wpa_supplicant in foreground mode, perhaps with debugging output, and see if the ouput tells you anything helpful? Can you check also the access-point's logs for anything that might help? -- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems and Network analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ---------------------------------------------------------------------- |
| |||
| UPDATE: I also tried the wpa_supplicant package found at http://www.slackware.com/~alien/slac...4.7-i486-1.tgz, but the outcome was the same: nothing happened. That might suggest the problem isn't in supplicant after all, but where else? I'm quite sure the ipw firmware and driver work ok. Any help appreciated. Mahy |
| |||
| I ran it in the foreground, and this is the result: ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported Initializing interface 'eth1' conf '/etc/wpa_supplicant.conf' driver 'ipw' ctrl_interface '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=0 eapol_version=1 ap_scan=1 fast_reauth=1 Line: 15 - start of a new network block ssid - hexdump_ascii(len=16): 4b 61 72 70 61 74 73 6b 61 20 39 39 38 2f 32 34 Karpatska 998/24 scan_ssid=1 (0x1) proto: 0x1 key_mgmt: 0x2 PSK (ASCII passphrase) - hexdump_ascii(len=17): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] Priority group 0 id=0 ssid='Karpatska 998/24' Initializing interface (2) 'eth1' 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 EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 wpa_driver_ipw_init is called SIOCGIWRANGE: WE(compiled)=18 WE(source)=18 enc_capa=0xf capabilities: key_mgmt 0xf enc 0xf Own MAC address: 00:13:ce:16:a3:17 wpa_driver_ipw_set_wpa: enabled=1 wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0 Failed to set encryption. wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0 Failed to set encryption. wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0 Failed to set encryption. wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0 Failed to set encryption. wpa_driver_ipw_set_countermeasures: enabled=0 wpa_driver_ipw_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec Added interface eth1 Wireless event: cmd=0x8b06 len=8 RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added State: DISCONNECTED -> SCANNING Starting AP scan (specific SSID) Scan SSID - hexdump_ascii(len=16): 4b 61 72 70 61 74 73 6b 61 20 39 39 38 2f 32 34 Karpatska 998/24 Scan timeout - try to get results Received 551 bytes of scan results (2 BSSes) Scan results: 2 Selecting BSS from priority group 0 0: 00:13:10:15:42:ce ssid='Karpatska 998/24' wpa_ie_len=24 rsn_ie_len=0 caps=0x11 selected based on WPA IE Trying to associate with 00:13:10:15:42:ce (SSID='Karpatska 998/24' freq=0 MHz) Cancelling scan request WPA: clearing own WPA/RSN IE Automatic auth_alg selection: 0x1 wpa_driver_ipw_set_auth_alg: auth_alg=0x1 WPA: using IEEE 802.11i/D3.0 WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 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_ipw_set_drop_unencrypted: enabled=1 State: SCANNING -> ASSOCIATING Setting authentication timeout: 10 sec 0 usec EAPOL: External notification - EAP success=0 EAPOL: External notification - EAP fail=0 EAPOL: External notification - portControl=Auto Wireless event: cmd=0x8b1a len=29 Wireless event: cmd=0x8b1a len=29 Authentication with 00:00:00:00:00:00 timed out. Added BSSID 00:00:00:00:00:00 into blacklist State: ASSOCIATING -> DISCONNECTED No keys have been configured - skip key clearing EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Setting scan request: 0 sec 0 usec State: DISCONNECTED -> SCANNING .... and so on and so forth, until i presses ctrl+c. P.S. i know my ssid is published here... i don't care |
| |||
| Mahy wrote: > wpa_driver_ipw_set_wpa: enabled=1 > wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0 > Failed to set encryption. > wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0 > Failed to set encryption. > wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0 > Failed to set encryption. > wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0 > Failed to set encryption. Perhaps you haven't configured your pre-shared keys in wpa_supplicant? ("PSK" in "WPA/PSK" stands for "Pre-Shared Keys". That means both wireless stations, access-point and client, have a set of common encryption keys prior to associating ...) > P.S. i know my ssid is published here... i don't care Two points on that: - Contrary to what a lot of wireless equipment manufacturers will have you believe, your SSID is not any kind of secret. Any wireless equipment within reception range of yours can pick up the SSID (whether or not your access point broadcasts it in its beacons) when the wireless link is being used. It's sent, in the clear, as part of the overhead of every packet sent over the wireless link. - If you're still concerned, (and the rest of what I'm going to say is something that you very likely already know), the SSID is trivial to change, unless you have a large number of client systems that you don't manage yourself. -- ---------------------------------------------------------------------- Sylvain Robitaille syl@alcor.concordia.ca Systems and Network analyst Concordia University Instructional & Information Technology Montreal, Quebec, Canada ---------------------------------------------------------------------- |
| |||
| On Sat, 13 May 2006 23:27:34 -0700, Mahy wrote: > Hi y'all, > > i just downloaded and installed ipw2200 drivers and firmware, no > problems, even scanning works. But my network is protected by WPA-PSK, > so i need wpa_supplicant (or is there any other way?). I downloaded the > sources, created the config file like this: > > CONFIG_DRIVER_IPW=y > CONFIG_DRIVER_WEXT=y > # CONFIG_DRIVER_BSD=y > # CONFIG_DRIVER_NDIS=y > CONFIG_WIRELESS_EXTENSION=y > CONFIG_IEEE8021X_EAPOL=y > CONFIG_EAP_MD5=y > CONFIG_EAP_MSCHAPV2=y > CONFIG_EAP_TLS=y > CONFIG_EAP_PEAP=y > CONFIG_EAP_TTLS=y > CONFIG_EAP_GTC=y > CONFIG_EAP_OTP=y > # CONFIG_EAP_SIM=y > # CONFIG_EAP_AKA=y > CONFIG_EAP_PSK=y > CONFIG_EAP_PAX=y > CONFIG_EAP_LEAP=y > > and compiled it, then copied the binaries to /usr/local/bin. This is my > /etc/wpa_supplicant.conf: > > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=0 > > eapol_version=1 > ap_scan=1 > fast_reauth=1 > > ### Associate with any open access point > ### Scans/ESSID changes can be done with wpa_cli > network={ > ssid="ssid" > scan_ssid=1 > proto=WPA > key_mgmt=WPA-PSK > psk="topsecret" > } > > But when i enter > > wpa_supplicant -B -i eth1 -c /etc/wpa_supplicant.conf -D ipw -w -dd > > it only prints "Daemonize.." and the command prompt appears again, > while nothing is changed in iwconfig. Am i doing anything wrong? Been > searching around forums, but haven't found anything else. Can someone > help me pls? TIA > > Mahy > You may need to reconfigure your kernel, eliminating the default ieee80211 and ipw2200 modules from the kernel configuration. When I set this up, I was using a Pentium M based laptop- so I had already configured the kernel for that hardware, and that was one more tweak on top of it. You may not need to do this, but I did. The kernel was using an out-of-date centrino driver which needed to be replaced. I am not sure which version of the driver is in the current kernel source. Here was a kernel configuration that I used for 2.6.14.3 http://www.xmission.com/~ddmayne/sla...6.14.3m-acpi-7 Perhaps you could recompile the kernel, upgrading to 2.6.16.16 at the same time. You could do "make old_config" for 2.6.16.9 (using the official slackware config), then adjust for your hardware, and the wireless tweaks in my configuration. The last time I posted these instructions, these were "current" sources. They may have been updated since then. The driver: http://prdownloads.sourceforge.net/i...2.tgz?download The firmware: http://ipw2200.sourceforge.net/firmware.php?fid=6 The ieee80211: http://prdownloads.sourceforge.net/i...2.tgz?download The wpa_supplicant: http://hostap.epitest.fi/releases/wp...t-0.4.8.tar.gz The libdnet: http://prdownloads.sourceforge.net/l...ar.gz?download The libpcap: This was already on my system. I also have a 2.6.15.4 kernel for Pentium M which is already compiled, with modules, etc. I'll hold off posting that, unless you want it. -- Douglas Mayne |
| |||
| Mahy wrote: > Hi y'all, > > i just downloaded and installed ipw2200 drivers and firmware, no > problems, even scanning works. But my network is protected by WPA-PSK, > so i need wpa_supplicant (or is there any other way?). I downloaded the > sources, created the config file like this: <snip config, wpa_supplicant.conf> I use wpa_supplicant at home with wpa-psk, madwifi, and ndiswrapper, config looks just a little bit simpler: # cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 network={ ssid="xxxxx" psk="xxxxxxxxxxx" priority=5 } IIRC the priority bit isn't necessary either. Also, I've upgraded my wireless-tools package to version 28.pre13. There's a package of version 28 at http://www.slackware.com/~alien/slac...ools/pkg/10.2/ Note that I'm only going on differences between config-files, not on good knowledge of wpa_supplicant. But it can't hurt to try :-) PJ |
| |||
| Sylvain Robitaille wrote: > Perhaps you haven't configured your pre-shared keys in wpa_supplicant? That's definitely not the case. > > ("PSK" in "WPA/PSK" stands for "Pre-Shared Keys". That means both > wireless stations, access-point and client, have a set of common > encryption keys prior to associating ...) I know an awful lot about wpa and wpa-psk, no need to tell me, thx. > > P.S. i know my ssid is published here... i don't care > > Two points on that: > > - Contrary to what a lot of wireless equipment manufacturers will have > you believe, your SSID is not any kind of secret. Any wireless > equipment within reception range of yours can pick up the SSID > (whether or not your access point broadcasts it in its beacons) > when the wireless link is being used. It's sent, in the clear, > as part of the overhead of every packet sent over the wireless link. > > - If you're still concerned, (and the rest of what I'm going to say is > something that you very likely already know), the SSID is trivial > to change, unless you have a large number of client systems that > you don't manage yourself. > Thanks, i know all this too. The sole reason why i put the "P.S" was that someone in this group (or was it you?) mentioned it's unwise to publish compiled kernels, coz it might leak some personal info. Then i got a feeling most of you are security freaks. Kinda sarcasm from my part, sorry |
| |||
| Douglas Mayne wrote: > I also have a 2.6.15.4 kernel for Pentium M which is already compiled, > with modules, etc. I'll hold off posting that, unless you want it. > Whoa, you've got a kernel to offer?? Of course i'd accept it! Hope y'all won't ostracize me from now on, but not being able to use wifi is for me by far the worst news in Linux. Far worse than hosed graphics. I need it functioning ASAP to surf the Net comfortably from Slack, bowse howtos and forums (and post requests Back to the kernel: yes please, post it. TIA Mahy |
| ||||
| On Sun, 14 May 2006 13:07:07 -0700, Mahy wrote: > Douglas Mayne wrote: >> I also have a 2.6.15.4 kernel for Pentium M which is already compiled, >> with modules, etc. I'll hold off posting that, unless you want it. >> > > Whoa, you've got a kernel to offer?? Of course i'd accept it! > > Hope y'all won't ostracize me from now on, but not being able to use > wifi is for me by far the worst news in Linux. Far worse than hosed > graphics. I need it functioning ASAP to surf the Net comfortably from > Slack, bowse howtos and forums (and post requests > > Back to the kernel: yes please, post it. TIA > > Mahy > Cut and paste from a previous posting: These are the instructions. These are the approximate steps to follow. Use at your own risk. Linux kernel is GPL. GPL license applies also: http://www.xmission.com/~ddmayne2/kernel/COPYING Compiled with gcc version 3.4.5 md5sums: http://www.xmission.com/~ddmayne2/ke...6.15.4/md5sums kernel 2.6.15.4: http://www.xmission.com/~ddmayne2/ke...-acpi-2-dm.tgz kernel modules: http://www.xmission.com/~ddmayne2/ke...-acpi-2-dm.tgz Firmware: Read and accept license before using: /lib/firmware/LICENSE http://www.xmission.com/~ddmayne2/ke...rmware-2.4.tgz Includes: alsa-driver 1.0.10 (with minor patch) ieee80211-1.1.6 ipw2200-1.0.7 Intel firmware 2.4 So, to install this kernel: 0. Download and verify (md5sums) the packages linked above. 1. installpkg kernel-2.6.15.4m-acpi-2-dm.tgz 2. installpkg kernel-modules-2.6.15.4m-acpi-2-dm.tgz 2.a. Fix link to /etc/rc.d/rc.modules (maybe not necessary if you are already running a 2.6 kernel) # cd /etc/rc.d # mv rc.modules rc.modules.save # ln -s rc.modules-2.6.15.4m-acpi-2 rc.modules 3. installpkg ipw2200-firmware-2.4.tgz 4. Fix boot loader to reflect new kernel per usual drill. 4.a. Look in /boot for the vmlinuz file to load. 5. Reboot with new kernel. 6. Run alsaconf to configure sound. 7. Test if wireless is working.* 8. Test if processor scaling and acpi are working, etc. ** * Beyond the scope of this post. ** Suspend features may or may not work. They are not working correctly (yet) on the Dell D610. YMMV. Also, remember, these files compiled by me. Use at your own risk. -- Douglas Mayne |