From: Jouni Malinen <j@w1.fi>
To: Pavel Roskin <proski@gnu.org>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Michael Buesch <mb@bu3sch.de>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Dan E <trg_info@mailhaven.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Hostapd doesn't like crda
Date: Mon, 29 Dec 2008 21:21:16 +0200 [thread overview]
Message-ID: <20081229192116.GA20493@jm.kir.nu> (raw)
In-Reply-To: <1230575256.22537.3.camel@dv>
On Mon, Dec 29, 2008 at 01:27:36PM -0500, Pavel Roskin wrote:
> On Mon, 2008-12-29 at 08:18 -0800, Luis R. Rodriguez wrote:
> > > I think this wouldn't be hackish, but do we actually _know_ when crda has finished
> > > uploading regulatory information? Does it do it all in one step?
> >
> > It would go in through another nl80211 command, NL80211_CMD_SET_REG. nl80211 eventually
> > calls set_regdom() and this will set it, so if all goes well we can remove the timer
> > at the end if its active (other means can call CRDA like for 802.11d or the wireless core
> > upon initialization).
>
> Can we have a command to _get_ regulatory settings? I think it would be
> useful. Then hostapd could wait until the correct settings are active.
> If it doesn't happen after some time, hostapd should exit with an error.
>
> It would be even better if hostapd could wait for an event notifying of
> the regulatory settings change.
While I could make hostapd poll for the change (either with get or by
waiting in a local loop waiting for the event; both are about equally
horrible hacks), I would really prefer this to be done by blocking the
response message in the kernel rather than requiring all user space apps
(or scripts, for that matter) from having to do this. This is just
likely to result in silly "sleep 1" everywhere and hoping that it is
always long enough wait..
I might even be tempted to just push that out from hostapd and leave it
to be a somebody else's problem (that silly shell script with sleep 1)
if the needed mechanism would mean that restarting hostapd takes extra
time). A command for querying the current country would get rid of the
extra penalty on restarts, so I would probably prefer it if these two
options were the only available choices.
Either way, the main problems I see here is to figure out when exactly
the CRDA processing has been completed and to make sure that userspace
apps will somehow know when that happened (i.e., get country better not
return the new country code before all CRDA parameters have been
configured and available for the following set_freq command).
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2008-12-29 19:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 21:08 Hostapd doesn't like crda Michael Buesch
2008-12-27 22:08 ` Jouni Malinen
2008-12-28 13:26 ` Michael Buesch
2008-12-29 3:45 ` Dan E
2008-12-29 10:28 ` Michael Buesch
2008-12-29 15:56 ` Luis R. Rodriguez
2008-12-29 16:04 ` Michael Buesch
2008-12-29 16:18 ` Luis R. Rodriguez
2008-12-29 18:27 ` Pavel Roskin
2008-12-29 18:43 ` Luis R. Rodriguez
2008-12-29 19:21 ` Jouni Malinen [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=20081229192116.GA20493@jm.kir.nu \
--to=j@w1.fi \
--cc=Luis.Rodriguez@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mb@bu3sch.de \
--cc=proski@gnu.org \
--cc=trg_info@mailhaven.com \
/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).