From: Larry Finger <Larry.Finger@lwfinger.net>
To: Tim Gardner <tim.gardner@canonical.com>
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 13:50:38 -0600 [thread overview]
Message-ID: <4EEA4F8E.60602@lwfinger.net> (raw)
In-Reply-To: <4EEA3F53.40305@canonical.com>
On 12/15/2011 12:41 PM, Tim Gardner wrote:
> 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.
I had never used the "auto" channel setting before. When I set my AP to the same
configuration as yours (130/54 and 36/auto), it sent the 802.11n beacon in the
2.4GHz channel. The 11G SSID was not seen; however, I could connect to the AP on
channel 1. When I switched to 11G channel 1, rather than auto, then I saw the
11G SSID in the beacon. I then tested the 5G band using a Dell DW1450 (p54usb)
dual-band device. The 11N SSID was present on channel 36 using auto or channel 1.
There may be a bug in the WNDR3300 firmware. Sometimes when I switched from
channel 1 to auto for the 2G band, that band would beacon the 11G SSID, and
other times, it would beacon the 11N SSID. I have not determined a pattern. The
11N SSID is always shown on the selected 5G channel. I could, however, connect
the RTL8188CE to whatever SSID the AP was sending on the 2.4GHz band.
Curiouser and curiouser,
Larry
next prev parent reply other threads:[~2011-12-15 19:50 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
2011-12-15 19:50 ` Larry Finger [this message]
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=4EEA4F8E.60602@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=tim.gardner@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).