WPA: Unsupported TKIP Group Cipher key length 13 (13)

ipw2200 should be pretty non-problematic.

Can you provide logs according to this:http://www.ubuntuforums.org/showpost.php?p=843493&postcount=31

Also, post you /etc/network/interfaces

this is what i got ,after kill NetworkManager, knetworkmanager, launch them both and check if everything is well launch, in the konsole where i launch NetworkManager

this is what i got ,after kill NetworkManager, knetworkmanager, launch them both and check if everything is well launch, in the konsole where i launch knetworkmanager

this is what i got when i check process after killing NetworkManager and knetworkmanager and relaunch them.

this is my interfaces file. With this config ifup only works when i configure my wifi to use wep key.

this is what show knetwork-manager when i try to connect.

What happens if you uncomment the 2 lines in /etc/network/interfaces

#auto eth1
#iface eth1 inet dhcp

 to be

auto eth1
iface eth1 inet dhcp

uncomment auto eth1 and iface eth1 inet dhcp in /etc/network/interfaces does the same thing.

I have to use "noacpi" as kernel parameter to boot with my laptop. I don't know if it can help to resolve the bug.

1. knetworkmanager needs to be ran as a normal user not via sudo. If ran via sudo, it is running as root and will look in root's home directory for the kwallet which contains the password for your wireless link. I've just ran knetworkmanager as a normal user and it has logged in.

2. I miss configured knetworkmanager initially, so I removed the file ~/.kde/share/config/knetworkmanagerrc You may just want to stop knetworkmanager and rename this file. Then start knetworkmanager and set up your wireless link again.

3. What is in your /etc/default/wpasupplicant file? Does the line starting OPTIONS using the flag "-D wext" as post linux kernel 2.6.13 the wpasupplicant driver type for ipw2200 chips is wext (inbuilt wireless api). This tripped me up when manually configuring my laptop to use wpasupplicant.

acccording to your message i look /etc/default/wpasupplicant and change the line "INTERFACES=EDIT" with "INTERFACES=eth1"
it changes radically the things : now network-manager try to connect but it can't due to no wpa-key find log in the next attachment. I try to find why the key have not been store and why he don't ask me to give it but i didn't find.

what i got in tje konsole where i launch NetworkManager, i got approximatly nothing in the konsole where i launch knetworkmanager

it's what i have in konsole where i launch networkmanager when i try to connect manually to network and gives my wpa key

it's what i have in konsole where i launch knetworkmanager when i try to connect manually to network and gives my wpa key

Hi, it looks like knetworkmanager is getting an invalid password from kwallet. Try opening the wallet and renaming the knetworkmanager passwords key name for your wireless link (from WANADOO-F177 to OLDESSID for example). This will force knetworkmanager to ask for a password when you try to connect as it won't find a password for your ESSID.

Hopefully this will help.

Is this still reproducable with latest n-m and knetworkmanager (and following previous post)?
I have similar config (ipw2200 + knm) and everything works as it should.

currently i don't have time to make tests and when i install dapper i keep an hold /home from a breezy flight 3! i'll make a fresh install and tell you.

with a totally new install of kubuntu dapper flight 6 with a new / and a new home i tryed to connect again on my wpa network and it does the same thing. it ask me my wpa key it stored it in kwallet (it doesn't work before due to my old /home configuration) and it stops at eth1 activation (28% of logging processus)
I've follow this instructions : https://wiki.ubuntu.com/DapperKNetworkmanager to install knetwork. it works fine on ethernet connection and with WEP encryption but not with WPA.

Can you post the contents of the files :

1. /etc/default/wpasupplicant
2. /etc/network/interfaces
3. /etc/wpa_supplicant.conf (if this has your passphrase/psk value then blank out the values)

And also what is the output if you start knetworkmanager from konsole

as Reinhard Tartler told me here : https://launchpad.net/distros/ubuntu/+source/wpasupplicant/+bug/36869 there is no more /etc/Default/wpasupplicant config files in the new version of wpa_supplicant. Other files follow..

my /etc/network/interfaces files.

My wpa_supplicant.conf files. He was not located in /etc/ but in /etc/wpa_supplicant/

Konsole output for Knetworkmanager and NetworkManager --no-daemon

Hi

It looks like the problem is with wpa_supplicant. This line containing "WPA: Unsupported TKIP Group Cipher key length 13 (13)" has been logged in the wpa_supplicant bugzilla although it was with a different driver. The url is

http://hostap.epitest.fi/bugz/show_bug.cgi?id=85

and is still outstanding,

so it's a wpa_supplicant bug. What have I to do to help?

Hi,

I'm not involved in wpa_supplicant project but I would suggest looking at their bugzilla reports and see if there is any match between your problem and ones that have been reported. This url is list problems similar to yours

http://hostap.epitest.fi/bugz/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=wpa_supplicant&component=wpa_supplicant+daemon&version=unspecified&long_desc_type=anywordssubstr&long_desc=Unsupported+TKIP+Group+Cipher+key+length+&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=

including closed/fixed ones. So hopefully there maybe some useful help already. If not use their bugzilla and report the bug at http://hostap.epitest.fi/bugz/ and pass on the log from networkmanager --no-daemon.

Hope they can help you further.

when i try wpa_supplicant manually by modify /etc/network/interfaces and using ifup this is what i got. so i think the bug should be move in wpa_supplicant.

my interface file (i've modify the wpa_key)

This bothers me still, as ipw2200 works great for me with WPA2 with AES.
Can you try loading ipw2200 kernel module with hwcrypto=0 (this was problem with older drivers)?

as someone told me there : http://hostap.epitest.fi/bugz/show_bug.cgi?id=131 this bug seems to be on by livebox and not concern wpa_supplicant. I'm currently looking for more informations.

this bug concern my router it shakes wap and wep encryption and linux can't manage this.

This is a bug in the AP, not in wpa_supplicant. The AP claims to use TKIP for group key, but then sends a key with length of 13 in the group key handshake even though TKIP keys are 32 octet long. See http://hostap.epitest.fi/bugz/show_bug.cgi?id=147 for details. Based on one comment, the AP can be made to behave by disabling "WPA or WEP" mode (use "WPA only").

rejecting this task as well based on information provided by Jouni. Thank you very much