From: Dan Williams <dcbw@redhat.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Saqeb Akhter <saqeb.akhter@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: carl9170: wnda3100 only 54MB/s
Date: Mon, 04 Oct 2010 12:58:41 -0500 [thread overview]
Message-ID: <1286215121.2255.3.camel@dcbw.foobar.com> (raw)
In-Reply-To: <201010020519.29042.chunkeey@googlemail.com>
On Sat, 2010-10-02 at 05:19 +0200, Christian Lamparter wrote:
> On Saturday 02 October 2010 04:56:35 Saqeb Akhter wrote:
> > Nope I already noticed that 1.8.8.3 was available so to that step, I
> > am getting frequent disconnects though, it might have to do with
> > NetworkManager doing background scanning so going to try and it it to
> > stop doing that.
> Channel changes (especially with HT) are more expensive with AR9170
> than AR9271 which features "fastcc" (fast channel change).
>
> > The NetGear driver on windows seems to ignore the WMM requirement
> > looks like.
> You can actually peek into the Windows' driver logic.
> The code is available under drivers/staging/otus/(80211core)
> AFAIK, it only checks if the HT IEs are all present.
>
> > Either way that's what the problem was, going to see if i
> > can get this disconnect problem sorted out.
> I thought "the new" NetworkManager is more intelligent and
> doesn't schedule scans while the device is actively
> transmitting/receiving data. Anyway, NetworkManager is
> "just" a manager for wpa_supplicant and wpa_supp works
> well enough.
NM >= 0.8.1 will request periodic scans unless you've locked the device
to a specific BSSID, because if you've done this you are indicating that
you don't need roaming. If you haven't specified a BSSID, then we still
need periodic scans in case the device needs to roam between APs in a
multi-AP system.
Note that some drivers still appear to ignore BSSID locking.
Dan
prev parent reply other threads:[~2010-10-04 17:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimN3X_e4fZhUSoTs-GmQ9kmaJUrgnxAu8=W2dT_@mail.gmail.com>
2010-10-01 14:22 ` carl9170: wnda3100 only 54MB/s Saqeb Akhter
2010-10-01 14:36 ` Christian Lamparter
[not found] ` <AANLkTimZYgDLLag+uGgdojrckZ5tgySC+UeyHCfee74J@mail.gmail.com>
2010-10-01 22:34 ` Saqeb Akhter
2010-10-01 22:52 ` Christian Lamparter
2010-10-01 23:56 ` Saqeb Akhter
2010-10-02 0:26 ` Christian Lamparter
2010-10-02 2:32 ` Saqeb Akhter
2010-10-02 2:52 ` Christian Lamparter
2010-10-02 2:56 ` Saqeb Akhter
2010-10-02 3:19 ` Christian Lamparter
2010-10-02 3:28 ` Saqeb Akhter
2010-10-02 6:18 ` Saqeb Akhter
2010-10-02 11:32 ` Christian Lamparter
2010-10-02 16:40 ` Saqeb Akhter
2010-11-29 17:14 ` [RFC] mac80211: filter multicast rx (was: Re: carl9170: wnda3100 only 54MB/s) Christian Lamparter
2010-11-29 18:37 ` [PATCH for-2.6.37?] mac80211: ignore non-bcast mcast managment frames Christian Lamparter
2010-11-29 18:45 ` Johannes Berg
2010-11-29 19:53 ` [PATCH for-2.6.37 v2] mac80211: ignore non-bcast mcast deauth/disassoc franes Christian Lamparter
2010-12-04 21:38 ` Jouni Malinen
2010-10-04 17:58 ` Dan Williams [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=1286215121.2255.3.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=saqeb.akhter@gmail.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).