Bug 10150

Summary:	MCC wireless should remember selected security protocol
Product:	Mageia	Reporter:	Tony Blackwell <tablackwell>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	derekjenn, mageia, mageia, thierry.vignaud
Version:	3
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakx-net	CVE:
Status comment:

Description Tony Blackwell 2013-05-19 01:45:09 CEST

Description of problem:MCC wireless configuration always opens with WEP selected as the security model, even when a particular connection has previously been configured to use WPA2.  MCC should read the previous configuration as it opens a re-edit of this.

A further point: I think we should change the default so MCC opens with WPA2 selected, not WEP.  Does anyone use WEP any more?


Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Thierry Vignaud 2013-05-19 16:02:31 CEST

CC: (none) => mageia, thierry.vignaud
Source RPM: (none) => drakx-net

Comment 1 Derek Jennings 2013-05-19 16:48:21 CEST

I do not see that behaviour here.

If I click on a network and select 'Configure' it comes up with the encryption mode set to whatever the Access Point is using.

Am I looking in the wrong place?

CC: (none) => derekjenn

Comment 2 Sander Lepik 2013-05-19 17:03:12 CEST

Usually MCC is detecting that configuration option from AP. Sometimes it fails to detect it and then it defaults to WEP. I hope that we are going to switch to NetworkManager in Mageia 4 and such problems will be history. AFAIK wpa_supplicant has something to do with that problem, but I haven't spent too much time figuring out what exactly is going on when this happens.

CC: (none) => sander.lepik

Comment 3 Tony Blackwell 2013-05-20 02:34:08 CEST

in 3 generations of Mageia I've never seen it stick with WPA2.  For me it always wants WEP.  Still, if we are going to switch as noted above, then perhaps we put this on hold pending that switch.

Comment 4 Tony Blackwell 2014-03-15 20:13:50 CET

Cleaning up old bugs.
This problem is no longer true as of Mageia 4 v2, so closing.

Status: NEW => RESOLVED
Resolution: (none) => FIXED