From: Christian Lamparter <chunkeey@googlemail.com>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: carl9170 - monitor mode TP drop
Date: Fri, 20 Apr 2012 19:59:54 +0200 [thread overview]
Message-ID: <201204201959.56495.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAFED-j=fZjXVhLKe=eOHM-rhR7g1ZvHeSMm1jUA0bdJbk4_qWQ@mail.gmail.com>
On Friday 20 April 2012 09:41:15 Janusz Dziedzic wrote:
> Hello,
>
> I am using newest compat-wireless + newest-firmware.
> Next I setup monitor mode + channel and run wireshark - I do that to
> record TCP flow on the channel.
>
> Before that I had TCP throughput about 30Mbit/s and after run
> wireshark I see TP drop - about 3Mbit/s (after setting monitor mode).
> This TP is between AP and other STA on the same channel.
>
> Should I set/check something more to not see this TP drop?
Well, I don't know how you exactly setup the mode. But If
the monitor interface is set to PROMISC, then it's likely
that the hardware will be set into a special "sniffer"
operation mode. This mode is great if you are interested in
frames with bad PLCPs and FCS but it is not so great for
throughput because the rx filter won't filter anymore and
the tons of garbage that usually is dropped early on gets
passed to the host and on it's way it competes for FIFO
resources with the data.
(One more thing: Isn't it possible to get the TCP flow,
from the "ethernet" (as ifconfig calls it) interface of
the wlan device as well?)
Regards,
Christian
next prev parent reply other threads:[~2012-04-20 18:00 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 [this message]
2012-04-23 4:27 ` Janusz Dziedzic
2012-04-23 6:47 ` Johannes Berg
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=201204201959.56495.chunkeey@googlemail.com \
--to=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).