From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 02/11] eap: Re-send Identity Request on EAPoL-Start
Date: Thu, 27 Aug 2020 13:53:17 -0500 [thread overview]
Message-ID: <0de9dd69-e91c-0b35-5a29-d41f3a0487a2@gmail.com> (raw)
In-Reply-To: <20200827181453.61823-2-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On 8/27/20 1:14 PM, Andrew Zaborowski wrote:
> It looks like clients sometimes miss our unsolicited Identity Request
> and need a resend.
> ---
> src/eap.c | 12 ++++++++++--
> src/eapol.c | 12 ++++++++----
> 2 files changed, 18 insertions(+), 6 deletions(-)
>
Applied.
By the way, there are several implementations (Apple AirPort for example) that
do not start WSC until an EAPoL-Start is sent. I don't recall that EAPoL-Start
behavior was specified in WSC 1.0. I know that one of my routers that uses WSC
2.0 doesn't do this and sends a RequestIdentity right away. So that might
explain what you're seeing here.
Regards,
-Denis
next prev parent reply other threads:[~2020-08-27 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 18:14 [PATCH 01/11] wscutil: Add wsc_build_beacon Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 02/11] eap: Re-send Identity Request on EAPoL-Start Andrew Zaborowski
2020-08-27 18:53 ` Denis Kenzior [this message]
2020-08-27 20:47 ` Andrew Zaborowski
2020-08-27 20:38 ` Denis Kenzior
2020-08-27 23:24 ` Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 03/11] eap-wsc: In WSC-R read UUID-E from settings Andrew Zaborowski
2020-08-27 19:03 ` Denis Kenzior
2020-08-27 18:14 ` [PATCH 04/11] ap: Move AP parameters to a struct Andrew Zaborowski
2020-08-27 19:00 ` Denis Kenzior
2020-08-27 18:14 ` [PATCH 05/11] ap: Drop unused variable Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 06/11] ap: Fix incoming Probe Request BSSID check Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 07/11] ap: Stop ongoing handshake on reassociation Andrew Zaborowski
2020-08-27 19:11 ` Denis Kenzior
2020-08-27 20:40 ` Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 08/11] ap: Push Button mode API and beacon changes Andrew Zaborowski
2020-08-27 19:42 ` Denis Kenzior
2020-08-27 20:57 ` Andrew Zaborowski
2020-08-27 20:51 ` Denis Kenzior
2020-08-27 18:14 ` [PATCH 09/11] ap: WSC Probe Request processing logic Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 10/11] ap: Parse WSC PBC association request and build response Andrew Zaborowski
2020-08-27 18:14 ` [PATCH 11/11] ap: Start EAP-WSC authentication with WSC enrollees Andrew Zaborowski
2020-08-27 19:16 ` [PATCH 01/11] wscutil: Add wsc_build_beacon Denis Kenzior
2020-08-27 23:18 ` Andrew Zaborowski
2020-08-28 0:12 ` Denis Kenzior
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=0de9dd69-e91c-0b35-5a29-d41f3a0487a2@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.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