> On Sun, Apr 10, 2016 at 1:28 PM, Grumbach, Emmanuel > <emmanuel.grumbach@xxxxxxxxx> wrote: > >> > On Tue, 2016-04-05 at 16:25 +0300, Gucea Doru wrote: > >> Is the iwlwifi driver capable of capturing data frames when the > >> channel bonding is set to 80Mhz? > > > > dev <devname> set freq <control freq> [20|40|80|80+80|160] [<center > > freq 1>] [<center freq 2>] > > > > You can take center_freq1 from the output of iw dev on a device that is > associated to the same AP. > > Thanks a lot, Emmanuel. My iw binary that came default with my Ubuntu > distribution was very old (3.4) and it didn't have support for channel bonding > larger than 40Mhz. > I compiled the latest iw version from sources then I took the > center_freq1 from the beacon advertised by the AP. That's because the iw > dev on a device associated to the same AP gave me the control frequency. > After that, I was able to capture the data frames. > > One more question that I promise to be the last one: > - I am trying to capture the Wi-Fi Direct traffic between two > smartphones: iw shows me that the p2p interface from one of the > smartphones uses 2.4Ghz, channel 1 so I set the monitor interface on 2.4, > channel 1. The problem is that, again, I can't see the data frames. Instead, I > can see the Association/Authentication Request, RTS/CTS, Block ACK (I > attached the Wireshark capture at [1]). > .... .... .... ...1 = HT LDPC coding capability: Transmitter supports receiving LDPC coded packets This means that both sides use a coding algo that 7260 doesn't understand. 7260 talks Viterbi. The only way to go here is to get a 7265 module (or later) instead. > Analyzing the capture, I noticed that the HT capabilities advertised in the > beacon frames indicates 802.11n D1.10. Does this trigger any indication for > you on how to setup the monitor interface? > > [1] > https://drive.google.com/file/d/0B5SBH08PU_ChNllaVHRienBSVlE/view?usp > =sharing > > Regards, > Doru ��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
