From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v2 0/9] Reassoc/FT roaming unification
Date: Wed, 6 Dec 2023 07:06:59 -0800 [thread overview]
Message-ID: <20231206150708.2080336-1-prestwoj@gmail.com> (raw)
Intead of adding a layer of abstraction through ft.c I instead just
added netdev_ft_reassociate. I chose not to reuse netdev_reassociate
due to its handling of soft/fullmac cards, new vs existing handshake
object, and its use of CMD_CONNECT vs CMD_ASSOCIATE. The added logic
seemed too complex.
Side note, we probably need to look into abandoning CMD_CONNECT for
reassociation as the kernel _still_ sends an Authenticate frame when
it shouldn't. Maybe at that point we could merge netdev_ft_reassociate
and netdev_reassociate, but for now this patch set fixes the issue at
hand.
James Prestwood (9):
auto-t: add explicit stop() to IWD class
auto-t: add association timeout test
auto-t: only call set_value for changed values in default()
ft: add FTE/RSNE building to ft_prepare_handshake
ft: add ft_handshake_setup
netdev: add netdev_ft_reassociate
station: use netdev_ft_reassociate
ft: remove ft_associate and helpers
netdev: station: remove NETDEV_EVENT_FT_ROAMED
autotests/testPSK-roam/failed_roam_test.py | 56 ++++--
autotests/util/hostapd.py | 9 +-
autotests/util/iwd.py | 4 +
src/ft.c | 222 ++++++++-------------
src/ft.h | 4 +-
src/netdev.c | 44 ++--
src/netdev.h | 6 +-
src/station.c | 20 +-
8 files changed, 183 insertions(+), 182 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-06 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 15:06 James Prestwood [this message]
2023-12-06 15:07 ` [PATCH v2 1/9] auto-t: add explicit stop() to IWD class James Prestwood
2023-12-06 15:07 ` [PATCH v2 2/9] auto-t: add association timeout test James Prestwood
2023-12-06 15:07 ` [PATCH v2 3/9] auto-t: only call set_value for changed values in default() James Prestwood
2023-12-06 15:07 ` [PATCH v2 4/9] ft: add FTE/RSNE building to ft_prepare_handshake James Prestwood
2023-12-06 16:36 ` Denis Kenzior
2023-12-06 17:08 ` James Prestwood
2023-12-06 17:14 ` Denis Kenzior
2023-12-06 17:59 ` James Prestwood
2023-12-06 15:07 ` [PATCH v2 5/9] ft: add ft_handshake_setup James Prestwood
2023-12-06 16:38 ` Denis Kenzior
2023-12-06 16:46 ` James Prestwood
2023-12-06 15:07 ` [PATCH v2 6/9] netdev: add netdev_ft_reassociate James Prestwood
2023-12-06 16:40 ` Denis Kenzior
2023-12-06 16:49 ` James Prestwood
2023-12-06 15:07 ` [PATCH v2 7/9] station: use netdev_ft_reassociate James Prestwood
2023-12-06 15:07 ` [PATCH v2 8/9] ft: remove ft_associate and helpers James Prestwood
2023-12-06 15:07 ` [PATCH v2 9/9] netdev: station: remove NETDEV_EVENT_FT_ROAMED 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=20231206150708.2080336-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=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