From: Andy Green <andy@warmcat.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: chaning mode only when interface down?
Date: Thu, 02 Aug 2007 10:18:03 +0100 [thread overview]
Message-ID: <46B1A14B.2070808@warmcat.com> (raw)
In-Reply-To: <1186046044.24230.11.camel@johannes.berg>
Somebody in the thread at some point said:
>> Because of this NM can't create ad-hoc networks because it does it while
>> the device is up.
>> Any ideas?
>
> Fix NM?
It can easily try it one way and if it fails, try the other.
NM has some other things that needed fixing last time I looked at it...
it thought it knew better than I did if a wireless interface was in
Monitor mode that I "really wanted it" to be in Managed.
-Andy
next prev parent reply other threads:[~2007-08-02 9:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 7:44 chaning mode only when interface down? dragoran
2007-08-02 9:14 ` Johannes Berg
2007-08-02 9:16 ` dragoran
2007-08-02 12:17 ` [ipw3945-devel] " Winkler, Tomas
2007-08-02 12:34 ` Johannes Berg
2007-08-02 12:41 ` Winkler, Tomas
2007-08-02 12:46 ` Johannes Berg
2007-08-02 13:11 ` Tomas Winkler
2007-08-02 12:48 ` dragoran
2007-08-02 12:53 ` Johannes Berg
[not found] ` <f6ca9fed0708020643p53ceedcav76b14814b1b1cabd@mail.gmail.com>
2007-08-02 15:52 ` Derek Atkins
2007-08-03 9:41 ` Johannes Berg
2007-08-03 14:33 ` Derek Atkins
2007-08-03 14:50 ` Johannes Berg
2007-08-03 14:53 ` John W. Linville
2007-08-03 15:10 ` Derek Atkins
2007-08-02 18:51 ` Dan Williams
2007-08-03 9:42 ` Johannes Berg
2007-08-03 11:20 ` Dan Williams
2007-08-30 22:24 ` blocking in dev->open (was: [ipw3945-devel] chaning mode only when interface down?) Johannes Berg
2007-08-02 9:18 ` Andy Green [this message]
2007-08-02 9:59 ` chaning mode only when interface down? Johannes Berg
2007-08-02 18:47 ` Dan Williams
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=46B1A14B.2070808@warmcat.com \
--to=andy@warmcat.com \
--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).