From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH v2 5/9] ft: get OCI prior to reassociation
Date: Tue, 28 Sep 2021 11:03:47 -0500 [thread overview]
Message-ID: <185247c1-67ea-e722-914d-dca6a675ff38@gmail.com> (raw)
In-Reply-To: 20210928154658.2382597-5-prestwoj@gmail.com
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
Hi James,
On 9/28/21 10:46 AM, James Prestwood wrote:
> This modifies the FT logic to fist call get_oci() before
> reassociation. This allows the OCI to be included in reassociation
> and in the 4-way handshake later on.
>
> The code path for getting the OCI had to be slightly changed to
> handle an OCI that is already set. First the handshake chandef is
> NULL'ed out for any new connection. This prevents a stale OCI from
> being used. Then some checks were added for this case in
> netdev_connect_event and if chandef is already set, start the 4-way
> handshake.
> ---
> src/ft.c | 13 ++++++++++++-
> src/ft.h | 2 ++
> src/netdev.c | 29 ++++++++++++++++++++++++++---
> 3 files changed, 40 insertions(+), 4 deletions(-)
>
<snip>
> @@ -3633,6 +3651,8 @@ static void netdev_connect_common(struct netdev *netdev,
> netdev->privacy = bss->capability & IE_BSS_CAP_PRIVACY;
> handshake_state_set_authenticator_address(hs, bss->addr);
>
> + handshake_state_set_chandef(hs, NULL);
> +
> if (!is_rsn)
> goto build_cmd_connect;
>
netdev_connect_common always operates on a brand new handshake, so this should
not be needed. I took this out for now.
Patches 1-8 applied, thanks.
Regards,
-Denis
next reply other threads:[~2021-09-28 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 16:03 Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-28 15:46 [PATCH v2 5/9] ft: get OCI prior to reassociation James Prestwood
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=185247c1-67ea-e722-914d-dca6a675ff38@gmail.com \
--to=iwd@lists.linux.dev \
/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