From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 4/4] dpp: scale PKEX timeout by the number of frequencies used
Date: Tue, 27 Aug 2024 07:21:25 -0700 [thread overview]
Message-ID: <20240827142125.751023-4-prestwoj@gmail.com> (raw)
In-Reply-To: <20240827142125.751023-1-prestwoj@gmail.com>
If the number of frequencies used is very small reduce the timeout
to avoid waiting for extended periods of time.
---
src/dpp.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/dpp.c b/src/dpp.c
index dad74efe..5d56456d 100644
--- a/src/dpp.c
+++ b/src/dpp.c
@@ -59,6 +59,7 @@
#define DPP_FRAME_RETRY_TIMEOUT 1
#define DPP_AUTH_PROTO_TIMEOUT 10
#define DPP_PKEX_PROTO_TIMEOUT 120
+#define DPP_PKEX_PROTO_PER_FREQ_TIMEOUT 10
static uint32_t netdev_watch;
static struct l_genl_family *nl80211;
@@ -4284,7 +4285,8 @@ static void __dpp_pkex_start_enrollee(struct dpp_sm *dpp)
{
dpp->current_freq = dpp->freqs[0];
- dpp_reset_protocol_timer(dpp, DPP_PKEX_PROTO_TIMEOUT);
+ dpp_reset_protocol_timer(dpp,
+ dpp->freqs_len * DPP_PKEX_PROTO_PER_FREQ_TIMEOUT);
l_debug("PKEX start enrollee (id=%s)", dpp->pkex_id ?: "unset");
--
2.34.1
next prev parent reply other threads:[~2024-08-27 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 14:21 [PATCH 1/4] dpp: factor out key derivation and starting PKEX into functions James Prestwood
2024-08-27 14:21 ` [PATCH 2/4] dpp: add Address/Frequency as parameters to PKEX enrollees James Prestwood
2024-08-27 14:21 ` [PATCH 3/4] dpp: allow PKEX configurators to run without multicast RX support James Prestwood
2024-08-27 14:21 ` James Prestwood [this message]
2024-08-28 2:25 ` [PATCH 1/4] dpp: factor out key derivation and starting PKEX into functions 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=20240827142125.751023-4-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