Description of problem: If I try to connect to my router with a WPA key I get the error message : "Des problèmes se sont produits pendant votre connexion réseau" = "Problems occurred during your network connection" If I try to connect to the same router with the same computer and same WPA key, but under Jolicloud distribution derived from Ubuntu, I have no problem. Everything works perfectly. The problem is a problem Mageia If I delete the WPA key and put "security none" on the router, everything works perfectly. If I write the configuration file "wireless-wpa.conf" ctrl_interface=/var/run/wpa_supplicant network={ ssid="myname" scan_ssid=1 key_mgmt=WPA-PSK psk="myKee" } and the script "wireless-wpa" #!/bin/bash ifconfig wlan0 down iwconfig wlan0 mode Managed ifconfig wlan0 up killall wpa_supplicant wpa_supplicant -B -Dwext -i wlan0 -c ./wireless-wpa.conf -dd dhclient wlan0 give him the rights : chmod etc and runs as root, everything works perfectly but the log shows various problems quote # ./wireless-wpa wpa_supplicant: aucun processus trouvé Initializing interface 'wlan0' conf './wireless-wpa.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A' Configuration file './wireless-wpa.conf' -> '/home/chr/./wireless-wpa.conf' Reading configuration file '/home/chr/./wireless-wpa.conf' ctrl_interface='/var/run/wpa_supplicant' Line: 3 - start of a new network block ssid - hexdump_ascii(len=5): 65 73 62 75 72 esbur scan_ssid=1 (0x1) key_mgmt: 0x2 PSK (ASCII passphrase) - hexdump_ascii(len=20): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] Priority group 0 id=0 ssid='esbur' WEXT: cfg80211-based driver detected SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf capabilities: key_mgmt 0xf enc 0xf flags 0x0 netlink: Operstate: linkmode=1, operstate=5 Own MAC address: 00:15:af:76:89:e0 wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 wpa_driver_wext_set_countermeasures RSN: flushing PMKID list in the driver Setting scan request: 0 sec 100000 usec EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: Supplicant port status: Unauthorized EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: Supplicant port status: Unauthorized EAPOL: Supplicant port status: Unauthorized Added interface wlan0 Daemonize.. /etc/sysconfig/network-scripts/network-functions: ligne419: /usr/sbin/nscd: Aucun fichier ou dossier de ce type The problem is probably in the module that provides connection drakconnect? who fails to pass the WPA key Version-Release number of selected component (if applicable): Kernel : 2.6.38.8-desktop586-10.mga Drakconf : 12.21.9-2.mga1 How reproducible: Every time with the GUI noproblem in rootin Konsole
ps aux|grep wpa check if there are 2 instances of wpa_supplicant
CC: (none) => n54
ps aux|grep wpa chr 2769 0.0 0.1 4296 772 pts/1 S+ 00:51 0:00 grep --color wpa root 4978 0.0 0.0 5008 204 ? Ss Apr14 0:00 wpa_supplicant -B -Dwext -i wlan0 -c ./wireless-wpa.conf -d I can found the directory /var/run/wpa-supplicant with [root@localhost wpa_supplicant]# ls -1 wlan0= and the file /usr/sbin/wpa_supplicant
Blocks: (none) => 5015
Bugs for mageia 1 should not be in a tracker for cauldron
Source RPM: Drakconf : 12.21.9-2.mga1 => drakx-net
Blocks: 5015 => (none)Assignee: bugsquad => mageia
(In reply to comment #4) > Bugs for mageia 1 should not be in a tracker for cauldron I overlooked this, Thanks!
I'm sorry : I'm newsbee in the godzilla. But in the form to introduce the bug, I have two choices to "version" : "1" or "Cauldron". I chose "1". That is why I do not understand why the bug is in a tracker for cauldron.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 1'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 1 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX