From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>,
Mircea Gherzan <mgherzan@gmail.com>
Subject: Re: Google Summer of Code 2009 -- Linux wireless roaming project
Date: Tue, 24 Mar 2009 12:05:05 +0100 [thread overview]
Message-ID: <200903241205.06417.helmut.schaa@gmail.com> (raw)
In-Reply-To: <200903241136.03991.hs4233@mail.mn-solutions.de>
Am Dienstag, 24. M=C3=A4rz 2009 schrieb Holger Schurig:
> > Hmm, quick example: AP1 - STA - AP2
> >
> > We cannot consider the signal strength as constant as it
> > varies over time even when neither the STA nor the AP are
> > moving. Assume a threshold value of t=3D40. Furthermore, the
> > signal strength of AP1 and AP2 might alter between 35-50 which
> > means we have an average signal strength of 42,5 > t.
> > Nevertheless that would result in ping-pongs between AP1 and
> > AP2 because the signal might drop below t on both APs, while
> > it would be better to stick to one AP as the signal is already
> > quite bad (but still good enough to do some communication).
>=20
> Yeah, but if the client is moving, you have to live with that,=20
> more or less.
>=20
> And if the client is not moving (and roaming is a loadable kernel=20
> module), then simply don't load it :-)
Ah, ok. I was more referring to an ordinary laptop user who sits at his
desk and once in a while starts moving (for example to a conference roo=
m).
While he sits at his desk the optimal solution shouldn't trigger a scan=
as
the chance that a better AP pops up is relatively low. Once he starts
moving scanning is desired.
> My ad-hoc approach that I already implemented (for non-mac80211)=20
> shows a quite number of scannings. But that is ok for my=20
> use-case (e.g. telnet connection via WLAN). "Connection lost" is=20
> way worse than one scanning/reassociation too much, especially=20
> if the scanning/association is done intelligently.
>=20
> So for now I wouldn't optimize here, but make non-sucking roaming=20
> possible in the first place. We can build upon this anyway.
=46ine with me. But too aggressive scanning might lead to unstable or
intermittent connections, especially when WPA-EAP without PMKSA-caching
is used where roaming from one AP to another can take up to several
seconds ;)
And additionally if the connection is idle, repeated scanning will
increase the power consumption which is not desired on battery driven
devices.
Helmut
--
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-03-24 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 21:57 Google Summer of Code 2009 -- Linux wireless roaming project Luis R. Rodriguez
2009-03-21 11:43 ` Helmut Schaa
2009-03-24 9:06 ` Holger Schurig
2009-03-24 10:15 ` Helmut Schaa
2009-03-24 10:36 ` Holger Schurig
2009-03-24 11:05 ` Helmut Schaa [this message]
2009-03-24 12:52 ` Mats Karlsson
2009-03-24 10:37 ` Dan Williams
2009-03-24 10:46 ` Holger Schurig
2009-03-24 10:49 ` 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=200903241205.06417.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=mgherzan@gmail.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 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.