linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Seth Forshee <seth.forshee@canonical.com>,
	Chaoming Li <chaoming_li@realsil.com.cn>,
	linux-wireless@vger.kernel.org
Subject: Re: Problems associating with RTL8188CE
Date: Thu, 15 Dec 2011 11:41:23 -0700	[thread overview]
Message-ID: <4EEA3F53.40305@canonical.com> (raw)
In-Reply-To: <4EE9445B.1010504@lwfinger.net>

On 12/14/2011 05:50 PM, Larry Finger wrote:
> Tim,
>
> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
> connected with my WNDR3300 with no difficulty. I tested all 4 modes
> supported by the AP. All worked.
>
> I assume that an installation would work the same as the live version,
> but that is easy for you to test.
>
> Larry
>

Here are the 3 modes I was able to successfully test on my WNDR3300 as 
an open AP:

* Up to 270Mbps at 2.4Ghz
   11N Channel:	03/2.422Ghz
   in this mode only the 11N SSID is beaconed.
   iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71

* Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
   11N Channel: 36 / 5.180Ghz
   11G Channel: auto
   in this mode only the G beacon can be seen (which makes sense)
   iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97

* Up to 130Mbps at 2.4Ghz
   11N Channel:	03/2.422Ghz
   in this mode only the 11N SSID is beaconed.
   iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44

This mode would not acquire a beacon using the rtl8192ce:

* Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
   11N Channel: 36 / 5.180Ghz
   11G Channel: auto
   in this mode no beacon can be seen.

I verified using a MacBook Air under OS/X that the N SSID was appearing 
on the 5 Ghz channel, but couldn't see the G beacon. Maybe its a bug in 
the WNDR3300.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

  reply	other threads:[~2011-12-15 18:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 22:54 Problems associating with RTL8188CE Seth Forshee
2011-11-20  5:25 ` Larry Finger
2011-11-21 18:13   ` Seth Forshee
2011-11-21 18:34     ` Larry Finger
2011-11-21 18:56       ` Seth Forshee
2011-11-22  2:01         ` Larry Finger
2011-11-22  2:20           ` Seth Forshee
2011-11-29 18:55             ` Seth Forshee
2011-12-13 19:42             ` Seth Forshee
2011-12-13 20:41               ` Larry Finger
2011-12-13 21:26                 ` Seth Forshee
2011-12-14  4:57                   ` Larry Finger
2011-12-14 16:23                     ` Seth Forshee
2011-12-14 16:39                       ` Larry Finger
2011-12-14 16:49                         ` Seth Forshee
2011-12-14 16:58                           ` Larry Finger
2011-12-14 17:12                             ` Seth Forshee
2011-12-14 17:25                               ` Larry Finger
2011-12-14 17:43                               ` Larry Finger
2011-12-14 17:58                                 ` Seth Forshee
2012-01-26 21:33                                   ` Seth Forshee
2012-01-26 23:50                                     ` Larry Finger
2012-01-27  3:06                                       ` Seth Forshee
2012-01-27 17:05                                         ` Seth Forshee
2012-01-27 18:14                                           ` Larry Finger
2011-12-14 21:52                           ` Tim Gardner
2011-12-14 22:54                             ` Larry Finger
2011-12-15  0:50                             ` Larry Finger
2011-12-15 18:41                               ` Tim Gardner [this message]
2011-12-15 19:50                                 ` Larry Finger
2011-12-16 16:53                                   ` Tim Gardner
2011-12-16 17:06                                     ` Larry Finger
2011-12-16 17:11                                       ` Tim Gardner

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=4EEA3F53.40305@canonical.com \
    --to=tim.gardner@canonical.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chaoming_li@realsil.com.cn \
    --cc=linux-wireless@vger.kernel.org \
    --cc=seth.forshee@canonical.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).