From: Ben Greear <greearb@candelatech.com>
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 07:41:18 -0700 [thread overview]
Message-ID: <4A71B10E.20808@candelatech.com> (raw)
In-Reply-To: <1248949853.29062.3.camel@johannes.local>
Johannes Berg wrote:
> On Wed, 2009-07-29 at 14:39 -0700, Ben Greear wrote:
>
>> On 07/29/2009 02:32 PM, Reinette Chatre wrote:
>>
>>> From: Reinette Chatre<reinette.chatre@intel.com>
>>>
>>> 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.
>>>
>> I'm chasing a similar problem while working on virtual STA device
>> support in ath5k. I was also going to try sending up to 3 polls before
>> giving up on the connection. Does that seems like a valid thing to do?
>>
>
> That seems somewhat better, yeah.
>
> I suspect the real cause of the issue is something else though, like the
> probe request not going out properly or the card being in a kind of
> 'temporary lock-up' state where it's not really doing anything for the
> time being -- I've never had a problem on any other (than iwlwifi)
> hardware.
>
> Of course, the virtual STA device support stuff potentially has similar
> issues, especially if it does channel switching like the ath9k virtual
> wiphy stuff.
>
We're not trying any channel switching, though it does seem to stop
transmitting
and/or receiving for a bit during some operations. The retransmit logic
was helping,
but it still isn't quite right. Hopefully we'll make more progress today.
Thanks,
Ben
> johannes
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-07-30 14:41 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 [this message]
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
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=4A71B10E.20808@candelatech.com \
--to=greearb@candelatech.com \
--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).