RDKBWIFI-278: CLIENT ASSOC CTRL REQUEST#926
Merged
narendradandu merged 3 commits intordkcentral:developfrom Apr 21, 2026
Merged
RDKBWIFI-278: CLIENT ASSOC CTRL REQUEST#926narendradandu merged 3 commits intordkcentral:developfrom
narendradandu merged 3 commits intordkcentral:developfrom
Conversation
sundram0711
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
b31e3de to
1c5dab9
Compare
github-actions
Bot
added
the
community contribution
sundram0711
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
4 times, most recently
from
8ab3213 to
b07a543
Compare
amarnathhullur
requested changes
Mar 23, 2026
sundram0711
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
b07a543 to
eb55006
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Implements EasyMesh “Client Assoc Ctrl Request” handling in the EM agent to block/unblock a station on a specific BSSID using the ACL mechanism, with optional expiry via a timer callback.
Changes:
- Adds a new EM bus namespace for
Device.WiFi.EM.ClientAssocCtrlRequest. - Introduces a new request payload type (
client_assoc_ctrl_req_t) for association control parameters. - Adds an EM event handler that updates ACL entries and schedules timed ACL removal.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 14 comments.
| File | Description |
|---|---|
| source/apps/em/wifi_em.h | Adds the new bus namespace string for the client association control request. |
| source/apps/em/wifi_em.c | Adds the ACL timer callback, event handler logic, and registers the new bus event in em_init(). |
| include/wifi_base.h | Adds the client_assoc_ctrl_req_t request structure used as the bytes payload. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
sundram0711
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
12 times, most recently
from
f70d64d to
d2ca27c
Compare
amarnathhullur
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
d2ca27c to
b339695
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
|
Internal builds verified by https://gerrit.teamccp.com/#/c/952530/ |
amarnathhullur
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
b339695 to
71cf376
Compare
amarnathhullur
requested changes
Apr 3, 2026
sundram0711
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
3 times, most recently
from
52d2a31 to
97621ef
Compare
amarnathhullur
approved these changes
Apr 8, 2026
amarnathhullur
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
97621ef to
a4a305c
Compare
Implement client association control request handling on a per-station basis. The agent receives and processes the request, forwarding it from the agent to OneWiFi and then to rdk-wifi-hal to block or unblock clients using the ACL mechanism. Unit Testing: Triggered the association control request from the controller using rdkb-cli. Added a temporary handler in main.go and invoked it via a curl command. Note: EasyMesh(rdkb-cli) currently supports processing this command only for connected clients. Test Results: When the controller sends a request to block a connected client on a specific BSSID for a defined duration, the client is added to the ACL for that BSSID. If the client disconnects and attempts to reconnect, it is denied access to the same BSSID. When blocked on the 5GHz BSSID, the client was still able to connect to the 2.4GHz BSSID. After blocking the client on both 5GHz and 2.4GHz BSSIDs, the client was unable to connect until the validity timer expired. Signed-off-by: Sundram Patel <Sundram.p@tataelxsi.co.in>
amarnathhullur
force-pushed
the
easymesh-client_assoc_ctrl_req
branch
from
a4a305c to
e354e4f
Compare
narendradandu
approved these changes
Apr 15, 2026
Contributor
|
Internal build success - https://gerrit.teamccp.com/#/c/953895/ |
narendradandu
approved these changes
Apr 21, 2026
narendradandu
approved these changes
Apr 21, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
RDKBWIFI-278: CLIENT ASSOC CTRL REQUEST
Implement client association control request handling on a per-station basis.
The agent receives and processes the request, forwarding it from the agent to OneWiFi and then to rdk-wifi-hal to block or unblock clients using the ACL mechanism.
Unit Testing:
Triggered the association control request from the controller using rdkb-cli.
Added a temporary handler in main.go and invoked it via a curl command.
Note: EasyMesh(rdkb-cli) currently supports processing this command only for connected clients.
Test Results:
When the controller sends a request to block a connected client on a specific BSSID for a defined duration, the client is added to the ACL for that BSSID.
If the client disconnects and attempts to reconnect, it is denied access to the same BSSID.
When blocked on the 5GHz BSSID, the client was still able to connect to the 2.4GHz BSSID.
After blocking the client on both 5GHz and 2.4GHz BSSIDs, the client was unable to connect until the validity timer expired.
Signed-off-by: Sundram Patel Sundram.p@tataelxsi.co.in