From: Pavel Roskin <proski@gnu.org>
To: Valdis.Kletnieks@vt.edu
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Weird wireless/wpa_supplicant screw-up.
Date: Fri, 12 Mar 2010 17:19:41 -0500 [thread overview]
Message-ID: <1268432381.3596.12.camel@mj> (raw)
In-Reply-To: <5220.1268430568@localhost>
On Fri, 2010-03-12 at 16:49 -0500, Valdis.Kletnieks@vt.edu wrote:
> So the root cause has something to do with params[idx].cipher being unset.
Sorry if it's obvious, but please make sure you don't have another
wpa_supplicant running and there is no other software that tries to
control the interface.
If you have NetworkManager, the device in question should be unmanaged.
This could be done by adding this
to /etc/NetworkManager/nm-system-settings.conf:
[main]
plugins=keyfile
[keyfile]
unmanaged-devices=/org/freedesktop/Hal/devices/net_00_1f_11_01_06_55
If the "plugins" line exists, "keyfile" should be added, separated by
comma from the previous word. The MAC address must be lowercase.
Entries on the unmanaged-devices line are separated by semicolons.
Use "cnetworkmanager -d" to make sure the device is unmanaged (install
cnetworkmanager if needed). You may need to restart NetworkManager or
even reboot after changing the configuration.
Perhaps we need it in the FAQ somewhere.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-12 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:22 Weird wireless/wpa_supplicant screw-up Valdis.Kletnieks
2010-03-12 11:14 ` Johannes Berg
2010-03-12 11:16 ` Johannes Berg
2010-03-12 21:49 ` Valdis.Kletnieks
2010-03-12 22:19 ` Pavel Roskin [this message]
2010-03-12 22:22 ` Valdis.Kletnieks
2010-03-13 3:09 ` Johannes Berg
2010-03-17 3:06 ` Valdis.Kletnieks
2010-03-17 3:22 ` Johannes Berg
2010-03-17 8:21 ` Valdis.Kletnieks
2010-03-17 9:03 ` Holger Schurig
2010-03-17 20:29 ` Valdis.Kletnieks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1268432381.3596.12.camel@mj \
--to=proski@gnu.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).