From: chris <chgans@googlemail.com>
To: linux-wireless@vger.kernel.org
Subject: WiFi roaming question
Date: Mon, 19 Aug 2013 16:04:59 +1200 [thread overview]
Message-ID: <5211996B.4060800@gmail.com> (raw)
Hi All,
I have setup a WiFi infrastructure with several APs connected by
ethernet, with only one AP acting as the gateway/dhcp server.
It is a "mixed band" infrastructure (2.4/5GHz).
My goal was to see how, as a WiFi client, I would have to manage which
access point to connect to.
My environment is a custom embedded Linux system with connman and
wpa_supplicant.
It turned out that, as a client, I don't have to bother with roaming
stuff, it simply works out of the box.
Though, I have a couple of questions regarding this OOBX (new buzz word
seen here and there for "out of the box experience" :) ).
- At which level the roaming is done? Is it at the WiFi kernel stack
(cfg/mac 80211), at driver level, or at chipset/firmware level or a mix
of them?
- Can I change my setup, so that I have control over the roaming?
- Is it a good idea to try to manage that myself from userspace?
My usecase is a set of industrial devices that needs to connect to a
WiFi network (either a unique AP or a set of APs).
On top of that I have to manage a special case where, for whatever
reason, the user would have forgotten to switch off somes APs, these APs
shouldn't be on might then interferes with the running system.
I know my questions are a bit broad, but I would appreciate if some one
could give me some hints or even better point me to some Linux centric
papers/articles.
Regards,
Chris
PS: I've found some documentation about IAPP, 802.11i, 802.11F, L2 vs L3
roaming (FWIU wifi vs IP), ... But nothing really clear to me and none
of them speaks about Linux compatibility/implementation.
next reply other threads:[~2013-08-19 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 4:04 chris [this message]
2013-08-19 8:26 ` WiFi roaming question Krishna Chaitanya
2013-08-20 4:40 ` Christian Gagneraud
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=5211996B.4060800@gmail.com \
--to=chgans@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.