From: Larry Finger <Larry.Finger@lwfinger.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>, linux-wireless@vger.kernel.org
Subject: Re: Problems associating with RTL8188CE
Date: Sat, 19 Nov 2011 23:25:44 -0600 [thread overview]
Message-ID: <4EC88F58.1080203@lwfinger.net> (raw)
In-Reply-To: <20111118225422.GD19138@thinkpad-t410>
On 11/18/2011 04:54 PM, Seth Forshee wrote:
> I'm seeing a lot of problems associating with APs when using a Toshiba
> NB505 with RTL8188CE wireless. The situation seems to have improved
> quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
> number of failed associations. This card doesn't seem to like my Linksys
> E2000 router in particular; I rarely see a successful association with
> this router.
>
> I'm attaching logs from the kernel and wpa_supplicant from some failed
> associations with the E2000 along with the wpa_supplicant configuration
> I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
> other information is needed, please let me know.
Would it be possible for you to have a separate computer log the transaction
between the AP with ESSID 'Kailia' and the RTL8188CE using wireshark or Kismet?
Chaoming may see something in the logs that I do not, but the request for
authentication is timing out. With wireshark, we can see what is actually on the
air.
Larry
next prev parent reply other threads:[~2011-11-20 5:25 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 [this message]
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
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=4EC88F58.1080203@lwfinger.net \
--to=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).