From: Hans Ekbrand <hans@sociologi.cjb.net>
To: linux-wireless@vger.kernel.org
Subject: USB 1.1, usb-dongle, NETGEAR WG111v2, timing problems in association
Date: Sat, 17 Jan 2009 21:46:57 +0100 [thread overview]
Message-ID: <20090117204654.GB9079@amin> (raw)
[-- Attachment #1: Type: text/plain, Size: 5206 bytes --]
Hi list!
On an old system with only USB 1.1, I tried to use a USB-dongle:
NETGEAR WG111v2. The device works perfectly with same kernel (2.6.26-1
from debian lenny) on a new system with USB 2.0, using the "rtl8187"
driver.
However, on USB 1.1 I get:
Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: Initial auth_alg=0
Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:17 jonspc kernel: [13991.380267] wlan1: authenticated
Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:17 jonspc kernel: [13991.604259] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: Initial auth_alg=0
Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.136073] wlan1: association frame received from 00:1b:2f:0c:2f:28, but not in associate state - ignoredel: [13992.340113] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
[Longer part of syslog follows later in this post]
I tried to use the device on two USB 1.1 systems, both failed with the
"association frame received ... but not in associate state - ignore",
message.
Is USB 2.0 required, or is there a workaround for this problem?
Here is the output of lsusb:
Bus 001 Device 066: ID 0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek RTL8187L]
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Below is a longer exerpt from syslog:
no key needed. jonspc NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan1#011#011wext#011/var/run/wpa_supplicant#011'spc NetworkManager: <info> SUP: response was 'OK'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was '0'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 48656c676573'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jan 17 17:25:01 jonspc NetworkManager: <info> SUP: response was 'OK'
Jan 17 17:25:01 jonspc kernel: [13975.564161] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:01 jonspc kernel: [13975.564194] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:01 jonspc kernel: [13975.564194] wlan1: authenticated
Jan 17 17:25:01 jonspc kernel: [13975.564194] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:02 jonspc kernel: [13975.788114] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:02 jonspc kernel: [13975.988110] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:02 jonspc kernel: [13976.188137] wlan1: association with AP 00:1b:2f:0c:2f:28 timed out
Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: Initial auth_alg=0
Jan 17 17:25:17 jonspc kernel: [13991.380234] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:17 jonspc kernel: [13991.380267] wlan1: authenticated
Jan 17 17:25:17 jonspc kernel: [13991.380267] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:17 jonspc kernel: [13991.604259] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: Initial auth_alg=0
Jan 17 17:25:18 jonspc kernel: [13992.136025] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.136073] wlan1: association frame received from 00:1b:2f:0c:2f:28, but not in associate state - ignoredel: [13992.340113] wlan1: authenticate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.343090] wlan1: RX authentication from 00:1b:2f:0c:2f:28 (alg=0 transaction=2 status=0)5:18 jonspc kernel: [13992.343116] wlan1: authenticated
Jan 17 17:25:18 jonspc kernel: [13992.343126] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.343116] wlan1: authenticated
Jan 17 17:25:18 jonspc kernel: [13992.343126] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:18 jonspc kernel: [13992.540122] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:19 jonspc kernel: [13992.740140] wlan1: associate with AP 00:1b:2f:0c:2f:28
Jan 17 17:25:19 jonspc kernel: [13992.940143] wlan1: association with AP 00:1b:2f:0c:2f:28 timed out
--
Hans Ekbrand (http://sociologi.cjb.net) <hans@sociologi.cjb.net>
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
use it to ensure that this mail is from me and has not been
altered on the way to you.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2009-01-17 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 20:46 Hans Ekbrand [this message]
2009-01-18 4:38 ` USB 1.1, usb-dongle, NETGEAR WG111v2, timing problems in association Larry Finger
2009-01-19 19:07 ` Hin-Tak Leung
2009-01-20 8:52 ` Hans Ekbrand
2009-02-02 15:55 ` Hans Ekbrand
2009-02-02 16:06 ` Larry Finger
2009-02-02 19:02 ` Hans Ekbrand
2009-02-02 22:40 ` Larry Finger
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=20090117204654.GB9079@amin \
--to=hans@sociologi.cjb.net \
--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).