Bug 6602

Summary:	WiFi tries to connect to any WiFi network always with the last entered password
Product:	Mageia	Reporter:	Daniel Gadawski <daniel>
Component:	RPM Packages	Assignee:	Olivier Blin <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, stormi-mageia
Version:	2	Keywords:	Triaged
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	drakx-net	CVE:
Status comment:

Description Daniel Gadawski 2012-06-27 22:39:41 CEST

Description of problem:


I'm using Mageia 2. I recently found that passwords for WiFi networks I use are all the same according to Mageia drakconnect.
I'm using two-three networks. When I'm at home, I'm using first network with - for example - SSID: "network1". It's protected by a WEP key, which i enter before connecting to it. Everything works great.
Problem occurs when I move to my work. I would like to connect to another network with SSID: "network2", which is also WEP protected network. However, drakconnect try to use password for "network1" and I have to change it before connecting. After that, it tries to use password from "network2" when I'm back home and try to connect to the "network1".


How reproducible:


Steps to Reproduce:
1. Try to connect to the any protected wireless network with some password.
2. Disconnect to the network and try to connect to another network.
3. Mageia will try to use the last entered password to the second network.

Samuel Verschelde 2013-09-05 15:12:06 CEST

CC: (none) => stormi
Source RPM: (none) => drakx-net

Comment 1 Samuel Verschelde 2013-09-05 15:46:43 CEST

Confirmed by a user (marja) on IRC.

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 2 Marja Van Waes 2013-09-05 16:20:47 CEST

yes, I've see the same problem, and "solved" it by giving both networks the same WPA key.


I'll call the networks "X", "Y" and "Z" (in chronological order)

There are still problems, even if they are not the same as before:

Just now, trying with network "Z", it seemed that the password I had entered for "Z" was replaced with the one for "Y" and "X", so I overwrote it with the "Z" password. 

Then I saw that "X" had disappeared from drakroam, but that in return there are 2 "Z"s now.

Connecting to any of them is impossible, btw, but in the past a reboot was needed when trying to connect to a new network with WPA, I suppose it is the same now (can't test now)

This is in Mageia 2, with KDE, no networkmanager installed, and using the network applet and drakroam

CC: (none) => marja11

Comment 3 Marja Van Waes 2013-09-05 16:23:28 CEST

network Z being a new (with visible SSID) network, that had never been configured before

X and Y don't broadcast their SSIDs

Comment 4 Manuel Hiebel 2013-10-22 12:19:00 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 5 Manuel Hiebel 2013-11-23 16:15:39 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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