Thanks for the info, Brian! This is unfortunate. Coincidentally, I came across this commit earlier today...I’ll see what I can do about undoing the changes in my kernel or at least making the necessary changes to prevent the driver from filtering non-multicast packets addressed to other destinations. Best, Tomasz On Mon, Aug 13, 2018 at 6:40 PM, Brian Norris <computersforpeace@xxxxxxxxx> wrote: > > On Mon, Aug 06, 2018 at 06:08:46PM -0400, Tomasz Kalbarczyk wrote: > > Hello, > > Hi! > > > I have a QCA6174 and I'm running tcpdump on the wireless interface to > > listen for packets. I can receive packets addressed directly to the > > device, but not any other packets on the network. > > > > Does anyone know the status of promiscuous mode support on ath10k? > > Note that this is different from monitor mode / supported on a larger > > subset of hardware. Dmesg merely indicates that the device has > > "entered promiscuous mode" when tcpdump is initiated. > > > > Here is a link to similar discussion regarding the ath9k a few years > > back: https://marc.info/?l=linux-wireless&m=135936563626791&w=2 > > This might be relevant: > > commit df1404650ccbfeb76a84f301f22316be0d00a864 > Author: Johannes Berg <johannes.berg@xxxxxxxxx> > Date: Wed Apr 22 14:40:58 2015 +0200 > > mac80211: remove support for IFF_PROMISC > > This support is essentially useless as typically networks are encrypted, > frames will be filtered by hardware, and rate scaling will be done with > the intended recipient in mind. For real monitoring of the network, the > monitor mode support should be used instead. > > Removing it removes a lot of corner cases. > > Regards, > Brian
