Search Linux Wireless

Re: ath10k stuck in mesh mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 20 November 2016 at 02:07, Bob Copeland <me@xxxxxxxxxxxxxxx> wrote:
> On Fri, Nov 18, 2016 at 10:43:06PM +0100, Matteo Grandi wrote:
>> So the question is: who decide if use MIMO and higher MCS hopefully on
>> 80MHz channel or not? Is the firmware? Is there a way to force the
>> interface to use 80MHz and/or MIMO? (iw provide the possibility to
>> choose between [HT20/HT40-/HT40+]).
>
> You can specify the channel width like so:
>
> iw dev wlan0 set freq 5745 80 5775
> iw dev wlan0 mesh join mesh-vht

With recent enough `iw` you can check the operational (max) bandwidth
of the interface with:

  iw dev wlan0 info

I don't know how mesh nodes negotiate their capabilities to each other
though so I don't know how reliable this is.

Actual modulation is picked by rate control in firmware. You can try
to force a fixed rate with[1]:

 iw dev wlan0 set bitrates legacy-5 ht-mcs-5 vht-mcs-5 1:9

It doesn't allow setting fixed bandwidth though so you'll need to
check rx bitrate on the receiving end to verify.

[1]: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug?s[]=set&s[]=bitrates#manual_bitrates_configuration


Michał




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux