Skip to content

RFC ath10k: fix qos workaround

Michal Kazior ath9k-devel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [ath9k-devel] [RFC 0/2] ath10k: fix qos workaround
Quoted 10 lines · Sujith Manoharan
Quoted 6 lines · Michal Kazior
Quoted 1 line

From what I've observed so far is frames in

monitor mode (non promiscuous) are corrupted. They have the QoS Control stripped, with LLC header finding itself in the QoS Control. Wireshark shows such packets as A-MSDU corrupted frames. I tried restoring the QoS Control but it didn't fix that.

I don't understand. Why should pure monitor mode care about the TX path ?

This is not concerned with the pure (I hope we don't have a misunderstanding here) monitor mode.

You can create monitor vif when associated and you might want to listen to the traffic *without* going into the promiscuous mode (no monitor vdev is created). It simply passes raw 802.11 frames that pass through mac80211 (both tx and rx) on other interfaces (i.e. associated station interface).

-- Pozdrawiam / Best regards, Michal Kazior.