From: Dmitry Torokhov <dtor@insightbb.com>
To: chunkeey@web.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH wireless-2.6-git] prism54: WPA/RSN support for fullmac cards
Date: Wed, 22 Nov 2006 02:01:34 -0500 [thread overview]
Message-ID: <200611220201.34717.dtor@insightbb.com> (raw)
In-Reply-To: <200611181118.02549.chunkeey@web.de>
On Saturday 18 November 2006 05:18, chunkeey@web.de wrote:
> Am Samstag, 18. November 2006 05:27 schrieben Sie:
> >
> > OK, i'll try installing kismet on another laptop. For now that's what I
> > have from iwevent:
> >
> > [root@core ~]# cat iwevents.bad
> > 21:30:52.185823 eth1 Set Mode:Managed
> where's Set Encryption key:****-****-****-****-****-****-** Security
> mode:restricted ? was the key set?
>
>
> > 21:30:52.226100 eth1 Set ESSID:"ALCT76_68b"
> > 21:30:54.505039 eth1 Authenticate request to XY [00 0D 0002]
> > 21:30:56.300128 eth1 Authenticate request to XY [00 0D 0002]
> ok, the error code is 0D (=unsupported Authentication Algorithm).
>
> >
> > [root@core ~]# cat iwevents.good
> > 21:50:50.575630 eth1 Set Mode:Managed
> > 21:50:50.604998 eth1 Set Encryption
> > key:****-****-****-****-****-****-** Security mode:restricted
> > 21:50:50.616502 eth1 Set ESSID:"ALCT76_68b"
> > 21:50:52.880361 eth1 Authenticate request to XY : [00 00 0002]
> > 21:50:52.882638 eth1 Associate request to XY : [00 00 0002]
> > 21:50:52.883625 eth1 New Access Point/Cell address:XY
> are your wireless-tools( iwconfig, iwevent, iwlist...) up to date? they've to
> be atleast Version 21!
>
Hmm, something funky is going on with my hotplug scripts - if I rerun
ifup eth1 after inserting the card it associates just fine. Sorry for
the false alarm, the drivers seems to be working fine.
Still not sure why old driver does not need second "ifup"...
--
Dmitry
next prev parent reply other threads:[~2006-11-22 7:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 12:57 [PATCH] prism54: wpa support for fullmac cards chunkeey
2006-10-04 10:38 ` Jiri Benc
2006-10-04 11:40 ` Dan Williams
2006-10-04 14:12 ` chunkeey
2006-10-04 21:43 ` Jouni Malinen
2006-10-05 17:17 ` chunkeey
2006-10-17 21:32 ` John W. Linville
2006-10-29 12:35 ` [PATCH wireless-2.6-git] prism54: WPA/RSN " chunkeey
2006-10-30 8:50 ` Johannes Berg
2006-10-30 20:17 ` Luis R. Rodriguez
2006-10-31 16:05 ` Dan Williams
2006-10-31 17:53 ` chunkeey
2006-11-03 14:49 ` Dan Williams
2006-11-03 16:06 ` Luis R. Rodriguez
2006-11-03 18:12 ` chunkeey
2006-11-03 18:41 ` Luis R. Rodriguez
2006-11-08 0:39 ` John W. Linville
2006-11-09 17:38 ` chunkeey
2006-11-09 23:16 ` Luis R. Rodriguez
2006-11-09 23:16 ` Luis R. Rodriguez
2006-11-10 14:42 ` Dan Williams
2006-11-17 5:42 ` Dmitry Torokhov
2006-11-17 19:43 ` chunkeey
2006-11-17 20:16 ` Dmitry Torokhov
2006-11-17 20:53 ` chunkeey
2006-11-17 21:02 ` Dmitry Torokhov
2006-11-17 21:09 ` Dmitry Torokhov
2006-11-17 21:35 ` chunkeey
2006-11-18 4:27 ` Dmitry Torokhov
2006-11-18 10:18 ` chunkeey
2006-11-22 7:01 ` Dmitry Torokhov [this message]
2006-11-24 15:55 ` chunkeey
[not found] ` <200611250039.03597.dtor@insightbb.com>
2006-11-25 16:50 ` chunkeey
2006-11-26 5:27 ` Dmitry Torokhov
2006-11-26 10:47 ` chunkeey
2006-12-06 1:44 ` John W. Linville
2006-12-06 12:05 ` chunkeey
2006-12-06 14:11 ` Dmitry Torokhov
2006-10-30 20:33 ` Dan Williams
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=200611220201.34717.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=chunkeey@web.de \
--cc=netdev@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).