Skip to content

Conversation

@ajayparida
Copy link
Contributor

Changes to set keep alive early scdule duration.

Introduced a configurable parameter to set the time offset (in ms) for scheduling Wi-Fi keep-alive frames earlier than the BSS max idle timeout advertised by the AP. This allows better compatibility with devices that may experience delays due to scheduling or processing. Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
Add a snippet for Wi-Fi keep alive schedule early offset setting. This will set the keep alive early schedule duration. Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
Pull keep-alive early schedule changes. Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>
@github-actions
Copy link

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
hostap zephyrproject-rtos/hostap@e942f86 zephyrproject-rtos/hostap#96 zephyrproject-rtos/hostap#96/files

DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@github-actions github-actions bot added manifest manifest-hostap DNM (manifest) This PR should not be merged (controlled by action-manifest) labels Jul 25, 2025
@@ -0,0 +1 @@
CONFIG_WIFI_NM_WPA_SUPPLICANT_KEEP_ALIVE_EARLY_MS=700
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need a snippet with just single config?

Comment on lines +642 to +651
config WIFI_NM_WPA_SUPPLICANT_KEEP_ALIVE_EARLY_MS
int "Select Wi-Fi keep-alive advance timing (ms before max idle timeout)"
range 100 1000
default 100
help
The supplicant schedules the keep-alive timer 100 ms prior to the BSS
Max Idle time specified by the AP. This offset is currently fixed. However,
due to scheduling and processing delays, some devices may require additional
time to transmit the packet. Introducing a configurable option to schedule
the keep-alive earlier would provide better flexibility for such cases.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
config WIFI_NM_WPA_SUPPLICANT_KEEP_ALIVE_EARLY_MS
int "Select Wi-Fi keep-alive advance timing (ms before max idle timeout)"
range 100 1000
default 100
help
The supplicant schedules the keep-alive timer 100 ms prior to the BSS
Max Idle time specified by the AP. This offset is currently fixed. However,
due to scheduling and processing delays, some devices may require additional
time to transmit the packet. Introducing a configurable option to schedule
the keep-alive earlier would provide better flexibility for such cases.
config WIFI_KEEP_ALIVE_TRANSMISSION_GRACE_PERIOD_MS
int "Wi-Fi Keep-Alive Grace Period (ms)"
range 100 1000
default 100
help
This setting tells your device how many milliseconds (ms) before the
Access Point's (AP) maximum idle timeout it should attempt to send a
Wi-Fi keep-alive packet.
The main reason for this **grace period** is to build in extra time
for your device's internal processes. If there are delays in getting
the keep-alive frame ready and out the door, it could end up being
sent *after* the AP's timeout, causing your connection to drop.
Increasing this value helps ensure the packet is sent well in
@ajayparida ajayparida closed this Jul 25, 2025
@ajayparida
Copy link
Contributor Author

There will be new PR for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Build System area: Wi-Fi Wi-Fi DNM (manifest) This PR should not be merged (controlled by action-manifest) manifest manifest-hostap

4 participants