From: "Alina Friedrichsen" <x-alina@gmx.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Call commit() on channel setting
Date: Fri, 27 Feb 2009 18:16:18 +0100 [thread overview]
Message-ID: <20090227171618.254890@gmx.net> (raw)
In-Reply-To: <200902271714.54181.mb@bu3sch.de>
Hello Michael!
> I think this is desired behavior.
Yes.
> We voluntarily associated with the
> "test" AP on channel 4.
Yes this is correct because IEEE80211_IBSS_AUTO_CHANNEL_SEL flag was se=
t.
> Who says that we want to assoc to the "test" ssid on channel 11?
Because this setting is now outdated. The channel is set to 11 and the =
IEEE80211_IBSS_AUTO_CHANNEL_SEL flag is clear.
If we now set the SSID to test again, we assoc to "test" on channel 11.=
Do not recover from the channel set automatically, is a broken behavio=
r, I think.
> This is a
> policy decision and such policy
> doesn't belong into the kernel. Userspace can initiate a reassociatio=
n
> after the channel change,
> if the AP switch is desired.
> There are good reasons to leave roaming decisions in userspace, becau=
se
> these decisions are simply very
> complex and would put lots of policy into the kernel or require lots =
of
> kernel API.
I think the basic functionality should work without any userspace daemo=
n. All the that can be implemented without real problems with a few lin=
es of code. This would better for embedded systems, if we don't need th=
e wpa_supplicant for an unencrypted network, or so.
Regards
Alina
--=20
Computer Bild Tarifsieger! GMX FreeDSL - Telefonanschluss + DSL
f=FCr nur 17,95 =BF/mtl.!* http://dsl.gmx.de/?ac=3DOM.AD.PD003K11308T45=
69a
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-27 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 23:43 [PATCH v2] mac80211: Call commit() on channel setting Alina Friedrichsen
2009-02-27 14:03 ` Michael Buesch
2009-02-27 15:35 ` Alina Friedrichsen
2009-02-27 15:39 ` Alina Friedrichsen
[not found] ` <20090227153418.254900@gmx.net>
2009-02-27 16:14 ` Michael Buesch
2009-02-27 17:16 ` Alina Friedrichsen [this message]
2009-02-27 18:25 ` [PATCH v3] " Alina Friedrichsen
2009-02-27 16:20 ` [PATCH v2] " Johannes Berg
2009-02-27 21:26 ` Alina Friedrichsen
2009-02-27 21:35 ` Johannes Berg
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=20090227171618.254890@gmx.net \
--to=x-alina@gmx.net \
--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).