[ath9k-devel] [RFC 0/2] ath10k: fix qos workaround

[Kalle Valo <kvalo@qca.qualcomm.com>]

Hi Michal,

Michal Kazior <michal.kazior@tieto.com> writes:

> On 24/04/13 12:53, Sujith Manoharan wrote:
>> Michal Kazior wrote:
>>> >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).