linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Bas Hulsken <bhulsken@hotmail.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: rt2500pci, infinite calls to rt2x00mc_configure_filter
Date: Sat, 29 Mar 2008 18:01:16 +0100	[thread overview]
Message-ID: <200803291801.17068.IvDoorn@gmail.com> (raw)
In-Reply-To: <1206808941.22448.22.camel@Bas>

Hi,

> --------------------------------------------------------------------
> this repeats for a while, all the time giving EAPOL-Key timeout
> messages. tetherial -i mon.wlan1 on the hostapd machine shows that no
> EAPOL key's are received, while tetherial on the laptop shows that they
> are being sent.

Could you enable debugfs and use the tools here:
http://www-user.rhrk.uni-kl.de/~nissler/rt2x00/index.html

To create a dump of the frames as they are actually send out from the driver
to the hardware including the status report. This will tell if rt2x00 is actually
bringing the frame to the hardware correctly.

> this is the flag status when running hostapd; as printed with
> printk(KERN_INFO "rt2500pci filter_flags: %d\n",
> rt2x00dev->packet_filter);
> 
> rt2500pci filter_flags: 2
> rt2500pci MAC changed: 00:0c:f6:14:05:19

Packet filter flags of 2 sounds a bit restrictive.

Johannes, for Master mode shouldn't the following flags be set as well:
FIF_PROMISC_IN_BSS
FIF_CONTROL

Or should the driver enable those automatically when master mode is enabled?

> IEEE 802.1X: 125 bytes from 00:1b:77:a4:db:26
>    IEEE 802.1X: version=1 type=3 length=121
> wlan1: STA 00:1b:77:a4:db:26 WPA: received EAPOL-Key frame (2/4
> Pairwise)
> WPA: 00:1b:77:a4:db:26 WPA_PTK entering state PTKCALCNEGOTIATING
> WPA: PTK derivation - A1=00:0c:f6:14:05:19 A2=00:1b:77:a4:db:26
> WPA: PMK - hexdump(len=32): [REMOVED]
> WPA: PTK - hexdump(len=64): [REMOVED]
> WPA: 00:1b:77:a4:db:26 WPA_PTK entering state PTKCALCNEGOTIATING2
> WPA: 00:1b:77:a4:db:26 WPA_PTK entering state PTKINITNEGOTIATING
> --------------------------------------------------------------------

I'm not sure what is happening here...

Ivo

  reply	other threads:[~2008-03-29 17:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 14:34 rt2500pci, infinite calls to rt2x00mc_configure_filter Bas Hulsken
2008-03-29 14:53 ` Ivo van Doorn
2008-03-29 16:42   ` Bas Hulsken
2008-03-29 17:01     ` Ivo van Doorn [this message]
2008-03-29 23:45       ` Adam Baker
2008-03-30 13:15         ` Bas Hulsken
2008-03-30 13:27           ` Ivo van Doorn
2008-03-30 16:32             ` Bas Hulsken
2008-03-30 16:49               ` Mattias Nissler
2008-03-31 12:01       ` Johannes Berg
2008-03-31 12:51         ` Ivo van Doorn
2008-03-31 12:56           ` Johannes Berg

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=200803291801.17068.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=bhulsken@hotmail.com \
    --cc=johannes@sipsolutions.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).