All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Pavel Roskin <proski@gnu.org>
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:22:28 -0500	[thread overview]
Message-ID: <6480.1268432548@localhost> (raw)
In-Reply-To: Your message of "Fri, 12 Mar 2010 17:19:41 EST." <1268432381.3596.12.camel@mj>

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

On Fri, 12 Mar 2010 17:19:41 EST, Pavel Roskin said:
> 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.

No NetworkManager here, so that shoots that theory. There's just a
wpa_supplicant running and nothing else managing the interface.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2010-03-12 22:22 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
2010-03-12 22:22       ` Valdis.Kletnieks [this message]
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=6480.1268432548@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.