RDKCOM-5528: RDKBDEV-3377 [Easymesh] Skip onewifi VAP creation in EasyMesh coloca…#901
Open
vlad-safonov wants to merge 1 commit intordkcentral:developfrom
Conversation
…ted mode Reason for change: In EasyMesh colocated deployments, VAPs (private, public, mesh) should not be automatically created during OneWiFi initialization. The EasyMesh controller will provide proper configuration via Multi-AP protocol and trigger VAP creation at the appropriate time. This change skips start_gateway_vaps() in rdk_dev_mode_type_em_colocated_node mode, similar to the existing extender mode logic. Radios are still initialized, and all services remain ready to handle configuration updates. Test procedure: verify all VAPs creted properly during init Risk: Low Priority: P2
Contributor
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
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.
…ted mode
Reason for change: In EasyMesh colocated deployments, VAPs (private, public, mesh) should not be automatically created during OneWiFi initialization. The EasyMesh controller will provide proper configuration via Multi-AP protocol and trigger VAP creation at the appropriate time.
This change skips start_gateway_vaps() in rdk_dev_mode_type_em_colocated_node mode, similar to the existing extender mode logic. Radios are still initialized, and all services remain ready to handle configuration updates.
Test procedure: verify all VAPs creted properly during init
Risk: Low
Priority: P2