From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-wireless@vger.kernel.org
Subject: Linux iwlwifi 801.11n speeds
Date: Mon, 30 Jun 2014 15:43:36 -0600 [thread overview]
Message-ID: <2766921.O7z3bAoKY3@balsa> (raw)
Hi,
I've been doing some reasearch and testing lately, and have noticed that
802.11n speeds in linux on two iwlwifi devices (6300, 6205) are anywhere from
20 to 40mbps slower than in windows 7.
I've tried enabling swcrypto and disabling power management, and neither help.
While signal strength seems to be better in windows based on the signal meter,
they may just calculate signal bars differently. I don't know.
Is there anything I can do to achieve similar speeds? I easily reach 90+ mbps
in windows, and rarely reach 70 mbps in linux.
I'm running debian sid, with the 3.14.7 and 3.14.4 debian kernels, and should
have the latest iwlwifi firmware.
I have a dual band Ubiquity AP Pro ap connected to a Sokeris 6501-50 firewall
appliance running debian sid as well, and connected to a full GbE lan, which
regularly achieves full speeds of 90MBps+. All settings on the actual network
were not changed between speed tests. N was tested solely on the 5Ghz band,
channel 36, and there is very little interference here on 5ghz. There is one
other network visible and its on the other end of the 5ghz band.
Oh, and my nexus 7 (2013) also achieves 90mbps+, it may even get better, but I
haven't managed to test local speeds, just tested with the speedtest.net app,
and my internet is 100mbps, so it pretty much maxes it out.
Thank you for any assistance.
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next reply other threads:[~2014-06-30 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:43 Thomas Fjellstrom [this message]
2014-07-01 8:23 ` Linux iwlwifi 801.11n speeds Peter Wu
2014-07-02 2:51 ` Thomas Fjellstrom
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=2766921.O7z3bAoKY3@balsa \
--to=thomas@fjellstrom.ca \
--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).