How TO - Zydas ZD1211 on Edgy with WPA

**locust** · November 5th, 2006

i got the same problem

Code:

Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Line: 1 - start of a new network block
Line 2: unknown network field 'ssid '.
Line 3: unknown network field 'scan_ssid '.
pairwise: 0x8
Line 5: Invalid PSK '”ironlady”'.
Line 5: failed to parse psk '”ironlady”'.
key_mgmt: 0x2
proto: 0x1
Line 8: WPA-PSK accepted for key management, but no PSK configured.
Line 8: removed CCMP from group cipher list since it was not allowed for pairwise cipher
Line 8: failed to parse network block.
Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
Failed to add interface wlan0
Cancelling scan request

Here is my /etc/wpa_supplicant.conf file

Code:

network={
                ssid = "xasis"
                scan_ssid = 1
                pairwise=TKIP
                psk=”******”
                key_mgmt=WPA-PSK
                proto=WPA
        }

any help would be greatly appreciated

**shof2k** · November 5th, 2006

mmm that seems ok. Are there any other lines in your /etc/wpa_supplicant.conf?

Also what is the result of typing "dmesg|tail" in a terminal?

I thought this may be a simple typo, but it may be something else causing wpa supplicant to fail.

**locust** · November 5th, 2006

no these are all the lines in my /etc/wpa_supplicant.conf

Here is the result of "dmesg|tail"

Code:

[17179608.452000] Bluetooth: Core ver 2.8
[17179608.452000] NET: Registered protocol family 31
[17179608.452000] Bluetooth: HCI device and connection manager initialized
[17179608.452000] Bluetooth: HCI socket layer initialized
[17179608.480000] Bluetooth: L2CAP ver 2.8
[17179608.480000] Bluetooth: L2CAP socket layer initialized
[17179608.524000] Bluetooth: RFCOMM socket layer initialized
[17179608.524000] Bluetooth: RFCOMM TTY layer initialized
[17179608.524000] Bluetooth: RFCOMM ver 1.7
[17179612.256000] eth0: no IPv6 routers present

**gb5757870** · November 5th, 2006

My wpa_supplicant.conf as follows: (Since I live in a different country and no-one knows really who I am I didn't bother before with not putting my psk)

network={
ssid = Priscilla
scan_ssid = 1
pairwise=TKIP
psk=*******
key_mgmt=WPA-PSK
proto=WPA
}

And a dmesg|tail results in:
[17179666.108000] zd1205: (exit) zd1205_init, /usr/src/zd1211-driver-r83/src/zd1205.c line 8570
[17179666.108000] usbcore: registered new driver zd1211b
[17179666.276000] zd1205: (enter) zd1205_open, /usr/src/zd1211-driver-r83/src/zd1205.c line 4353
[17179666.340000] zd1205: (exit) zd1205_open, /usr/src/zd1211-driver-r83/src/zd1205.c line 4436
[17179666.344000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[17179722.692000] zd1205: (enter) zd1205_close, /usr/src/zd1211-driver-r83/src/zd1205.c line 4896
[17179722.708000] zd1205: (exit) zd1205_close, /usr/src/zd1211-driver-r83/src/zd1205.c line 4962
[17179722.824000] zd1205: (enter) zd1205_open, /usr/src/zd1211-driver-r83/src/zd1205.c line 4353
[17179722.828000] zd1205: (exit) zd1205_open, /usr/src/zd1211-driver-r83/src/zd1205.c line 4436
[17179722.832000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
elvis@elvis-desktop:~$

**catanzag** · November 6th, 2006

locust, sorry, maybe I'm wrong as you already know it, but what about line 5 error?

Originally Posted by locust

i got the same problem

Code:

....
Line 5: Invalid PSK '”ironlady”'.
Line 5: failed to parse psk '”ironlady”'.
key_mgmt: 0x2
proto: 0x1
Line 8: WPA-PSK accepted for key management, but no PSK configured.
.....

did you put directly your ascii passphrase? the psk must be codified by essid; here an example by wieman01 in http://www.ubuntuforums.org/showthread.php?t=202834.

type the following command in a terminal:

Code:

wpa_passphrase <your_essid> <your_ascii_key>

Resulting in an output like...

Code:

network={
ssid="test"
#psk="12345678"
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab1 5bbc6c52e7522f709a
}

Copy the "hex_key" (next to "psk=...") and replace <your_hex_key> in the "interfaces" files with it.

regards

catanzag

**gb5757870** · November 8th, 2006

Dunno about locust but I followed the instructions from catanzag and I'm still getting the same error.

Err, any idea guys?

**iorbell** · December 5th, 2006

Just wanted to say that this thread and how to is wonderful!! I have all my PC's here at home running Linux (always Ubuntu in the end, having tried many distros), and the one remaining nut I have not been able to crack is getting wireless working with my wpa setup. Until now that is...

Great thread. Ian

**shof2k** · December 5th, 2006

Glad it helped

I'm afraid I'm not a pure linux techie. This was really just publishing what I found out by trial and error, hoping that it made life easier for folks.

Personally I can't wait till the 2.6.18 kernel arrives with all of this built in, then I can "retire"

**logos382** · December 29th, 2006

Hi locust!
I've experimented same problem!
try to change your /etc/network/interfaces with something like this, work for me:

Code:

auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-conf managed
wpa-ssid <your_essid>
wpa-ap-scan 2
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <your_hex_key>
#wpa-conf /etc/wpa_supplicant.conf
address 192.168.1.3
netmask 255.255.255.0
network 192.168.1.0
gateway 192.168.1.1

to made <your_hex_key> look at the post suggested by catanzag! in the same post I found this configuration settings and the work-around to restar your interface at startup!

P.S.
Thanks to shof2k for his how-to! (I never compilde driver by my self)
Thanks to wieman01 for is configuration setting!

**logos382** · December 29th, 2006

As I sayd before a followed the great how-to of shof2k! compiling end without error
My ZyAIR G-220 work fine. But after a while(1-5 hours), my nettraffic crashes. dmesg reports something like this:

Code:

[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] 1211_readl failed for 5 attempts...Very Serious<3>zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211: failed reg_urb
[17191401.116000] zd1211:USB ST Code = -19
[17191401.116000] zd1211_writel failed for 5 attempts

I tried it with the r83 and r80 both same problem.

Problem involving also USB because when the dongle crash i can't acces to my HDD connected via USB. (sopping in the middle of episode of Lost