From: Bas Hulsken <bhulsken@hotmail.com>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: hostapd with mac80211 and rt2500pci: hostapd doesn't receive clients EAPOL keys unless mon.wlan1 is promiscuous
Date: Wed, 26 Mar 2008 19:51:04 +0100 [thread overview]
Message-ID: <1206557464.2844.3.camel@Bas> (raw)
In-Reply-To: <1206281653.2902.45.camel@Bas>
Hi Johannes,
don't mean to push you or anything, but I was wondering if you
overlooked my last mail. You asked me to add some printk's to the
rt2500pci driver to debug hostapd authentication failure. I did this,
and these are the results:
upon ifupping the interface:
------------------------------------------------
phy0: Selected rate control algorithm 'pid'
Registered led device: rt2500pci-phy0:radio
rt2500pci MAC changed: 00:0c:f6:14:05:19
rt2500pci filter_flags: 2
ADDRCONF(NETDEV_UP): wlan1: link is not ready
------------------------------------------------
when I run hostapd, this is in dmesg:
------------------------------------------------
rt2500pci MAC changed: 00:00:00:00:00:00
rt2500pci MAC changed: 00:0c:f6:14:05:19
rt2500pci MAC changed: 00:00:00:00:00:00
rt2500pci MAC changed: 00:0c:f6:14:05:19
rt2500pci filter_flags: 2
rt2500pci filter_flags: 0
rt2500pci MAC changed: 00:00:00:00:00:00
rt2500pci MAC changed: 00:0c:f6:14:05:19
rt2500pci filter_flags: 2
------------------------------------------------
this is immediately on startup of hostapd, after that filter and MAC
remain unchanged (at least if my printk catches everything).
does this look ok to you? Does it explain why I can only receive EOPOL
keys when in promiscuous mode?
thanks for your help,
Bas
On Sun, 2008-03-23 at 15:14 +0100, Bas Hulsken wrote:
> Hi Johannes,
>
> On Sun, 2008-03-23 at 14:00 +0100, Bas Hulsken wrote:
>
> > before I blow up the system, I guess this should do the trick?
> > (remember, I'm not a kernel hacker ;-):
>
> ok.. so I decided to just give it a try.. seems to work, this is dmesg
> upon ifupping the interface:
>
> phy0: Selected rate control algorithm 'pid'
> Registered led device: rt2500pci-phy0:radio
> rt2500pci MAC changed: 00:0c:f6:14:05:19
> rt2500pci filter_flags: 2
> ADDRCONF(NETDEV_UP): wlan1: link is not ready
>
> when I run hostapd, this is in dmesg:
>
> rt2500pci MAC changed: 00:00:00:00:00:00
> rt2500pci MAC changed: 00:0c:f6:14:05:19
> rt2500pci MAC changed: 00:00:00:00:00:00
> rt2500pci MAC changed: 00:0c:f6:14:05:19
> rt2500pci filter_flags: 2
> rt2500pci filter_flags: 0
> rt2500pci MAC changed: 00:00:00:00:00:00
> rt2500pci MAC changed: 00:0c:f6:14:05:19
> rt2500pci filter_flags: 2
>
> this is immediately on startup of hostapd, after that filter and MAC
> remain unchanged (at least if my printk catches everything).
>
> thanks,
> Bas
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-26 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 11:24 hostapd with mac80211 and rt2500pci: hostapd doesn't receive clients EAPOL keys unless mon.wlan1 is promiscuous Bas Hulsken
2008-03-23 12:12 ` Johannes Berg
2008-03-23 13:00 ` Bas Hulsken
2008-03-23 14:14 ` Bas Hulsken
2008-03-26 18:51 ` Bas Hulsken [this message]
2008-03-27 12:59 ` 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=1206557464.2844.3.camel@Bas \
--to=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).