linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: don't downgrade VHT20 to HT20
Date: Wed, 19 Mar 2014 15:22:14 +0100	[thread overview]
Message-ID: <1395238934.4142.22.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQnvSxOCxV4UwUmi2_if8NQWWJCht=urAewBZAiEJdHpZA@mail.gmail.com> (sfid-20140225_141121_872159_6A96AC3B)

Sorry for the delay. Somehow I thought this was addressed, but I'm
confused.

I think we all agree that the spec says:

> > A VHT STA shall set the Supported Channel Width Set subfield in its HT
> > Capabilities element HT Capabilities Info field to 1, indicating that
> > both 20 MHz operation and 40 MHz operation are supported.

and that the station should therefore set the 20_40 capability bit in
the association response?

> The spec also defines VHT BSS operating channel width is derived from
> HT Operation Element: STA Channel Width field (Table 10-19) and 20 MHz
> is not forbidden for AP/mesh. hostapd seems to go in line with this
> and allows VHT20 and VHT40.

Yes but how is that related to the *capability* bit? You're talking
about the HT/VHT operation information.

> Without my patch (i.e. with the 20/40 check left intact):
> 
> * If a station connects to VHT20 BSS, hostapd tries to add a VHT20
> station, but mac80211 downgrades it to HT20,
> * If mac80211 station connects to a VHT20 BSS it gets downgraded to HT20 too.
> 
> This means mac80211 is unable to setup VHT20 pairing properly even
> though VHT20 BSS is defined in the spec.
> 
> My take is 10.39.1 means VHT STA AssocReq must contain
> IEEE80211_HT_CAP_SUP_WIDTH_20_40.
> I suppose AP (hostapd) should deny STA association in that case.

So are you saying the station isn't setting 20_40 capability? Or is
something else unsetting the bit in case it's a 20MHz network?

johannes


  reply	other threads:[~2014-03-19 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 11:27 [PATCH] mac80211: don't downgrade VHT20 to HT20 Michal Kazior
2014-02-25 12:07 ` Johannes Berg
2014-02-25 12:10   ` Johannes Berg
2014-02-25 13:11     ` Michal Kazior
2014-03-19 14:22       ` Johannes Berg [this message]
2014-03-20  9:39         ` Michal Kazior
2014-03-21 12:03           ` Johannes Berg
2014-05-09  8:39 ` 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=1395238934.4142.22.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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).