From: "Ralph Houthoofdt" <ralph@rora.be>
To: ath10k@lists.infradead.org
Subject: QCA9880 slow performance adhoc/IBSS mode
Date: Tue, 28 Feb 2017 17:51:14 +0100 [thread overview]
Message-ID: <00d001d291e2$dfb7d950$9f278bf0$@rora.be> (raw)
Dear all,
Im currently doing me masters thesis on the subject of Wireless Mesh
Networks and how to optimize them for home use.
The devices I use are 5x PC Engine APU2c4 with 2x QCA9880 chip (Compex
WLE900VX). All of them are running LEDE (OpenWRT fork).
The problem Im experiencing is the same as
http://lists.infradead.org/pipermail/ath10k/2017-January/009075.html . Using
the tips mentioned I did not come to a better performance. Im thinking its
driver related..
When running iperf3 only one direction is running at a reasonable
throughput. Since I am using adhoc mode primarily I decided to use these
packages:
- Kmod-ath10k-ct
- Ath10k-firmware-qca988x-ct
Some sources on the internet said that using the Candela Tech drivers should
result in better support for adhoc/mesh networks.
As suggested in the other issue linked above, I switched TCP congestion
control to Reno instead of the default Cubic.
I also did try the command iw reg set BE since I am from Belgium, but
running iw reg get right after still gave me US as a result.
Let me know what additional command info I should post. Any help would be
greatly appreciated.
Iwconfig:
adhoc0 IEEE 802.11 ESSID:"mesh"
Mode:Ad-Hoc Frequency:5.18 GHz Cell: 02:CA:FE:CA:CA:40
Tx-Power=20 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Iw reg get (Im from Belgium):
global
country BE: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW
(5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
Kind regards,
Met vriendelijke groeten,
Ralph Houthoofdt
Student industriële wetenschappen informatica
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2017-02-28 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 16:51 Ralph Houthoofdt [this message]
2017-02-28 16:56 ` QCA9880 slow performance adhoc/IBSS mode Ben Greear
2017-02-28 17:36 ` Ralph Houthoofdt
2017-02-28 17:41 ` Ben Greear
2017-02-28 18:02 ` Ralph Houthoofdt
2017-02-28 18:11 ` Ben Greear
2017-02-28 21:48 ` Ralph Houthoofdt
2017-02-28 22:02 ` Ben Greear
2017-03-01 8:21 ` Ralph Houthoofdt
2017-03-01 14:50 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00d001d291e2$dfb7d950$9f278bf0$@rora.be' \
--to=ralph@rora.be \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox