From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Jouni Malinen <j@w1.fi>, Samuel Ortiz <samuel@sortiz.org>,
Alina Friedrichsen <x-alina@gmx.net>
Subject: Re: configuring while interface is down
Date: Wed, 11 Mar 2009 09:49:59 -0400 [thread overview]
Message-ID: <1236779399.10989.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1236774973.20266.13.camel@johannes.local>
On Wed, 2009-03-11 at 13:36 +0100, Johannes Berg wrote:
> Hi,
>
> Alina raised an interesting point -- wext allows you to configure an
> interface while it is down, at least by convention. Some parameters for
> cfg80211 we reject while an interface is down, e.g. adding new stations,
> partly for technical reasons and partly because that doesn't make sense
> when the mode of interface isn't fixed.
>
> For cfg80211's assoc/ibss calls, I think we should reject them outright
> when the interface is down, any objections?
wext *allows* that, but drivers never consistently implemented that
(prism54 for example). With most soft-mac style adapters you can't scan
while the interface is down either. Anything meaningful use of the
interface happens when the firmware (if any) is loaded and the device is
operational. The only reason for setting parameters while the device
was down was to allow "commit-style" handling of the parameters; set
them all up while down, bring the interface up, and it uses all the
params you've set/locked on the interface. With cfg80211, that's
already handled in a much better manner, thus +1 from me.
Dan
prev parent reply other threads:[~2009-03-11 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 12:36 configuring while interface is down Johannes Berg
2009-03-11 13:43 ` Alina Friedrichsen
2009-03-11 13:48 ` Johannes Berg
2009-03-11 14:52 ` Samuel Ortiz
2009-03-14 6:24 ` Kalle Valo
2009-03-11 15:58 ` Alina Friedrichsen
2009-03-11 16:05 ` Johannes Berg
2009-03-11 13:46 ` John W. Linville
2009-03-11 13:49 ` Dan Williams [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=1236779399.10989.3.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=samuel@sortiz.org \
--cc=x-alina@gmx.net \
/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