Linux wireless drivers development
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Subject: Re: BUG: ifdown doesn't notify cfg80211
Date: Wed, 29 Jul 2009 14:59:55 +0200	[thread overview]
Message-ID: <200907291459.55484.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <200907291325.51598.hs4233@mail.mn-solutions.de>

> # iw dev eth1 connect -w MNHS key 0:11111
> eth1 (phy #0): connected to 00:13:19:80:da:30
> # ifconfig eth1 down
> # ifconfig eth1 up
> # iw dev eth1 connect -w MNHS key 0:11111
> command failed: Operation already in progress (-114)

As Johannes pointed out on IRC, this happens only if you used

iwconfig eth1 key s:11111
iwconfig eth1 essid MNHS

previously on the device. Seems that the CFG80211-configuration 
doesn't delete the WEXT-configuration remnants. And as soon as 
you "ifup" the device, it starts associating based on old WEXT 
data, resulting in the busy.

-- 
http://www.holgerschurig.de

      reply	other threads:[~2009-07-29 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 11:10 BUG: ifdown doesn't notify cfg80211 Holger Schurig
2009-07-29 11:25 ` Holger Schurig
2009-07-29 12:59   ` Holger Schurig [this message]

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=200907291459.55484.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --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