From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: use beacons for connection monitoring
Date: Thu, 30 Jul 2009 04:39:51 +0200 [thread overview]
Message-ID: <1248921591.28545.256.camel@violet> (raw)
In-Reply-To: <1248903902.8925.1.camel@johannes.local>
Hi Johannes,
> > The connection monitor currently relies on probe requests paired
> > with probe responses to ensure that a connection is alive. This is
> > fragile in some environments where probe responses can get lost.
> > When we receive beacons we can also consider the connection to be
> > alive, so cancel connection poll instance when we receive a beacon.
> >
> > The debug message "cancelling probereq poll due to a received beacon"
> > is removed as part of this change as this case is hit very often after
> > the above change and debug log receives significant number of these messages.
>
> Not doing that was actually intentional -- we want to know whether or
> not the connection is working both ways, not just whether we can receive
> frames. This can certainly be improved, but I'm not sure this is the
> best approach.
this patch might be a band-aid and needs improvement or a total
different solution, but it does help my disconnect problems. It makes my
connection fully stable again. So it is not a wrong approach in general,
because otherwise I have to be always close to me AP. And then using
WiFi is bloody pointless since I could just put an Ethernet cable into
the wall socket directly.
Regards
Marcel
next prev parent reply other threads:[~2009-07-30 2:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 21:32 [PATCH] mac80211: use beacons for connection monitoring Reinette Chatre
2009-07-29 21:39 ` Ben Greear
2009-07-30 10:30 ` Johannes Berg
2009-07-30 14:41 ` Ben Greear
2009-07-30 17:45 ` reinette chatre
2009-07-30 19:47 ` Johannes Berg
2009-07-29 21:45 ` Johannes Berg
2009-07-29 21:50 ` reinette chatre
2009-07-30 5:24 ` Maxim Levitsky
2009-07-29 22:10 ` Ben Greear
2009-07-30 10:28 ` Johannes Berg
2009-07-30 2:39 ` Marcel Holtmann [this message]
2009-07-30 9:36 ` Helmut Schaa
2009-07-30 9:54 ` Johannes Berg
2009-07-31 7:08 ` Maxim Levitsky
2009-07-31 7:43 ` Johannes Berg
2009-07-31 7:58 ` Johannes Berg
2009-07-31 8:04 ` Maxim Levitsky
2009-07-31 9:41 ` Marcel Holtmann
2009-07-31 13:19 ` Maxim Levitsky
2009-07-31 13:39 ` Johannes Berg
2009-07-31 13:56 ` Maxim Levitsky
2009-07-31 14:06 ` 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=1248921591.28545.256.camel@violet \
--to=marcel@holtmann.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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).