From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH 1/5] eapol: IP Allocation KDE support
Date: Mon, 14 Sep 2020 11:46:16 -0500 [thread overview]
Message-ID: <7fc7ee8b-fa8a-024f-dbed-3e4343a0ce5f@gmail.com> (raw)
In-Reply-To: <20200914135120.463623-1-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Hi Andrew,
On 9/14/20 8:51 AM, Andrew Zaborowski wrote:
> Support IP allocation during the 4-Way Handshake as defined in the P2P
> spec. This is the supplicant side implementation.
>
> The API requires the user to set hs->support_ip_allocation true before
> eapol_start(). On HANDSHAKE_EVENT_COMPLETE, if this same flag is still
> set, we've received the IP lease, the netmask and the authenticator's
> IP from the authenticator and there's no need to start DHCP. If the
> flag is cleared, the user needs to use DHCP.
> ---
> I can split this into two flags if preferred.
> ---
> src/eapol.c | 76 +++++++++++++++++++++++++++++++++++++++++++------
> src/handshake.h | 9 +++++-
> 2 files changed, 76 insertions(+), 9 deletions(-)
>
Patches 1-3, 5 applied. 4 Doesn't apply.
Regards,
-Denis
prev parent reply other threads:[~2020-09-14 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 13:51 [PATCH 1/5] eapol: IP Allocation KDE support Andrew Zaborowski
2020-09-14 13:51 ` [PATCH 2/5] eapol: IP Allocation KDE support authenticator side Andrew Zaborowski
2020-09-14 13:51 ` [PATCH 3/5] netconfig: Don't bswap IP netmasks for __builtin_popcountl Andrew Zaborowski
2020-09-14 13:51 ` [PATCH 4/5] p2p: Try IP allocation during 4-Way handshake on client Andrew Zaborowski
2020-09-14 13:51 ` [PATCH 5/5] unit: Add two EAPOL IP allocation scenarios Andrew Zaborowski
2020-09-14 16:46 ` Denis Kenzior [this message]
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=7fc7ee8b-fa8a-024f-dbed-3e4343a0ce5f@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 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.