linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: carl9170 - monitor mode TP drop
Date: Mon, 23 Apr 2012 08:47:55 +0200	[thread overview]
Message-ID: <1335163675.3928.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAFED-jkFtT2agUpymwWN-srTVH+wkh7bbkgkxQg9e4vy+q-Xvw@mail.gmail.com> (sfid-20120423_062709_111941_72F1C6FE)

On Mon, 2012-04-23 at 06:27 +0200, Janusz Dziedzic wrote:

> This is a scenario:
> AP <--> STA1 (channel 6)
> STA2 == carl_monitor (channel 6)
> 
> This is what I can see on STA1:
> # iperf -c 192.168.254.1 -t 100 -i 5
> ------------------------------------------------------------
> Client connecting to 192.168.254.1, TCP port 5001
> TCP window size:  512 KByte (default)
> ------------------------------------------------------------
> [  3] local 192.168.254.181 port 46048 connected with 192.168.254.1 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [  3]  0.0- 5.0 sec  17.4 MBytes  29.2 Mbits/sec
> [  3]  5.0-10.0 sec  19.6 MBytes  32.9 Mbits/sec
> [  3] 10.0-15.0 sec  20.4 MBytes  34.2 Mbits/sec
> [  3] 15.0-20.0 sec  19.8 MBytes  33.1 Mbits/sec
> [  3] 20.0-25.0 sec  19.8 MBytes  33.1 Mbits/sec
> [  3] 25.0-30.0 sec  19.8 MBytes  33.1 Mbits/sec
> [  3] 30.0-35.0 sec  19.6 MBytes  32.9 Mbits/sec
> [  3] 35.0-40.0 sec  18.1 MBytes  30.4 Mbits/sec
> 
> =====> here I setup carl monitor on second PC, like this:
> =====> iw dev wlan0 set type monitor
> =====> iw dev wlan0 set freq 2437
> =====> ifconfig wlan0 up
> 
> [  3] 40.0-45.0 sec  2.38 MBytes  3.98 Mbits/sec
> [  3] 45.0-50.0 sec  2.50 MBytes  4.19 Mbits/sec
> [  3] 50.0-55.0 sec  3.00 MBytes  5.03 Mbits/sec
> 
> Seems I don't even need to start wireshark here ... and see this TP drop.

FWIW, I have observed this as well (in the past, my ar9170 devices all
died now)

johannes


  reply	other threads:[~2012-04-23  6:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20  7:41 carl9170 - monitor mode TP drop Janusz Dziedzic
2012-04-20 17:59 ` Christian Lamparter
2012-04-23  4:27   ` Janusz Dziedzic
2012-04-23  6:47     ` Johannes Berg [this message]
2012-04-23 17:45     ` Christian Lamparter
2012-04-25  5:28       ` Janusz Dziedzic
2012-04-25 17:28         ` Christian Lamparter
2012-04-25 18:24           ` Janusz Dziedzic
2012-04-25 18:54             ` Christian Lamparter
2012-04-26  7:45               ` Janusz Dziedzic
2012-04-26 18:25                 ` Christian Lamparter
2012-05-03  7:58           ` Johannes Berg
2012-05-03 21:44             ` Christian Lamparter
2012-05-07  7:00               ` Johannes Berg

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=1335163675.3928.1.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@googlemail.com \
    --cc=janusz.dziedzic@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).