Bug 11243 - WiFi wpa/wpa2 with shared key can't connected
Summary: WiFi wpa/wpa2 with shared key can't connected
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-17 07:37 CEST by Bernard SIAUD
Modified: 2013-10-02 11:19 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bernard SIAUD 2013-09-17 07:37:28 CEST 
Description of problem:
When I see with mcc the Wifi, I find my WiFi. But, I can't connected.

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


How reproducible:


Steps to Reproduce:
1. Go to mcc => network => "Centre réseau" (the first in the left Top)
2. Chose WiFi
3. Chose My Wifi (connected) and I have this in the console too many time :


got wireless event: <3>CTRL-EVENT-DISCONNECTED bssid=XXX reason=0 eth1
got wireless event: <3>Trying to associate with XXX (SSID='DartyBox_XXXX' freq=2437 MHz) eth1
got wireless event: <3>Association request to the driver failed eth1
got wireless event: <3>Associated with 00:00:00:00:00:00 eth1
got wireless event: <3>CTRL-EVENT-DISCONNECTED bssid=XXX reason=0 eth1
got wireless event: <3>Trying to associate with XXXb (SSID='DartyBox_XXXX' freq=2437 MHz) eth1
got wireless event: <3>Association request to the driver failed eth1
got wireless event: <3>Associated with 00:00:00:00:00:00 eth1
got wireless event: <3>CTRL-EVENT-DISCONNECTED bssid=XXX reason=0 eth1



Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-09-18 11:58:12 CEST 
does it work with networkmanager ?
Comment 2 Bernard SIAUD 2013-09-18 18:09:56 CEST 
I havn't networkmanager.
Now, I have try with networkmanager, it's the same :

got wireless event: <3>Trying to associate with XXX (SSID='DartyBox_XXXX' freq=2437 MHz) eth1
got wireless event: <3>Association request to the driver failed eth1
got wireless event: <3>Associated with XXX eth1
got wireless event: <3>CTRL-EVENT-DISCONNECTED bssid=XXX reason=0 eth1
got wireless event: <3>Trying to associate with XXX (SSID='DartyBox_XXXX' freq=2437 MHz) eth1
got wireless event: <3>Association request to the driver failed eth1
got wireless event: <3>Associated with XXX eth1
got wireless event: <3>CTRL-EVENT-DISCONNECTED bssid=XXX reason=0 eth1
Comment 3 Dave Hodgins 2013-09-19 01:01:42 CEST 
The use of eth1 in a cauldron install would leave me to think it's bug 11101
that may be causing the problem.

Workaround is to use mcc to remove all network interfaces, reboot, then add
in the correct one.

CC: (none) => davidwhodgins

Comment 4 Bernard SIAUD 2013-09-20 19:41:08 CEST 
Yes after a reboot I have the WiFi ! But I have not all understandard.
I will speak about this in french : http://www.mageialinux-online.org/forum/topic.php?id=16369&pt=&idm=&quote=#m158655
Comment 5 Manuel Hiebel 2013-10-02 11:19:12 CEST 
closing then (please do it yourself next time thanks)

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.