Date: Sun, 21 Feb 2010 11:35:41 +0100 From: Alexander Egorenkov <egorenar@googlemail.com> To: Sam Leffler <sam@errno.com> Cc: freebsd-net@freebsd.org Subject: Re: HT rate set in net80211 not changeable for STA Message-ID: <2d3b7e441002210235q5c6de2bvaedfa460fcb0766e@mail.gmail.com> In-Reply-To: <4B6F2A44.3010205@errno.com> References: <2d3b7e441002060028i5b1fc665p92b10fa21d77284d@mail.gmail.com> <8F5F80D8-A262-49F4-B580-781A44D3190D@freebsd.org> <2d3b7e441002060658h49712201m464dac80208db369@mail.gmail.com> <4B6DE491.8010901@errno.com> <2d3b7e441002070041waa8f968le66328ebeb7b163d@mail.gmail.com> <4B6F2A44.3010205@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This MCS32 HT rate causes problems with AMRR. If the connection between a client and an AP is very good and the AP supports MCS32, the client keeps increasing the Tx rate upto MCS32 and then the problems begin because the client starts to send with MCS32. Alex. On Sun, Feb 7, 2010 at 10:01 PM, Sam Leffler <sam@errno.com> wrote: > Alexander Egorenkov wrote: > > >> >> On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler <sam@errno.com <mailto: >> sam@errno.com>> wrote: >> >> The advertised rate set should be initially set according to the >> capabilities of the device. There were no devices > 2x2 when I >> wrote the code so MCS15 is the max. To support such devices you >> need to do more than just grow the rateset. >> >> >> But my device is a 2T2R device and supports MCS32 (HT duplicate mode). >> >> > MCS32 is special; as you indicate it forces duplicate signal on the upper > and lower channels in HT40. There is no support for MCS32 in net80211. > > Sam > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2d3b7e441002210235q5c6de2bvaedfa460fcb0766e>