linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Alexander Simon <alexander.simon@saxnet.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/4] mac80211: Add HT operation modes for IBSS
Date: Sat, 13 Aug 2011 10:05:45 -0600	[thread overview]
Message-ID: <4E46A0D9.3090906@openwrt.org> (raw)
In-Reply-To: <2276990.7uHyxQX4MO@alex-1>

On 2011-08-12 8:25 AM, Alexander Simon wrote:
>>  Ok, that makes sense. So you need the get_bss_ht() only for fixed mode I
>>  guess.
> Exactly.
>>
>>  >  This should answer your last questions:
>>  >  When not fixed, the BSSID configuration always is preferred. Thus, we
>>  >  would join as HT40 even though not requested.
>>  >  So, when we requsted HT40-, but the IBSS is HT40+, we would work on -.
>>
>>  ? I think I know what you mean but your example seems .. the wrong way
>>  around?
> Damn, you're right. We would work on HT+, not -, as the BSS config is
> preferred.
>>
>>  >  I wanted to have the opportunity to start HT on an existing IBSS.
>>
>>  Well that should always be OK?
>>
>>  >  The problem is that legacy station may "kill" the HT configuration:
>>  >  If STA A starts in HT IBSS and lets say Windows STA B joins, B would
>>  >  advertise that IBSS as non-HT as it ignores our HT IE.
>>  >  Then, if STA A dies and STA C joins, it will be non-HT.
>>
>>  mac80211 is STA C? Would it be a problem to use HT if the IBSS was
>>  previously non-HT? The old members will ignore it, but other new HT
>>  members may work OK? IOW -- is it not possible to have a mixed HT/non-HT
>>  IBSS?
> Basically, as to my knowledge, the only difference is that we add HI IEs. Non-
> HT stations will ignore these, of course.
> A mixed network should be no problem - as long as Greenfield is turned off
> (and i don't turn in on anywhere).
>
> To proceed with basics: I follow a very simple approach (for non-fixed freq):
> Use current BSS HT settings. If none exists, use iw config. If no iw config,
> no HT.
What's the point of disabling HT in that case. Since it's a superset of 
normal A/B/G mode, we could just leave it enabled (defaulting to HT20) 
instead of reconfiguring based on beacons at a later point in time.

- Felix

  reply	other threads:[~2011-08-13 16:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 12:02 [PATCH 1/4] nl80211: Parse channel type attribute in an IBSS join request Alexander Simon
2011-08-08 12:04 ` [PATCH 2/4] cfg80211: Add cfg80211_get_bss_ht to also match HT configuration Alexander Simon
2011-08-10 13:53   ` Johannes Berg
2011-08-10 15:48     ` Alexander Simon
2011-08-10 16:05       ` Johannes Berg
2011-08-10 17:50         ` Alexander Simon
2011-08-12 12:32           ` Johannes Berg
2011-08-12 14:20             ` Alexander Simon
2011-08-08 12:09 ` [PATCH 3/4] mac80211: Add HT helper functions Alexander Simon
2011-08-10 13:54   ` Johannes Berg
2011-08-10 13:55   ` Johannes Berg
2011-08-08 12:10 ` [PATCH 4/4] mac80211: Add HT operation modes for IBSS Alexander Simon
2011-08-10 14:03   ` Johannes Berg
2011-08-10 15:31     ` Alexander Simon
2011-08-12 12:35       ` Johannes Berg
2011-08-12 14:25         ` Alexander Simon
2011-08-13 16:05           ` Felix Fietkau [this message]
2011-08-10 13:50 ` [PATCH 1/4] nl80211: Parse channel type attribute in an IBSS join request Johannes Berg
2011-08-23 19:39 ` John W. Linville

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=4E46A0D9.3090906@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=alexander.simon@saxnet.de \
    --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).