Skip to content

RDKBWIFI-388: Add support for onboarding extender using WPS mechanism in RDK-B - #24

Merged
cpokuru merged 1 commit into
rdkcentral:developfrom
bsomanath:develop
Jul 23, 2026
Merged

RDKBWIFI-388: Add support for onboarding extender using WPS mechanism in RDK-B#24
cpokuru merged 1 commit into
rdkcentral:developfrom
bsomanath:develop

Conversation

@bsomanath

Copy link
Copy Markdown

On extender builds (CONFIG_EXTENDER), trigger WPS PBC on the station AccessPoint.16 interface instead of FH AP.1/AP.2.

… in RDK-B

On extender builds (CONFIG_EXTENDER), trigger WPS PBC on the station
AccessPoint.16 interface instead of FH AP.1/AP.2.

Signed-off-by: Somanath Bulusu <bsomanath@plume.com>
Copilot AI review requested due to automatic review settings July 23, 2026 10:23

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds extender-specific WPS onboarding behavior in rdk-wps-monitor so that, on CONFIG_EXTENDER builds, the WPS PBC trigger is sent to the station interface (AP.16) rather than the fronthaul AP.1/AP.2.

Changes:

  • On CONFIG_EXTENDER, trigger WPS via Device.WiFi.AccessPoint.16.WPS.X_CISCO_COM_ActivatePushButton.
  • Otherwise, keep existing behavior of triggering WPS for both 2.4GHz (AP.1) and 5GHz (AP.2).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread rdk-wps-monitor/source/button_callback.c
Comment thread rdk-wps-monitor/source/button_callback.c
@cpokuru
cpokuru merged commit c1b78aa into rdkcentral:develop Jul 23, 2026
3 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants