From: Johannes Berg <johannes@sipsolutions.net>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Add HT IE to IBSS beacons and probe responses.
Date: Fri, 14 May 2010 15:58:34 +0200 [thread overview]
Message-ID: <1273845514.4950.23.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4BEB175F.7000001@free.fr>
On Wed, 2010-05-12 at 23:02 +0200, Benoit Papillault wrote:
> I thought again about 2 HT STA joining a non-HT IBSS. If we want those 2
> STA to be able to send/receive HT frames then they must know each other
> capabilities. So HT Capabilities should be sent if ht_supported = true,
> even if channel_type is CHAN_NO_HT
That has interesting protection requirements. How do we take care of
those?
> 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'll let you discuss that with Bruno. I think we may need to "upgrade"
to HT on receiving that, rather than leaving us without connectivity to
that peer.
johannes
prev parent reply other threads:[~2010-05-14 13:58 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
2010-05-13 7:09 ` Benoit Papillault
2010-05-14 13:58 ` Johannes Berg [this message]
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=1273845514.4950.23.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benoit.papillault@free.fr \
--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).