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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
