11n in adhoc mode

[PseudoCylon]

> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 11 Dec 2012 01:19:51 -0800
> From: Adrian Chadd <adrian at freebsd.org>
> To: Johann Hugo <jhugo at meraka.csir.co.za>
> Cc: freebsd-wireless at freebsd.org
> Subject: Re: 11n in adhoc mode
> Message-ID:
>         <CAJ-Vmon-Ppk_i074X+r1DQCei4BgTh4VZ=obVJsgKTtHNigQpA at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> .. so now I have 11n IBSS working, but the performance is pretty
> shocking. I bet there's some timers that are just not programmed
> correctly.
> I see massive numbers of long retries and CRC errors.

Are protection modes set correctly on both ends? This happens when
each end uses different prot mode.

> * Then some ancillary stuff - mostly processing beacon frames from
> peers and handling HT IE changes correctly.

Because this is an adhoc mode issue, this may not apply. But, this is
what I have been seeing. Yet another ancillary stuff.

Currently, protection mode is updated though ieee80211_htprot_update()
(finally iv_update_beacon() is called), and it is called only in
hostap mode.

When occupancy changes, an ap updates beacon and tells driver to
updated the prot mode.

Even though, other ends receives updated beacon, ieee80211 stack
doesn't tell driver to update the mode (other than in ap mode). As the
result, those nics run on different prot modes.

When operating with mismatched mode, retry and crc error counts skyrocket.

I think we need to add ic_update_prot().


AK