RDKBWIFI-459: Add Device.WiFi.EM.FailedConnection RBUS event#1167
Open
santhoshg6 wants to merge 2 commits into
Open
RDKBWIFI-459: Add Device.WiFi.EM.FailedConnection RBUS event#1167santhoshg6 wants to merge 2 commits into
santhoshg6 wants to merge 2 commits into
Conversation
Reason for change: When a Wi-Fi client fails to connect due to authentication or association failure (e.g., wrong password, MIC failure, ACL deny), there is no RBUS event to notify upper layers about the failure. This change introduces the Device.WiFi.EM.FailedConnection event that is published on connection failure, carrying the BSSID, station MAC, IEEE 802.11 status code, and reason code as a JSON payload. Test Procedure: 1. WPA3-SAE wrong password — verified event published with status=15 (SAE Challenge Failure), reason=0 2. WPA2-PSK wrong password — verified event published with status=0, reason=14 (MIC Failure) 3. ACL deny (blacklist) — verified event published with status=33 (Unspecified/ACL deny), reason=0 All scenarios validated via RBUS subscriber and packet capture on rdkb-lgm platform. Risks: Low. New RBUS event only; no modification to existing connection or data path logic. No impact on normal association flow. Signed-off-by: sgunasekaran@maxlinear.com
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reason for change:
When a Wi-Fi client fails to connect due to authentication or association failure (e.g., wrong password, MIC failure, ACL deny), there is no RBUS event to notify upper layers about the failure. This change introduces the Device.WiFi.EM.FailedConnection event that is published on connection failure, carrying the BSSID, station MAC, IEEE 802.11 status code, and reason code as a JSON payload.
Test Procedure:
Risks:
Low. New RBUS event only; no modification to existing connection or data path logic. No impact on normal association flow.
Signed-off-by: sgunasekaran@maxlinear.com