From: Wolfgang Breyha <wbreyha@gmx.net>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: EAP Identity Response dropped on 5GHz
Date: Thu, 02 Dec 2010 15:24:49 +0100 [thread overview]
Message-ID: <4CF7AC31.2020206@gmx.net> (raw)
In-Reply-To: <4CF66912.8050302@gmx.net>
Wolfgang Breyha wrote, on 01.12.2010 16:26:
> In the same moments I see
>> Dec 1 15:53:18 hpwb kernel: [15439.900071] wlan0: dropped frame to 00:26:cb:xx:xx:xx (unauthorized port)
>> Dec 1 15:53:19 hpwb kernel: [15440.894484] wlan0: dropped frame to 00:26:cb:xx:xx:xx (unauthorized port)
>> Dec 1 15:53:20 hpwb kernel: [15441.893895] wlan0: dropped frame to 00:26:cb:xx:xx:xx (unauthorized port)
These are IPv6 discovery packets of ethertype 0x86DD. So that's correct.
But introducing a usleep(100000) in
wpa_supplicant/src/eap_peer/eap.c:136, or in other words....
> wpa_supplicant logs:
>
>> 1291215721.998646: Process pending EAPOL frame that was received just before association notification
>> 1291215721.998677: RX EAPOL from 00:26:cb:xx:xx:xx
>> 1291215721.998713: Setting authentication timeout: 70 sec 0 usec
>> 1291215721.998747: EAPOL: Received EAP-Packet frame
>> 1291215721.998778: EAPOL: SUPP_PAE entering state RESTART
>> 1291215721.998806: EAP: EAP entering state INITIALIZE
............ HERE ................
>> 1291215721.998835: EAP: EAP entering state IDLE
>> 1291215721.998865: EAPOL: SUPP_PAE entering state AUTHENTICATING
>> 1291215721.998895: EAPOL: SUPP_BE entering state REQUEST
>> 1291215721.998924: EAPOL: getSuppRsp
>> 1291215721.998952: EAP: EAP entering state RECEIVED
>> 1291215721.998998: EAP: Received EAP-Request id=1 method=1 vendor=0 vendorMethod=0
>> 1291215721.999034: EAP: EAP entering state IDENTITY
>> 1291215721.999065: CTRL-EVENT-EAP-STARTED EAP authentication started
>> 1291215721.999087: EAP: EAP-Request Identity data - hexdump_ascii(len=40):
>> 1291215721.999159: EAP: using real identity - hexdump_ascii(len=15):
>> 1291215721.999198: EAP: EAP entering state SEND_RESPONSE
>> 1291215721.999220: EAP: EAP entering state IDLE
>> 1291215721.999267: EAPOL: SUPP_BE entering state RESPONSE
>> 1291215721.999290: EAPOL: txSuppRsp
>> 1291215721.999318: TX EAPOL: dst=00:26:cb:xx:xx:xx
.... lets path this packet through to the AP over air.
I haven't found the source of this race condition which causes this. The
reason why it only happens on 5GHz channels is unknown as well.
With kind regards,
Wolfgang Breyha
--
Wolfgang Breyha <wbreyha@gmx.net> | http://www.blafasel.at/
Vienna University Computer Center | Austria
next prev parent reply other threads:[~2010-12-02 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 15:26 EAP Identity Response dropped on 5GHz Wolfgang Breyha
2010-12-02 14:24 ` Wolfgang Breyha [this message]
2010-12-02 23:32 ` Eliad Peller
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=4CF7AC31.2020206@gmx.net \
--to=wbreyha@gmx.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).