linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: darklight wu <darklightwu@gmail.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Failed to capture data packets using Monitor mode with Intel 7260 card. (Under Ubuntu 14.04)
Date: Wed, 20 May 2015 00:44:51 +0800	[thread overview]
Message-ID: <CALWn1pt-neiJhrQcEES4cktcfyL0+c2B=GUAh8+Xo0L06VmsfA@mail.gmail.com> (raw)
In-Reply-To: <CANUX_P3XPLvLhYy7pb9_LXjEynfNjgzhbW3zFYfxVCjcjGNczw@mail.gmail.com>

On Mon, May 18, 2015 at 3:26 PM, Emmanuel Grumbach <egrumbach@gmail.com> wrote:
> On Mon, May 18, 2015 at 10:01 AM, darklight wu <darklightwu@gmail.com> wrote:
>> Hi, All:
>>
>> I configured the Wifi Monitor mode with Intel 7260 card under
>> Ubuntu14.04 and then used Wireshark to capture packets from air. But I
>> could only get management/control packets but no data packets. I tried
>> different channels and also with HT20 or HT40+/-.
>>
>> The commands I used were:
>>
>> iw dev wlan0 interface add mon0 type monitor
>> iw dev wlan0 del  //I googled and was told I needed to delete the
>> wlan0 first. Or else I got device busy (-16) error
>> ifconfig mon0 up
>> iw dev mon0 set channel 1
>>
>> I also tried to use other ways like "airmon-ng start wlan0". All the
>> observations were same, no data packets. It's weird! Anyone has a
>> clue?
>>
>
> This is weird. But I recommend to add power_scheme=1 as a module
> parameter to iwlmvm. Since iwlmvm is loaded automatically, you'll need
> to add that to /etc/modprobe.d/iwlwifi.conf.
> 14.04 ships 3.13 and I remember we had issues with monitor mode at
> that time. You may want to try a newer kernel.

I tried again today with "power_scheme=1" and also booted with Ubuntu
15.04. Both still failed to work in monitor mode. And with Ubuntu
15.04, I event could not configure the nic to work on monitor mode.
The same commands at least can set the monitor mode under 14.04.
Meanwhile, I just want to clarify, the nic could capture data packets
to/from itself but could not capture others that were not belongs to
it. My co-worker tried on another machine with Ubuntu 14.04, he was
also failed.

Any tricks here?

  reply	other threads:[~2015-05-19 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  7:01 Failed to capture data packets using Monitor mode with Intel 7260 card. (Under Ubuntu 14.04) darklight wu
2015-05-18  7:26 ` Emmanuel Grumbach
2015-05-19 16:44   ` darklight wu [this message]
2015-05-19 17:41     ` Emmanuel Grumbach
2015-05-20  3:43       ` Matt Chen
2015-05-20  4:00         ` darklight wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALWn1pt-neiJhrQcEES4cktcfyL0+c2B=GUAh8+Xo0L06VmsfA@mail.gmail.com' \
    --to=darklightwu@gmail.com \
    --cc=egrumbach@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).