2011-04-28 12:14:12

by Alexander Simon

[permalink] [raw]
Subject: Re: [PATCH 4/4] mac80211: Add IEEE802.11n for IBSS

> Also what if the IBSS is created with HT40+ and then joins, can it join
> HT40-? Is the channel type "advisory" like the frequency? Can it join
> HT20 IBSS as well?
HT type can`t be advisory, as there may be stations without n.

Our card is set to HT40+/- if set by iw.
Some other station is added into our internal station list by its HT beacons.
E.g. if we have configured HT40- and there is someone with HT40+, minstrel_ht
should use HT20 only. But i admit it seems cleaner to AND both caps.



2011-04-28 12:56:20

by Johannes Berg

[permalink] [raw]
Subject: Re: [PATCH 4/4] mac80211: Add IEEE802.11n for IBSS

On Thu, 2011-04-28 at 12:13 +0000, Alexander Simon wrote:
> > Also what if the IBSS is created with HT40+ and then joins, can it join
> > HT40-? Is the channel type "advisory" like the frequency? Can it join
> > HT20 IBSS as well?
> HT type can`t be advisory, as there may be stations without n.

Yeah, but it's possible to still communicate with them.

> Our card is set to HT40+/- if set by iw.
> Some other station is added into our internal station list by its HT beacons.
> E.g. if we have configured HT40- and there is someone with HT40+, minstrel_ht
> should use HT20 only. But i admit it seems cleaner to AND both caps.

Well. You need to consider more than just this. I have a feeling you're
only considering fixed channel use cases. But if we configure HT40+, and
then find a peer on a channel that may only use HT40-, then what?

johannes