From: Michael Buesch <mb@bu3sch.de>
To: James Ketrenos <jketreno@linux.intel.com>
Cc: linux-wireless@vger.kernel.org, Zhu Yi <yi.zhu@intel.com>
Subject: Re: IPW2200 monitoring FW broken
Date: Thu, 15 Feb 2007 20:20:27 +0100 [thread overview]
Message-ID: <200702152020.28131.mb@bu3sch.de> (raw)
In-Reply-To: <45D49BDA.30402@linux.intel.com>
On Thursday 15 February 2007 18:43, James Ketrenos wrote:
> Michael Buesch wrote:
> > On Thursday 15 February 2007 17:35, James Ketrenos wrote:
> >> you can't update the packet capture
> >> window or you'll lose packets; but you should be able to get them all if
> >> you're doing a tethereal > somefile or if you turn off the update of the
> >> main window.
> >
> > "update of the packet capture window". What's that?
> > I started a simple traffic monitoring in wireshark. Nothing fancy.
>
> In the 'Capture Options', the only option you can set is 'Hide capture
> info dialog'. If you turn on 'Update list of packets in real time' or
> 'Automatic scrolling in live capture', packets get dropped. I don't
> know if its a libpcap queue that fills up, if it starves the NIC, or
> what--but having those turned on greatly reduces the # of packets you'll
> capture.
Hm, yeah. I have that turned on. But I don't see this issue
when monitoring with bcm43xx hardware.
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-15 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 17:40 IPW2200 monitoring FW broken Michael Buesch
2007-02-15 16:35 ` James Ketrenos
2007-02-15 18:10 ` Michael Buesch
2007-02-15 17:43 ` James Ketrenos
2007-02-15 19:20 ` Michael Buesch [this message]
2007-02-15 18:07 ` James Ketrenos
2007-02-15 19:57 ` Michael Buesch
2007-02-16 9:26 ` Johannes Berg
2007-02-18 3:41 ` Daniel Drake
2007-02-18 11:27 ` Michael Buesch
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=200702152020.28131.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.com \
/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).