From: Bruno Randolf <br1@einfach.org>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Add HT IE to IBSS beacons and probe responses.
Date: Thu, 13 May 2010 09:47:07 +0900 [thread overview]
Message-ID: <201005130947.07577.br1@einfach.org> (raw)
In-Reply-To: <4BEB175F.7000001@free.fr>
On Thursday 13 May 2010 06:02:23 Benoit Papillault wrote:
> > Also I just noticed that there's a TODO item in rx.c when we receive an
> > HT frame from a peer we don't know about yet. Not sure what to do there,
> > but you'll need to look at it.
>
> I did some patch in this area in my tree. Basically, the peer STA is
> created only on beacon/probe response since only those frames contains
> peer capabilities. Any frames received before is simply ignored.
i think the same applies to non-HT. when we receive a frame from a STA we
haven't seen a beacon from yet, we just mark the rate at which we received the
frame and can use that for a reply. later, when we receive a beacon, the rate-
set is updated. i guess the same can be done for HT and i'd argue that it
should be done like this in order to be able to communicate even though we
have not received a beacon from that particular STA yet - there are some
reasons why the beacon might not have reached us:
* the STA might have deferred beacon sending for a few intervals as part of
the normal beacon backoff
* the beacon might have been lost due to interference
* or the other STA might be a buggy implementation which doesn't send IBSS
beacons for a while, like some madwifi versions.
in any case the ability to communicate is more important than a complete rate-
set...
bruno
next prev parent reply other threads:[~2010-05-13 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 22:36 [PATCH v2] cfg80211: Parse channel_type in NL80211_CMD_JOIN_IBSS Benoit Papillault
2010-05-05 22:36 ` [PATCH v2] mac80211: Add HT IE to IBSS beacons and probe responses Benoit Papillault
2010-05-06 6:40 ` Johannes Berg
2010-05-07 23:01 ` Benoit Papillault
2010-05-11 10:48 ` Johannes Berg
2010-05-12 21:02 ` Benoit Papillault
2010-05-13 0:47 ` Bruno Randolf [this message]
2010-05-13 7:09 ` Benoit Papillault
2010-05-14 13:58 ` 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=201005130947.07577.br1@einfach.org \
--to=br1@einfach.org \
--cc=benoit.papillault@free.fr \
--cc=johannes@sipsolutions.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).