wifi: Hostap prepare upmerge #11899

Modifications for building supplicant on Zephyr RTOS. Signed-off-by: Sridhar Nuvusetty <sridhar.nuvusetty@nordicsemi.no> Signed-off-by: Sachin Kulkarni <sachin.kulkarni@nordicsemi.no> Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no> Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Co-authored-by: krishna T <krishna.t@nordicsemi.no>

The file was removed but was still included. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Remove uninitialized variable that is no longer needed, this causes crash in case supplicant thread exits. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

* Include HOSTAP_BASE to fix header file paths * Select WEP automatically through Kconfig Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

1. Add WPA_SUPP_LOG_LEVEL_* Kconfig options to control the WPA supplicant log level the same way as other SDK components. 2. Add WPA_SUPP_DEBUG_LEVEL Kconfig option to be used for compile-time filtering of WPA supplicant debug messages. By default, it is aligned with WPA_SUPP_LOG_LEVEL. 3. Implement Zephyr variants of wpa_debug.h and wpa_debug.c files that use Zephyr logging subystem as the default output and apply compile-time filtering for the messages. Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>

Eloop framework in wpa_supplicant uses select with minimal timeout of all registered users, but by default it is 10secs (periodic cleanup task), so, in case of no other events all registered users will be delayed by 10secs. In Linux, select exits without waiting for full 10secs as for there is a handler registered for NL80211 sockets and whenever there is a event from Kernel select exits and processes expired events immediately. In Zephyr, we don't have such mechanism as we use direction function calls between kernel and wpa_supplicant, so, add an event socket and register it with Eloop and use this to post the event, the socket handler pass the event to wpa_supplicant. For user interface we just post a dummy message only to unblock select. This solves both problems: * Unblocking select for all interesting events immediately * Terminate driver context for events as we use sockets, so, remove mbox + thread. This significantly improves the association time from 30s to 5s. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Using first interface handle everywhere is not ideal, esp. when we add support for multi-VIF, so, query wpa_supplicant with the interface name to get the handle. The interface name itself is hard coded to "wlan0" everywhere for now. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These APIs will be used by nRF Wi-Fi management to interact with wpa_supplicant. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

This is now purely an internal utility, so, moved from sdk-nrf to here as it works with wpa_supplicant. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Now that display scan is natively supported using wifi_mgmt, remove it from WPA supplicant API and wpa_cli. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Using UDP sockets need an interface with properly configured IP address and then either IPv4/IPv6 enabled, UNIX socket don't need any of those and work perfectly well for IPC. This solves two bugs: * Matter doesn't enable IPv4, so, the events stop working, as the code doesn't support IPv6 sockets and also doesn't protect with IPv4 define. * Wi-Fi sample assigns IP address in the `prj.conf` but if an application doesn't do that, then socket send fails. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

With recent changes, WPA CLI build is broken. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

All options depend on WPA_SUPP, so, add a check. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Don't use the same acronym in help. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Free ifname before returning. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

ifname can be null if memory allocation fails. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Add support to handle signal polling requests from application. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Before processing wifi_mgmt APIs check and wait for WPA supplicant initialization. This solves bus fault when wifi_mgmt API is called too early (before WPA supplicant populates "global" pointer). This is done using a binary semaphore with initial value as 1. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

When both API and Shell commands are invoked, crashes were observed due to missing locking and using stack memory to pass down to the driver. Use a lock to serialize all APIs, both when invoked from using API directly or viz shell and also calling multiple APIs, and for status use the dynamic memory to avoid passing stack memory when there is concurrent access. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If a channel is provided pass it WPA supplicant to use that in both scan and connection. The conversion from channel to frequency without any regulatory information (country code, OP class) is tricky, but use Global with widest OP classes common to most countries (81 and 128). Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

MBO is multi-band operation, this is needed for WFA certification for Wi-Fi 6. Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

* Debug logging is excessive and needs larger buffer size to avoid truncating/dropping logs * Also, in general supplicant outputs bunch of logs, so, even for non-debug case increase the buffer size Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In case of failure scenarions, mutex is not unlocked causing next command to block forever (shell thread is blocked). Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

MbedTLS is only used by sdk-hostap, choose the necessary Kconfig options by default instead of relying on samples. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Zephyr has deprecated including "zephyr" directory in includes, so, all references should mandatory use "zephyr" prefix. Also, reordered the include groups. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If a connect has been issued before the first connect timeout/success, then there is a deadlock as connect API holds the mutex but calls the connect status worker which tries to get mutex. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If we get a new connection request, gracefully terminate it by sending a failure event before starting tracking of the new connection status. This also avoid a case where old work is rescheduled even though its cancelled successfully. Also, return a different status for this termination. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is an internal header file. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Now that nRF Wi-Fi management is merged with Zephyr's Wi-Fi management, use Zephyr's Wi-Fi management. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Support for handling MLME frames. Enable RRM support in capabilities. Support for wnm_bss_query wpa_cli cmd. Signed-off-by: Sridhar Nuvusetty <sridhar.nuvusetty@nordicsemi.no>

When 802.15.4 is enabled the link address is 8, but we only allocate 6 bytes on stack causing buffer overflow. Use proper macro for the link address length and also add a length check just in case. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Now that Zephyr supports taking PMF setting from the user, use that instead of hard-coding to optional. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Whenever a connection/disconnection is requested, a terminated event is sent first always before sending the result event. Fix to send terminate event only if a second connection/disconnection is requested. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If a 802.15.4 interface is present, then this is expected and not an error, so, just silently ignore. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If we enable OpenThread then these are disabled by default, so, enable them explicitly. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

* Since the supp_shell_connect_status is called (queued) recursively the counter of connection retries (with second interval) needs to persist between consecutive calls. Without this change the supplicant retries to connect to the AP endlessly. * Also got rid of some magic numbers. Signed-off-by: Marcin Kajor <marcin.kajor@nordicsemi.no>

When the connection timeout was 0 the code would always fail the connection. Change the condition to handle the timeout only if it is positive. By the way, simplify the conditions and unlock the mutex after modifying the shared variable. Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>

Add checks to read and print the link mode correctly. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Useful to know the network status. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These are needed for LED support for STA sample to track WPA supplicant connection state changes and blink LEDs. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Allow connect only if interface is up. Signed-off-by: Sridhar Nuvusetty <sridhar.nuvusetty@nordicsemi.no> Signed-off-by: Sachin D Kulkarni <sachin.kulkarni@nordicsemi.no>

This is needed for automated software maturity. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Now that WPA supplicant sends events to Zephyr directly to handle AP initiated (dis)connection events, remove sending the events from Wi-Fi management wrapper to avoid sending duplicate events. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Use z_wpa_supplicant as the name space instead of zephyr_supp. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In Linux WPA CLI is a standalone application that uses sockets to communicate with ctrl_iface (uses Eloop), in Zephyr we have replaced sockets with direct function calls, but this introduces concurrency as we don't go through Eloop which causes instability and crashes esp. in the deinitialization path. Implement Zephyr's version of WPA CLI and control interface using socketpair UNIX style sockets, here WPA CLI can be invoked as a standard function rather than an executable. To avoid code duplication move all commands processing to a separate file that can be used by wpa_cli application and also wpa_cli_zephyr library (all other changes to wpa_cli are restored). Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Instead of exposing limited commands using wrappers add a generic pass through WPA CLI that can take any command supported by WPA CLI. Only downside is we lose the help for each command in shell, but as this is only for internal use (WFA certification) this is not a constraint. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Directly calling WPA supplicant APIs is error prone as it introduces concurrency, so, use WPA CLI interface to serialize them using control interface and Eloop. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This was a typo but as its in the string for WPA CLI, went undetected. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

If a sample doesn't use POSIX_API then the default POSIX_MAX_FDS are 4, but Zephyr's WPA supplicant needs at least 7, so, fix this by explicitly defining it. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This needs CONFIG_POSIX_API and now that we have moved to use wpa_cli_zephyr this is no longer required. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Use "z_wpas_" as the prefix for all internal functions to disambiduate between wpa_supplicant APIs. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Using the network management events from the driver dynamically add/remove interfaces to the WPA supplicant, this ensures a better integration of driver and WPA supplicant rather than WPA supplicant assuming interface is administratively up. Default behaviour now would be for the interface to be administratively up but operationally down till the WPA supplicant associates and then interface will be operationally up. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

When switching to control interface, the code to configure channel from user to WPA supplicant has been removed, use the control interface to configure the channel. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This was missed in cleaning up old interface. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

All these WPA cli command invocations need to be checked for return value to catch issues early. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

* Check for security instead of assuming psk means security (Handy in test for switching b/w PSK and None). * Use Enums and remove comments. * Specifically check for PSK. * Throw error if not matching any. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Now that we are using control interface as the primary communications this is applicable for all. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This was checked in by mistake. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This is needed esp. for "wifi status" as that makes a call all the way to Driver, and if its called from network management thread then more stack is needed. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

EK support is still experimental. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

The minimum requirement for WPA supplicant is 4. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

In case multiple threads use this to post events to WPA supplicant. Signed-off-by: Krishna T <krishna.t@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is now obsolete as we implement full fledged control interface. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

For handling interface events they need to go through global control interface. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Spelling mistake. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This disables all further processing in the WPA supplicant before we remove the interface. Also, add a check after interface add/remove to make sure it worked before proceeding ahead. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In case of failure set return value to avoid doing further work. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These are mainly for debugging, so, use DEBUG macro. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is now fully supported. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Remove unused variable. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Always scan for SSID's to handle hidden SSID case. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These are currently unused in hostap, but conflict with Zephyr's implementation (duplicate function), revisit when this is actually used as the function signatures b/w hostap and Zephyr are different. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Remove non-essential boot log messages. Signed-off-by: Sachin D Kulkarni <sachin.kulkarni@nordicsemi.no>

With upstream commit [1] when CONFIG_POSIX_API is enabled then Zephyr's header are included before the `libc` headers causing issues as Zephyr doesn't support POSIX signal implementation. Resolve this by not using POSIX_API and add a negative dependency. [1] - zephyrproject-rtos/zephyr@43110dd Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Without this the build fails, so, should be selected automatically rather than relying on the application. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This is a common modules used by P2P, WPA3 and Enterprise, so, it needs to be enabled with a custom config to avoid re-definitions. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

WPA3 also needs to enable PMKSA caching, though the file is included but the define (IEEE8021X_EAPOL) is not passed. Due to code size (text) increase when WPA_SUPP_EAPOL is enabled, this feature is not enabled by default. If required this can be enabled explicitly by application. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Read beacon interval and DTIM period as part of Wi-Fi status. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Commit 044ed05fe11cc2e59e1e915dc6fadcdde6bf0820 ("Make WPA CLI as passthrough") made this SYS_INIT() a no-op. It's breaking the build now that SYS_INIT function signatures are 'int callback(void)'. Remove it entirely since it does nothing. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>

While fetching connection info as part of processing the interface status command, if error is returned by driver, set the params to 0 and reset the return value, so that other params are not ignored by the caller. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

When copying event from driver and postnig to WPA supplicant, the IE's are not copied, so, if WPA supplicant takes longer to process the event the driver frees the IEs causing invalid data to be processed by WPA supplicant. This is a common issue to all events. For now Authentication events are being affected due to WPA3-SAE taking longer to process, so, fix only Authentication events for now as a generic fix needs more work and thought. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Commit f13d1c9 ("nrf_security: Remove usage of HEAP in platform.c") broke Wi-Fi security as MbedTLS calloc/free are now undefined and any allocations by MbedTLS will fail resulting in crypto failures. Fix this by setting alternatives to stdlib variants. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

These were added implicitly by Zephyr, but for NS build we need to explicitly add these. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

This was missed and is needed to compile with NS image. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

* Add TLS none * Enable PBKDF2 in WPA supplicant Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

In order to get nRF7002 NS build going, we need to use PSA MbedTLS template to get entropy working. Rather than having a single set of options which makes dependency management tough, have a separate entry for PSA based MbedTLS which is enabled by for NS variants only. Also, don't use MbedTLS APIs for entropy, instead use the Zephyr APIs that can work for both NS and S builds. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Update peer TWT capability from connection info. Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

This is important for applications relying on WPA supplicant being disconnected after the call to disconnect. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

ACK the disconnect command with disconnect complete. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Raise connection timed out event to net management queue. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Previously for some reason we have removed logs as they were causing issues, but that is not true anymore. So, add back all error logs. Signed-off-by: Krishna T <krishna.t@nordicsemi.no>

Use the pattern matching on interface names to filter only Wi-Fi interfaces. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Remove remnants of mbedtls entropy usage. Entropy is now accessed through zephyr APIs so enabling MBEDTLS_ENTROPY_C is no longer needed. Without MBEDTLS_ENTROPY_C option there is no reason to change the default configuration value of MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG. NCSDK-22096 Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>

Generate supplicant ready event once the control connection between cli and supplicant is setup. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

This significantly saves flash size that is much needed for Matter apps. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Key mgmt value being passed to wpas_key_mgmt_to_zephyr is the combination (bitwise OR) of all configured security modes for an SSID while the expected input is the security mode negotiated for the association. This results in wpas_key_mgmt_to_zephyr failing to identify correct security mode and falling through to the default case (UNKNOWN). Security mode which is being used by the current association is stored in supplicant interface structure. Refer to this(struct wpa_supplicant) instead of network configuration data (struct wpa_ssid), for reading security mode. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Free the memory once its done. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Register WPA supplicant as a Wi-Fi network manager. Also fix a memory leak while handling the error patch in remove interface. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Divide them cleanly in to private and public. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These ops are not implemented by the WPA supplicant and too much of a hassle to implement a pass through all the way to the driver, so, we use the offloaded APIs registered by the driver and make direct calls. Though offloaded APIs are are registered as long as the interface is managed by the WPA supplicant, Wi-Fi management will not invoke them directly. But if WPA supplicant is disabled (Scan only mode), then Wi-Fi management invokes them directly. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Add support for newly added scan parameters structure handling. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is not a user configuration option and is automatically selected by CONFIG_WPS, hence no CONFIG_ prefix. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

As per 802.11-2020: 11.21.13 BSS max idle period management "If dot11WirelessManagementImplemented is true, dot11BSSMaxIdlePeriod is nonzero and dot11BSSMaxIdlePeriodIndicationByNonAPSTA is true, then a non-S1G non-AP STA shall include a BSS Max Idle Period element in the (Re)Association Request frame. If the BSS Max Idle Period element is present in the (Re)Association Request frame received by a non-S1G AP that has dot11BSSMaxIdlePeriodIndicationByNonAPSTA equal to true, then the non-S1G AP may choose the non-AP STA’s preferred maximum idle period. The non-S1G AP indicates its chosen value to the non-S1G STA in the (Re)Association Response frame." Add BSS max idle timeout (default 300s) in association request. Use CONFIG_BSS_MAX_IDLE_TIME to modify this timeout at build time. Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no> Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Fix PSA dependency on random number support. Random number generated is wanted, instead of a specific PRNG algorithm. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>

…port Enable the PSA key type which enables AES block cipher support. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>

Include hostap module files. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This snapshot tag is taken before the force push to re-write history to include nrf sauce tags as per [1], this will be over-written with the force pushed commit in subsequent commits, see [2] for details. [1] - https://nordicsemi.atlassian.net/wiki/spaces/NCS/pages/108201225/Pull+Requests [2] - https://nordicsemi.atlassian.net/wiki/spaces/NCS/pages/108233364/Synchronization#Synchronization-RebasingOSStrees Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This moves the Zephyr only code to sdk-nrf, and keeps Zephyr changes part of OSS in sdk-hostap in preparation for upmerge. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This code was never run through checkpatch, so, fix the compliance. Also, Zephyr wpa_cli relies on macro with flow control, so, add an exception to checkpatch. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This wasn't caught till now as there was no CI in sdk-hostap. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

wifi: Hostap prepare upmerge #11899

wifi: Hostap prepare upmerge #11899

Commits on Aug 1, 2023