[WiFi][Windows Driver][NetAdaptorCx] Media state un-operational after successful connection in open security

Question

Hi,

We are currently bringing up a Wi-Fi driver for Windows 11. At this stage, we have successfully implemented Wi-Fi scanning, and the scan results are visible in the Windows UI. We are also able to successfully connect to an open (unsecured) Wi-Fi network.

However, after the connection is established, the adapter does not become operational. Running ipconfig /all shows that the media state is un-operational, even though the connection process appears to complete successfully.

From the NetAdapterCx side, we have already implemented the following:

• NetAdapter creation and startup using NetAdapterCx.

TX and RX queue creation with all required queue callbacks (Start, Advance, Stop, Cancel, Cleanup, Notification Enabled).

Adapter capabilities including MTU, maximum frame size, link capabilities, MAC address, and receive filters.

• Link state handling using NetAdapterSetLinkState().

WDI control path implementation for Scan, Connect, Disconnect, Reset, and Radio State operations. Scan completes successfully, association succeeds, and the expected WDI indications are generated.

Firmware successfully completes open authentication and association, and Windows reports the WLAN state as Connected.

We also see that NetTxQueueNotifyMoreCompletedPacketsAvailable() and NetRxQueueNotifyMoreReceivedPacketsAvailable() are not yet being called.

During testing, we observe the following:

WLAN state: Connected

MediaConnectionState: Connected

InterfaceOperationalStatus: Dormant (5)

OperationalStatusDownInterfacePaused: True

ipconfig /all reports Media State: Media un-operational

Static IPv4 address remains in the Tentative state.

Given that the connection workflow completes successfully and NetAdapterSetLinkState() is called with the Connected state, is there any additional NetAdapterCx requirement that could cause the interface to remain in the Dormant/Media un-operational state? Is there anything else that must be implemented before Windows considers the adapter fully operational?