Bug 163711 - awkward parameter group in wpa_supplicant configuration when using ap_scan=2
Summary: awkward parameter group in wpa_supplicant configuration when using ap_scan=2
Status: RESOLVED DUPLICATE of bug 152291
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 9
Hardware: 32bit Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-05 09:36 UTC by Gilles Sabourin
Modified: 2006-04-07 11:08 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
ifup-wireless patch (757 bytes, patch)
2006-04-06 19:55 UTC, Gilles Sabourin 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gilles Sabourin 2006-04-05 09:36:49 UTC 
This bug report has a relationship with bug #152291 which I reopened for suse 10.0.

I am currently working with a linksys WRT54GS device with no ssid broadcast, wpa-psk ciphering with either TKIP or AES algorithm.

I can't associate with my acces point : ifup-wireless script does not work either with TKIP or AES (CCMP) ciphering because the parameter " group " which has been added in wpa_supplicant configuration is awkward.

Although you may think that group parameter in mandatory when reading the ap_scan description, a bug in wpa-supplicant prevents it to operate correctly when present.

Please, could you add only WIRELESS_CYPHER_GROUP if this variable is already
defined in /etc/sysconfig/network/wireless, instead of using it in a mandatory
way ?

Also, don't forget to add a template for wireless parameters file, I mean
wireless.template file in /etc/sysconfig/network/ for example.
Comment 1 Michael Gross 2006-04-05 12:52:22 UTC 
> This bug report has a relationship with bug #152291 which I reopened for suse
> 10.0.

Is this the exact same problem? If it was not fixed for 10.0, we should handle this in the original report and increase the version there.
Comment 2 Gilles Sabourin 2006-04-05 17:45:23 UTC 
Michael, you should have a look at bug report #152291
I do not see clearly what do SUSE team intend to do about this subject.
Comment 3 Gilles Sabourin 2006-04-06 19:55:35 UTC 
Created attachment 77013 [details]
ifup-wireless patch
Comment 4 Gilles Sabourin 2006-04-06 19:57:33 UTC 
Michael,

I have tested the patch above and it works, incase of
- SSID broadcast diasbled,
- WPA ciphering
- ndiswrapper driver use.

best regards,
Gilles
Comment 5 Gilles Sabourin 2006-04-06 19:58:48 UTC 
Michael,

I have tested the patch above and it works, in case of
- SSID broadcast disabled,
- WPA ciphering
- ndiswrapper driver use.

best regards,
Gilles
Comment 6 Michael Gross 2006-04-07 11:08:20 UTC 
OK then, but the same patch is attached to bug #152291 - so no reason to open to concurrent reports. You might write a mail to the assignee or add a report there, the involved people will receive a mail. I cannot make that decision. I'm increasing the version there.

*** This bug has been marked as a duplicate of 152291 ***