All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFCv4 3/3] mac80211: add VHT support for IBSS
Date: Tue, 27 Jan 2015 11:24:31 +0100	[thread overview]
Message-ID: <1422354271.1890.62.camel@sipsolutions.net> (raw)
In-Reply-To: <1422348243-4928-3-git-send-email-janusz.dziedzic@tieto.com> (sfid-20150127_094518_689625_288E01DC)

On Tue, 2015-01-27 at 09:44 +0100, Janusz Dziedzic wrote:

> +u8 *ieee80211_ie_build_vht_oper(u8 *pos, struct ieee80211_sta_vht_cap *vht_cap,
> +				const struct cfg80211_chan_def *chandef)

> +	/* 1 stream, MCS0-7 as a min Basic VHT MCS rates */
> +	vht_oper->basic_mcs_set = cpu_to_le16(0xfffc);

Unless I'm mistaken in my reading of the spec, this will make any
well-behaved client (i.e. not mac80211) not join this network since it
supports VHT MCSes.

We seem to do the same for HT:

        /* It seems that Basic MCS set and Supported MCS set
           are identical for the first 10 bytes */
        memset(&ht_oper->basic_set, 0, 16);
        memcpy(&ht_oper->basic_set, &ht_cap->mcs, 10);

but I'm not convinced it's right. It probably only works because nobody
ever tested against a well-behaved non-HT client? Or perhaps there isn't
even one?

I for one am not really comfortable with this restriction - there's very
little point in making such a restriction in IBSS since if you have it
then the other node will just form its own network on the same channel
and you've won nothing - only lost interoperability.

johannes


  reply	other threads:[~2015-01-27 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  8:44 [RFCv4 1/3] cfg80211: add VHT support for IBSS Janusz Dziedzic
2015-01-27  8:44 ` [RFCv4 2/3] mac80211: IBSS fix scan request Janusz Dziedzic
2015-01-27  8:44 ` [RFCv4 3/3] mac80211: add VHT support for IBSS Janusz Dziedzic
2015-01-27 10:24   ` Johannes Berg [this message]
2015-01-27 11:39     ` Janusz Dziedzic
2015-01-27 11:43       ` 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=1422354271.1890.62.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=janusz.dziedzic@tieto.com \
    --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 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.