From: Seth Forshee <seth.forshee@canonical.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: Performance problems with Netgear WNDAP350
Date: Tue, 10 Sep 2013 08:55:09 -0500 [thread overview]
Message-ID: <20130910135509.GA4501@thinkpad-t410> (raw)
In-Reply-To: <21038.55900.901542.571888@gargle.gargle.HOWL>
On Tue, Sep 10, 2013 at 02:07:48PM +0530, Sujith Manoharan wrote:
> Seth Forshee wrote:
> > I posted some wireshark traces in case someone else can find something
> > else informative that I've missed. They're at
> > http://people.canonical.com/~sforshee/wndap350/:
> >
> > * iperf-iwlwifi.pcapng.gz: Trace from iperf client on Linux STA with
> > iwlwifi
> > * iperf-server.pcapng.gz: Trace from the iperf server for the same test
> > as iperf-iwlwifi
> > * iperf-osx.pcapng.gz: Trace from iperf client on OSX, using Broadcom
> > wireless
>
> The link with the iwlwifi client seems to be drowning in RTS/CTS exchanges
> compared with the osx client.
>
> iwlwifi: total: 109087, RTS - 9782 (9.0 %)
> osx: total: 522581, RTS - 8366 (1.6 %)
Yes, but I don't think that's behind the APs failure to send us frames
for long periods of time. I can better compare the RTS/CTS exchanges
between the two when I can get an otherwise stable connection to the AP
from Linux.
Seth
prev parent reply other threads:[~2013-09-10 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 21:25 Performance problems with Netgear WNDAP350 Seth Forshee
2013-09-10 8:37 ` Sujith Manoharan
2013-09-10 13:55 ` Seth Forshee [this message]
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=20130910135509.GA4501@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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