Date: Tue, 23 Feb 2010 13:12:42 +0100 From: Alexander Egorenkov <egorenar@googlemail.com> To: Rui Paulo <rpaulo@freebsd.org> Cc: freebsd-net@freebsd.org Subject: Re: HT rate set in net80211 not changeable for STA Message-ID: <2d3b7e441002230412n4df32e6dm872af957b368f816@mail.gmail.com> In-Reply-To: <0FE9B65C-5612-411A-8EA8-24ABF57999BC@freebsd.org> 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> <2d3b7e441002210235q5c6de2bvaedfa460fcb0766e@mail.gmail.com> <0FE9B65C-5612-411A-8EA8-24ABF57999BC@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
The problem is not on the AP side, the client sends with MCS32 because it's the last MCS in ni_htrates array of AP and the connection is good. AMRR increases the Tx rate to AP till MCS32 and then the client sends with MCS32. I changed AMRR a bit so it would skip MCS32 and it works fine now. I had to change AMRR anyway, because ieee80211_amrr.c doesn't support HT nodes. On Tue, Feb 23, 2010 at 1:01 PM, Rui Paulo <rpaulo@freebsd.org> wrote: > On 21 Feb 2010, at 10:35, Alexander Egorenkov wrote: > > > 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. > > Can you change the bitrate mask in the HTINFO information element? If you > say that you don't support MCS32, the AP shouldn't use it. > > -- > Rui Paulo > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2d3b7e441002230412n4df32e6dm872af957b368f816>