A stored transmit-power value does not prove that the radio changed output. Trace the setting to an implemented control path, record whether the request was accepted, obtain supported readback and reserve physical-output claims for a suitable measurement. These are separate evidence levels, with different owners and failure modes. This guide pins NetworkManager 1.50.0 and Linux…
A congestion diagnosis needs evidence about access to the channel, not just received signal strength. Align signal observations, transmission outcomes and valid channel-survey intervals, then change one controlled condition. Similar RSSI with different service latency can be consistent with contention, but it does not identify the competing transmitter or rule out endpoint delays. This guide…
Choose a Wi-Fi architecture by tracing the behavior you must change to its effective owner. The labels FullMAC and SoftMAC are useful starting points, but they do not establish that a particular scheduling, rate-control or power-save decision is editable in host code. Hardware and firmware offloads can bypass code that appears to be the obvious…
A radio firmware fault can interrupt Wi-Fi while Linux continues running. Preserve the driver’s fault report and any device coredump promptly, then correlate them with the specific radio incident. A normal host uptime and an empty panic archive do not establish that the radio firmware stayed healthy. This procedure follows Linux 6.12 Intel iwlwifi MVM…
Use Wi-Fi notifications to request reconciliation, not as an infallible history from which current association can always be reconstructed. After event loss, reader restart or an interrupted state query, mark the affected view uncertain and obtain fresh supported state. Never let a delayed callback overwrite a newer observation merely because it was processed last. This…
Retire WPS by qualifying a replacement installation and recovery path for every shipped device cohort before removing the old entry point. Updating the phone app alone cannot give a WPS-only embedded device a different provisioning protocol. The migration decision must include the device firmware, installer platform, access network and the recovery route available after credentials…
Use profile priority to choose among eligible automatic-connection candidates, and define manual selection as a separate product action. A higher-priority network becoming visible does not automatically replace an already active connection in NetworkManager. Without that distinction, an interface can promise “preferred network” while implementing an unexplained mix of current connection, remembered priority and temporary blocking….
A station rejected because the AP cannot admit it should retain its credentials and report an admission problem. Preserve the protocol phase, received status and AP-side resource evidence before deciding that a password is wrong. Even the commonly relevant status 17 is a category of rejection, not proof of one specific capacity limit. This guide…
If downlink data reaches a sleeping client only after it sends something, test whether that uplink is a valid U-APSD trigger and whether the downlink belongs to a delivery-enabled access category. The symptom alone does not prove U-APSD: the uplink may instead change ordinary power state, refresh another network dependency or simply coincide with application…
When a TWT agreement ends or changes, retire every application timer and queue dependency tied to the old agreement. Reconcile the current driver state, then use the product’s supported ordinary-send path or a newly confirmed schedule. Do not leave records waiting forever for a wake notification belonging to an agreement that no longer exists. This…