Re: [zd1211-devs] 3COM 3CRUSB10075 fails to connect to WEP network
Richard Hughes wrote: > The error should probably not have said: > > SoftMAC: Open Authentication with 00;00 failed, error code: 13 > > But instead: > > SoftMAC: Open Authentication with 00;00 failed: Requested authentication > algorithm not supported (try open mode instead of shared key) > > I would happily send a patch for that if you want. Send a patch to linux-wireless and netdev with me on CC. I'm not sure if it will be accepted, as in general printk isn't supposed to be an informative error reporting procedure and the user shouldn't be expected to look there in this situation. The correct solution would be to propogate the IEEE 802.11 authentication frame status field to userspace in some sane fashion. Also, softmac development is mostly stopped anyway. If you're going to hack on this, check out John's wireless-dev.git tree and fix things up in d80211/cfg80211 instead :) > I've no idea why ipw3945 works and zd1211 does not work with "shared > key" access points, although if it's a design decision it should > probably be propagated to the user via NetworkManager. ipw3945 probably handles it in hardware or defaults to some automatic mode (i.e. if we receive a challenge inside the authentication response, then go into shared key mode and send the encrypted challenge in a response). This is debatable as to whether it should be default behaviour: it would make things easier for the user in this situation, but makes it easy for a malicious user to set up a fake AP and remotely retrieve your WEP key without you being aware. Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] 3COM 3CRUSB10075 fails to connect to WEP network
On Wed, 2007-02-14 at 08:21 -0500, Daniel Drake wrote: > Hi Richard! Remember me? Of course! You *still* owe me that beer :-) > Richard Hughes wrote: > > SoftMAC: Scanning finished: scanned 11 channels starting with channel 1 > > SoftMAC: Queueing Authentication Request to 00:11:95:19:a7:4c > > SoftMAC: Cannot associate without being authenticated, requested > > authentication > > SoftMAC: Sent Authentication Request to 00:11:95:19:a7:4c. > > SoftMAC: Already associating or associated to 00:11:95:19:a7:4c > > SoftMAC: Open Authentication with 00:11:95:19:a7:4c failed, error code: > > 13 > > This error code comes from the access point - it rejected you. So at > frame packet transmission/reception at this level seems to be working. > > Error code 13 means "Requested authentication algorithm not supported". > This probably means that the access point requires you to use shared key > authentication (as opposed to open auth). Ahh yes. Not my access point (at my girlfriends) and it is set to shared. The error should probably not have said: SoftMAC: Open Authentication with 00;00 failed, error code: 13 But instead: SoftMAC: Open Authentication with 00;00 failed: Requested authentication algorithm not supported (try open mode instead of shared key) I would happily send a patch for that if you want. > If you have administrative access to the AP you may want to disable > shared key authentication and go back to open mode. Shared key is really > insecure, it basically gives your WEP key away to anyone nearby > sniffing the network. I do (default usernames and passwords ;-) and it is indeed working with open mode. I've no idea why ipw3945 works and zd1211 does not work with "shared key" access points, although if it's a design decision it should probably be propagated to the user via NetworkManager. Thanks for your help with this. Richard. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] 3COM 3CRUSB10075 fails to connect to WEP network
On Wed, 2007-02-14 at 11:02 +, Richard Hughes wrote: > I have a 3COM 3CRUSB10075 wireless USB device which does not work with > Fedora Core 6. > I'm using the latest v1.3 firmware from sourceforge with a 2.6.20 > vanilla kernel. > I've tried zd1211rw drivers from 2.6.19, 2.6.20 and also the git repo at > http://dsd.object4.net/git/zd1211.git > It has a USB id of 0ace:1215 ZyDAS. > > On insert, I get the following in dmesg. > > zd1211rw 5-1:1.0: firmware version 4725 > zd1211rw 5-1:1.0: zd1211b chip 0ace:1215 v4810 high 00-16-e0 AL2230_RF > pa0 ---N > zd1211rw 5-1:1.0: eth1 I have the 'same' adapter. Note that 3Com actually produces two versions of this adapter, distinguishable by serial number and USB ID. For example, when I plug mine in I get: << usb 1-1: new full speed USB device using uhci_hcd and address 3 << usb 1-1: configuration #1 chosen from 1 choice << usb 1-1: reset full speed USB device using uhci_hcd and address 3 << zd1211rw 1-1:1.0: firmware version 4605 << zd1211rw 1-1:1.0: zd1211 chip 6891:a727 v4330 full 00-0f-cb RF2959_RF << pa0 g--- << zd1211rw 1-1:1.0: eth1 3Com distributes 2 different sets of drivers for this adapter, based on serial number: One driver for adapters with serials starting with 0300/ and another one for serials starting with 0100/ and 0200/. They warn that installing the wrong driver may leave your adapter inoperable (!). I got this info from http://www.3com.com/products/en_US/result.jsp?selected=all&sort=effdt&sku=3CRUSB10075&order=desc HTH! Will Keaney -- Build a person a fire, and they may be warm for a day. Set that person on fire, and they will be warm for the rest of their life. GnuPG Public Key ID 1024D/203C7431. Public Key Available From http://keyserv.nic-se.se:11371/#extract signature.asc Description: This is a digitally signed message part - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] 3COM 3CRUSB10075 fails to connect to WEP network
Hi Richard! Remember me? Richard Hughes wrote: > SoftMAC: Scanning finished: scanned 11 channels starting with channel 1 > SoftMAC: Queueing Authentication Request to 00:11:95:19:a7:4c > SoftMAC: Cannot associate without being authenticated, requested > authentication > SoftMAC: Sent Authentication Request to 00:11:95:19:a7:4c. > SoftMAC: Already associating or associated to 00:11:95:19:a7:4c > SoftMAC: Open Authentication with 00:11:95:19:a7:4c failed, error code: > 13 This error code comes from the access point - it rejected you. So at frame packet transmission/reception at this level seems to be working. Error code 13 means "Requested authentication algorithm not supported". This probably means that the access point requires you to use shared key authentication (as opposed to open auth). I'm not sure how you would set this in networkmanager, but on the console you would do: ifconfig eth2 up iwconfig eth2 key restricted iwconfig eth2 essid Then check dmesg to make sure authentication has completed. If you have administrative access to the AP you may want to disable shared key authentication and go back to open mode. Shared key is really insecure, it basically gives your WEP key away to anyone nearby sniffing the network. Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
[zd1211-devs] 3COM 3CRUSB10075 fails to connect to WEP network
I have a 3COM 3CRUSB10075 wireless USB device which does not work with Fedora Core 6. I'm using the latest v1.3 firmware from sourceforge with a 2.6.20 vanilla kernel. I've tried zd1211rw drivers from 2.6.19, 2.6.20 and also the git repo at http://dsd.object4.net/git/zd1211.git It has a USB id of 0ace:1215 ZyDAS. On insert, I get the following in dmesg. zd1211rw 5-1:1.0: firmware version 4725 zd1211rw 5-1:1.0: zd1211b chip 0ace:1215 v4810 high 00-16-e0 AL2230_RF pa0 ---N zd1211rw 5-1:1.0: eth1 SoftMAC: ASSERTION FAILED (0) at: net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate() SoftMAC: Associate: Scanning for networks first. SoftMAC: Associate: failed to initiate scan. Is device up? ADDRCONF(NETDEV_UP): eth2: link is not ready In NetworkManager 0.6.4 the scanned networks are shown (all at 100% signal) but attempting to connect fails every time. More log data is at the end of this emails. Ideas for how to debug this are welcome. Many thanks, Richard Hughes --- More details: NetworkManager spots the device as an "Unknown USB interface" but will not let me connect to my WEP network with dmesg output; SoftMAC: Associate: Scanning for networks first. SoftMAC: Scanning finished: scanned 11 channels starting with channel 1 SoftMAC: Queueing Authentication Request to 00:11:95:19:a7:4c SoftMAC: Cannot associate without being authenticated, requested authentication SoftMAC: Sent Authentication Request to 00:11:95:19:a7:4c. SoftMAC: Already associating or associated to 00:11:95:19:a7:4c SoftMAC: Open Authentication with 00:11:95:19:a7:4c failed, error code: 13 SoftMAC: Scanning finished: scanned 11 channels starting with channel 1 and NetworkManager --no-daemon: NetworkManager:starting... NetworkManager:eth2: Device is fully-supported using driver 'zd1211rw'. NetworkManager:nm_device_init(): waiting for device's worker thread to start NetworkManager:nm_device_init(): device's worker thread started, continuing. NetworkManager:Now managing wireless (802.11) device 'eth2'. NetworkManager:Deactivating device eth2. ... NetworkManager:User Switch: /org/freedesktop/NetworkManager/Devices/eth2 / itest NetworkManager:Deactivating device eth2. NetworkManager:Device eth2 activation scheduled... NetworkManager:Activation (eth2) started... NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) started... NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) complete. NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) starting... NetworkManager:Activation (eth2/wireless): access point 'itest' is encrypted, but NO valid key exists. New key needed. NetworkManager:Activation (eth2) New wireless user key requested for network 'itest'. NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) complete. NetworkManager:Activation (eth2) New wireless user key for network 'itest' received. NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) started... NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... NetworkManager:Activation (eth2) Stage 1 of 5 (Device Prepare) complete. NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) starting... NetworkManager:Activation (eth2/wireless): access point 'itest' is encrypted, and a key exists. No new key needed. NetworkManager:SUP: sending command 'INTERFACE_ADD eth2 wext/var/run/wpa_supplicant' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'AP_SCAN 1' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'ADD_NETWORK' NetworkManager:SUP: response was '0' NetworkManager:SUP: sending command 'SET_NETWORK 0 ssid 69333836' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 key_mgmt NONE' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 auth_alg SHARED' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 wep_key0 ' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'ENABLE_NETWORK 0' NetworkManager:SUP: response was 'OK' NetworkManager:Activation (eth2) Stage 2 of 5 (Device Configure) complete. ioctl[SIOCGIWSCAN]: Resource temporarily unavailable NetworkManager:Old device 'eth2' activating, won't change. NetworkManager:Activation (eth2/wireless): association took too long (>20s), failing activation. NetworkManager:Act
