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: Fri, 17 Nov 2006 23:27:48 -0500 [thread overview]
Message-ID: <200611172327.49477.dtor@insightbb.com> (raw)
In-Reply-To: <200611172153.50278.chunkeey@web.de>
On Friday 17 November 2006 15:53, chunkeey@web.de wrote:
> >
> > The card is WG511 talking to netgear WGR614 router. I am using WEP128
> > with shared keys. Router is set to be "g" only. The OS is Fedora Core
> > 3 (I swear I will upgrade :) ), just recompiled wireless tools from
> > sources in FC6.
> >
> > > for debugging:
> > > dmesg & iwevent output would be nice...
> >
> > Will do when I get home.
> >
> > > but I'll accept a short "sniffer" extract too. ;)
> > >
> > > (it would be really good, if you can provide a package dump form a
> > > working setup with the old driver too!)
> >
> > You'd have to tell me exactly what you want me to do.
> just the Management Frames (MLME):
> Beacon, Authentication and Association Responses/Requests Frames
> you can capture these frames with an extra sniffer card (in monitor mode)
> just run tcpdump, wireshark(ethereal), kismet, ...
>
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
21:30:52.226100 eth1 Set ESSID:"ALCT76_68b"
21:30:54.505039 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:30:56.300128 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:30:58.095251 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:11.413225 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:13.207322 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:15.003497 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:16.798687 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:18.593844 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:31.911710 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:33.705200 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:35.501650 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:37.296756 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:39.091866 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:52.409596 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
21:31:54.203281 eth1 Custom driver event:Authenticate request to 00:0f:b5:5b:fe:3a [00 0D 0002]
[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 Custom driver event:Authenticate request to 00:0F:B5:5B:FE:3A : ACCEPTED (00)
21:50:52.882638 eth1 Custom driver event:Associate request to 00:0F:B5:5B:FE:3A : ACCEPTED (00)
21:50:52.883625 eth1 New Access Point/Cell address:00:0F:B5:5B:FE:3A
>
> >
> > The reason for me trying the patch is that the card locks up
> > frequently (the amber transmission light turns on stays this way).
>
> Do you get any fancy "mgt timeout ..." or something in dmesg, when
> the cards locks up? (include one, if you can, maybe syslog "saved" one)
>
No, just netdev watchdog bitches:
Nov 16 23:15:30 core kernel: [164606.712000] NETDEV WATCHDOG: eth1: transmit timed out
Nov 16 23:15:30 core kernel: [164606.712000] eth1: tx_timeout, scheduling a reset
Nov 16 23:15:30 core kernel: [164606.712000] eth1: resetting device...
Nov 16 23:15:30 core kernel: [164606.712000] eth1: uploading firmware...
Nov 16 23:15:31 core kernel: [164606.996000] eth1: firmware version: 1.0.4.3
Nov 16 23:15:31 core kernel: [164606.996000] eth1: firmware upload complete
Nov 16 23:15:31 core kernel: [164607.232000] eth1: interface reset complete
--
Dmitry
next prev parent reply other threads:[~2006-11-18 4:27 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 [this message]
2006-11-18 10:18 ` chunkeey
2006-11-22 7:01 ` Dmitry Torokhov
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=200611172327.49477.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.