Bug 141591

Summary:	WLAN configuration not written correctly to config files
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Michael Neumeier <dennismail>
Component:	YaST2	Assignee:	Joachim Gleissner <joachim.gleissner>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	unspecified
Target Milestone:	---
Hardware:	i586
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Yast 2 logs hwinfo --wlan

Description Michael Neumeier 2006-01-05 17:04:22 UTC

I tried to configure my Intel 2200 WLAN card in my FSC Amilo laptop. YaST accepts all data I entered, but doesn´t seem to write correctly my key (which is a 64bit WEP one).

After a reboot of the laptop, iwconfig either says that the key is 
3030-3030-3030-3030-3030-3030-3030-3030 or key is set to "off". I can then set the key again on the command line:

$ iwconfig eth1 key <mykey>

After some seconds, I can ping my router as well as URLs in the Internet. But after the reboot, I have to set the key again manually as above.

In this context, I just noticed that the rate of the WLAN card is not correctly recognized: The speed is set to 22MBit, but the card supports 54MBit. I can as well set this manually (iwconfig eth1 rate 54M), but it´s gone as well when I reboot.

Yours,
Michael Neumeier

Comment 1 Michael Gross 2006-01-09 16:08:31 UTC

Please attach `hwinfo --wlan' as well as your yast2 logfiles. Thanks.

Comment 2 Michael Neumeier 2006-01-13 17:42:32 UTC

Created attachment 63318 [details]
Yast 2 logs

Comment 3 Michael Neumeier 2006-01-13 17:43:42 UTC

Created attachment 63319 [details]
hwinfo --wlan

Comment 4 Michael Neumeier 2006-01-13 17:46:45 UTC

Here are the two attachments you asked for. Please note that I sent them from another PC, so I had to copy these two files from my laptop to the other machine. To do so, I deleted the config for the WLAN-Interface and made a confuguration for the ethernet card (both integrated in the laptop). This information may be useful, I think.

Comment 5 Michael Neumeier 2006-01-16 10:35:30 UTC

Oh, I just noticed the checkbox that changes the status back to "assigned". Sorry!

But I can also add some more info which may be useful. As I use my laptop in different areas, I tried to configure scpm (I included /etc/sysconfig/network/ifcfg-wlan-... in the Ressources list!) with two different WLAN-config. 
Both ifcfg-wlan-... files have the correct settings in it (essid, key etc). When I change the profile and check the contents of the file (cat ifcfg-wlan...), the correct settings show clearly the the change of the profile worked correctly (excpet that after the initialization, there are no changed ressources in the dialogue box of the profile manager).
But when I then type in "iwconfig eth1", the contents of the ifcfg-wlan... file don´t seem to be applied, as there are still shown the same settings as before the profile change.

So can this be a problem that this file is not correctly read?

Comment 6 Michael Gross 2006-01-16 15:11:51 UTC

Reassigning this to Martin...

Comment 7 Martin Vidner 2006-01-16 15:19:34 UTC

If the config files are correct but not applied after a profile switch, then it is a SCPM problem.

Comment 8 Michael Neumeier 2006-01-16 15:39:52 UTC

OK, this may be a scpm problem, but even if I switch off scpm, the problem exists: No connection with WLAN - only if I set the key again (as described above).

BTW: I don´t believe it´s a hardware issue, as with SuSE 9.3, all worked fine. So I think this is actually a 10.0 bug.

Comment 9 Joachim Gleissner 2006-01-19 11:40:17 UTC

Does it help to add a line with PREFER_WPA_SUPPLICANT='no' to your ifcfg-file?

Comment 10 Michael Neumeier 2006-01-19 15:44:25 UTC

Yes, this did help! Thank you!

But this should be included in a doc somewhere. I think. As I didn´t have problems with 9.3, I ask myself if this is version- or machine-specific.

Anyhow, for me, the problem is solved.

Comment 11 Joachim Gleissner 2006-01-19 15:52:33 UTC

In 9.3 wpa_supplicant wasn't used for non-WPA connection. In principle every connection should work with wpa_supplicant, but it seems there are several cases where this is not the case so I'm considering to change the default back. Anyway, thanks for testing!

Comment 12 Michael Neumeier 2006-01-20 13:31:58 UTC

No Problem!

btw: Now, the scpm works also correctly!

Greets,
Michael

Comment 13 Joachim Gleissner 2006-02-09 18:20:27 UTC

Made PREFER_WPA_SUPPLICANT='no' default in 10.1.