* Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
@ 2016-02-16 14:33 Lindner, Frank
2016-02-16 14:46 ` Michal Kazior
0 siblings, 1 reply; 4+ messages in thread
From: Lindner, Frank @ 2016-02-16 14:33 UTC (permalink / raw)
To: ath10k
Hi there,
I'm using QCA980 hw2.0 (Compex WLE900VX5) in monitor mode. Using Linux Kernel 4.3.3 and ath10k firmware 10.2.4.70.19-2.
When capturing 2.4 GHz WIFI operating in 802.11g (1 to 54 Mbit/s), Wireshark displays only 1, 2, 5.5 or 11 Mbit/s as TX rate for the frames. When capturing in parallel with Airpcap on Windows or a Ralink-based card in monitor mode, frame TX rate is displayed correctly with 1 to 54 Mbit/s.
I also tried older firmware versions. Same issue.
Also when trying to capture with tcpdump, only up 11 Mbit/s is shown.
Is this a known issue?
Is there any fix for this?
iw phy phy0 info
Wiphy phy0
Band 1:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (disabled)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Band 2:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-23
Frequencies:
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (23.0 dBm) (passive scanning, no IBSS, radar detection)
* 5280 MHz [56] (23.0 dBm) (passive scanning, no IBSS, radar detection)
* 5300 MHz [60] (23.0 dBm) (passive scanning, no IBSS, radar detection)
* 5320 MHz [64] (23.0 dBm) (passive scanning, no IBSS, radar detection)
* 5500 MHz [100] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5520 MHz [104] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5540 MHz [108] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5560 MHz [112] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5580 MHz [116] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5600 MHz [120] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5620 MHz [124] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5640 MHz [128] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5660 MHz [132] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5680 MHz [136] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5700 MHz [140] (30.0 dBm) (passive scanning, no IBSS, radar detection)
* 5720 MHz [144] (30.0 dBm) (radar detection)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 16
max scan IEs length: 195 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x7 RX 0x7
Configured Antennas: TX 0x7 RX 0x7
Supported interface modes:
* managed
* AP
* AP/VLAN
* monitor
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ AP } <= 8,
total <= 8, #channels <= 1, STA/AP BI must match
Supported commands:
* new_interface
* set_interface
* new_key
* new_beacon
* new_station
* new_mpath
* set_mesh_params
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* action
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* Unknown command (84)
* Unknown command (87)
* Unknown command (85)
* Unknown command (89)
* Unknown command (92)
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* Unknown mode (10): 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* Unknown mode (10): 0x40 0xd0
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
dmesg:
[ 4.135577] ath10k_pci 0000:11:00.0: qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.2.4.70.19-2 api 5 htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1 features no-p2p,raw-mode
[ 4.135582] ath10k_pci 0000:11:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 4.280056] ath: EEPROM regdomain: 0x0
[ 4.280058] ath: EEPROM indicates default country code should be used
[ 4.280059] ath: doing EEPROM country->regdmn map search
[ 4.280065] ath: country maps to regdmn code: 0x3a
[ 4.280065] ath: Country alpha2 being used: US
[ 4.280066] ath: Regpair used: 0x3a
[ 4.402764] cfg80211: Current regulatory domain intersected:
[ 4.402769] cfg80211: DFS Master region: unset
[ 4.402770] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 4.402771] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 4.402773] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 4.402778] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2300 mBm), (0 s)
[ 4.402779] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 3000 mBm), (0 s)
[ 4.402780] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Best Regards,
Frank
Vorstandsvorsitzender: Dipl.-Ing. Dirk Wilhelm
Aufsichtsratsvorsitzender: Dr.-Ing. Peter Hasse
Handelsregister: HRB Saarbrücken Nr. 13201
Ust.ID Nr.: DE 153807627
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
2016-02-16 14:33 Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark Lindner, Frank
@ 2016-02-16 14:46 ` Michal Kazior
2016-02-16 15:02 ` AW: " Lindner, Frank
0 siblings, 1 reply; 4+ messages in thread
From: Michal Kazior @ 2016-02-16 14:46 UTC (permalink / raw)
To: Lindner, Frank; +Cc: ath10k
On 16 February 2016 at 15:33, Lindner, Frank <Frank.Lindner@ghmt.de> wrote:
> Hi there,
>
> I'm using QCA980 hw2.0 (Compex WLE900VX5) in monitor mode. Using Linux Kernel 4.3.3 and ath10k firmware 10.2.4.70.19-2.
> When capturing 2.4 GHz WIFI operating in 802.11g (1 to 54 Mbit/s), Wireshark displays only 1, 2, 5.5 or 11 Mbit/s as TX rate for the frames. When capturing in parallel with Airpcap on Windows or a Ralink-based card in monitor mode, frame TX rate is displayed correctly with 1 to 54 Mbit/s.
> I also tried older firmware versions. Same issue.
> Also when trying to capture with tcpdump, only up 11 Mbit/s is shown.
> Is this a known issue?
> Is there any fix for this?
https://wireless.wiki.kernel.org/en/users/drivers/ath10k#known_bugslimitations
If you don't mind dirtying your hands with some C code you can try
using the following patch (it will not cleanly apply to upstream
kernel but should be fairly straightforward to port):
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-checkins/YGYm6gNUnEE
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* AW: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
2016-02-16 14:46 ` Michal Kazior
@ 2016-02-16 15:02 ` Lindner, Frank
2016-02-16 15:17 ` Michal Kazior
0 siblings, 1 reply; 4+ messages in thread
From: Lindner, Frank @ 2016-02-16 15:02 UTC (permalink / raw)
To: Michal Kazior; +Cc: ath10k
Hi Michal,
thanks for your instant response.
May I ask why this isn't implemented in a new firmware release?
Is there a short manual, what and where I need to edit the code and how to compile it? I'm not that familiar with coding on that level.
Thanks.
Best Regards,
Frank
-----Ursprüngliche Nachricht-----
Von: Michal Kazior [mailto:michal.kazior@tieto.com]
Gesendet: Dienstag, 16. Februar 2016 15:46
An: Lindner, Frank
Cc: ath10k@lists.infradead.org
Betreff: Re: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
On 16 February 2016 at 15:33, Lindner, Frank <Frank.Lindner@ghmt.de> wrote:
> Hi there,
>
> I'm using QCA980 hw2.0 (Compex WLE900VX5) in monitor mode. Using Linux Kernel 4.3.3 and ath10k firmware 10.2.4.70.19-2.
> When capturing 2.4 GHz WIFI operating in 802.11g (1 to 54 Mbit/s), Wireshark displays only 1, 2, 5.5 or 11 Mbit/s as TX rate for the frames. When capturing in parallel with Airpcap on Windows or a Ralink-based card in monitor mode, frame TX rate is displayed correctly with 1 to 54 Mbit/s.
> I also tried older firmware versions. Same issue.
> Also when trying to capture with tcpdump, only up 11 Mbit/s is shown.
> Is this a known issue?
> Is there any fix for this?
https://wireless.wiki.kernel.org/en/users/drivers/ath10k#known_bugslimitations
If you don't mind dirtying your hands with some C code you can try using the following patch (it will not cleanly apply to upstream kernel but should be fairly straightforward to port):
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-checkins/YGYm6gNUnEE
Michał
Vorstandsvorsitzender: Dipl.-Ing. Dirk Wilhelm
Aufsichtsratsvorsitzender: Dr.-Ing. Peter Hasse
Handelsregister: HRB Saarbrücken Nr. 13201
Ust.ID Nr.: DE 153807627
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
2016-02-16 15:02 ` AW: " Lindner, Frank
@ 2016-02-16 15:17 ` Michal Kazior
0 siblings, 0 replies; 4+ messages in thread
From: Michal Kazior @ 2016-02-16 15:17 UTC (permalink / raw)
To: Lindner, Frank; +Cc: ath10k
On 16 February 2016 at 16:02, Lindner, Frank <Frank.Lindner@ghmt.de> wrote:
> Hi Michal,
>
> thanks for your instant response.
> May I ask why this isn't implemented in a new firmware release?
I don't know.
The patch I've pointed out uses a hacky approach by using firmware
debugging interface to get the tx rate info. Because of that it
carries an inherent performance degradation.
> Is there a short manual, what and where I need to edit the code and how to compile it? I'm not that familiar with coding on that level.
Hmm.. The least painful and fairly documented procedure would be to
use backports:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/backports
https://backports.wiki.kernel.org/index.php/Documentation
You'll then need to port the changes from the pointed patch into
there. Note: chromium uses `wireless-xxx` masking. You'll need to make
sure you apply changes to drivers/net/wireless/ath/ath10k directory.
Here's a few words on the diff format used for patches:
https://en.wikipedia.org/wiki/Diff_utility#Variations
Michał
> Thanks.
>
> Best Regards,
> Frank
>
> -----Ursprüngliche Nachricht-----
> Von: Michal Kazior [mailto:michal.kazior@tieto.com]
> Gesendet: Dienstag, 16. Februar 2016 15:46
> An: Lindner, Frank
> Cc: ath10k@lists.infradead.org
> Betreff: Re: Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark
>
> On 16 February 2016 at 15:33, Lindner, Frank <Frank.Lindner@ghmt.de> wrote:
>> Hi there,
>>
>> I'm using QCA980 hw2.0 (Compex WLE900VX5) in monitor mode. Using Linux Kernel 4.3.3 and ath10k firmware 10.2.4.70.19-2.
>> When capturing 2.4 GHz WIFI operating in 802.11g (1 to 54 Mbit/s), Wireshark displays only 1, 2, 5.5 or 11 Mbit/s as TX rate for the frames. When capturing in parallel with Airpcap on Windows or a Ralink-based card in monitor mode, frame TX rate is displayed correctly with 1 to 54 Mbit/s.
>> I also tried older firmware versions. Same issue.
>> Also when trying to capture with tcpdump, only up 11 Mbit/s is shown.
>> Is this a known issue?
>> Is there any fix for this?
>
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k#known_bugslimitations
>
> If you don't mind dirtying your hands with some C code you can try using the following patch (it will not cleanly apply to upstream kernel but should be fairly straightforward to port):
>
> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-checkins/YGYm6gNUnEE
>
>
> Michał
>
>
>
> Vorstandsvorsitzender: Dipl.-Ing. Dirk Wilhelm
> Aufsichtsratsvorsitzender: Dr.-Ing. Peter Hasse
> Handelsregister: HRB Saarbrücken Nr. 13201
> Ust.ID Nr.: DE 153807627
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-02-16 15:18 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-16 14:33 Bug: QCA9880 hw2.0: TX-Rate Display in Wireshark Lindner, Frank
2016-02-16 14:46 ` Michal Kazior
2016-02-16 15:02 ` AW: " Lindner, Frank
2016-02-16 15:17 ` Michal Kazior
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.