Bug 8758

Summary:	Failure to connect to wireless network, wpa_supplicant started twice
Product:	Mageia	Reporter:	Reinout van Schouwen <reinout>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	wpa_supplicant	CVE:
Status comment:
Attachments:	Output of lspcidrake -v wpa_supplicant log output

Description Reinout van Schouwen 2013-01-20 15:20:21 CET

Description of problem:
Mageia 3 beta either fails to connect to the wireless network, or when it connects it quickly disconnects.
Mageia 2 has no problems at all in the same configuration.

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

1.1-2.mga3

How reproducible:
Always

Steps to Reproduce:
1. Log into Gnome
2. Select wireless network from Network Manager
3. Enter WPA shared key in the dialog.

Expected results: connection to wireless network
Actual results: network status icon changes to 'connected' but the connection is quickly broken again. After some time, the network icon reverts to 'unconnected'. In the mean time, no network traffic is possible.

Comment 1 Reinout van Schouwen 2013-01-20 15:20:43 CET

Created attachment 3418 [details]
Output of lspcidrake -v

Comment 2 Reinout van Schouwen 2013-01-20 15:21:58 CET

Created attachment 3419 [details]
wpa_supplicant log output

Comment 3 Sander Lepik 2013-01-20 16:43:53 CET

I think it might be the same bug as #8450 - i saw the same reason=3 disconnecting in my own logs.

CC: (none) => sander.lepik

Comment 4 Sander Lepik 2013-01-20 16:48:24 CET

https://wiki.archlinux.org/index.php/Wicd#Random_disconnecting - do you have power saving turned on? If yes then would it help if you disable it?

Comment 5 Reinout van Schouwen 2013-01-20 20:26:18 CET

I've followed the instructions to turn power saving off, with no effect at all unfortunately.

Comment 6 Reinout van Schouwen 2013-01-28 21:19:10 CET

Update: doing a modprobe -r ath9k followed by modprobe ath9k actually makes the problem go away, although the log messages about being disconnected and connected again keep appearing steadily in wpa_supplicant.log. However, the wireless connection doesn't seem to suffer much from it. 

Still, the wireless network should work from the start of course.

Comment 7 Reinout van Schouwen 2013-02-09 00:33:06 CET

I don't know what I did to make things work in comment #6, but it wasn't unloading and reloading the ath9k module. At best, I get a connection that lasts a few seconds and then dies.  (current cauldron)

Comment 8 Thomas Backlund 2013-02-09 03:13:35 CET

Does kernel-3.8.0-0.rc7.1.mga3 do any difference ?

CC: (none) => tmb

Comment 9 Reinout van Schouwen 2013-02-11 23:59:57 CET

(In reply to comment #8)
> Does kernel-3.8.0-0.rc7.1.mga3 do any difference ?

Unfortunately, I notice no change with this kernel update.

Comment 10 Reinout van Schouwen 2013-02-22 23:09:05 CET

After googling around a bit I found this page which put me on the right track: http://azitech.wordpress.com/2010/02/22/deauthenticating-reason3/

It turns out that there are two instances of wpa_supplicant being launched:
[reinout@x56v ~]$ ps aux|grep wpa
root      1119  0.1  0.0  45868  1592 ?        Ss   21:32   0:02 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
root      2569  0.0  0.0  45884  3540 ?        Ss   21:34   0:00 /usr/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant.conf -P /run/wpa_supplicant.pid

After killing them and re-selecting my network from NetworkManager, a new wpa_supplicant instance is started and the connection is as stable as ever!

Seems like a serious issue to me, but I have to wonder what's so special about my setup that I am the first to report this!

Summary: [ath9k] Failure to connect to wireless network => Failure to connect to wireless network, wpa_supplicant started twice

Comment 11 Reinout van Schouwen 2015-01-04 21:24:18 CET

I think this was solved with the default MGA4 configuration that disables gnome-network-manager by default.

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