Skip to content

Conversation

bcarlson-dev
Copy link
Contributor

@bcarlson-dev bcarlson-dev commented Sep 10, 2025

Reason for change: With this, unified-wifi-mesh can read the SSID and password of the backhaul mesh, then tell the backhaul sta that it should connect to that network. unified-wifi-mesh should be in charge of telling OneWifi what it should associate to. OneWifi shouldn't blindly associate to a network.

Test Procedure: Ensure the mesh_ap_passphrase variable is populated in the em_bss_t struct.

Risks: Very Low

Priority: P1

Depends on unified-wifi-mesh #442

@gsathish86
Copy link
Contributor

@bcarlson-dev
Can you check why the Pi builds are failing ?

@bcarlson-dev
Copy link
Contributor Author

@bcarlson-dev

Can you check why the Pi builds are failing ?

I am on my honeymoon and will be unavailable but with every PR I do, I make the description very full. This one states that it depends on changes in a UWM PR.

Reason for change: With this, unified-wifi-mesh can read the SSID and
password of the backhaul mesh, then tell the backhaul sta that it should
connect to that network. `unified-wifi-mesh` should be in charge of
telling OneWifi what it should associate to. `OneWifi` shouldn't blindly
associate to a network.

Test Procedure: Ensure the `mesh_ap_passphrase` variable is populated in
the `em_bss_t` struct.

Risks: Very Low

Priority: P1

Signed-off-by: Benjamin Carlson <[email protected]>
@bcarlson-dev bcarlson-dev force-pushed the normal-sta-connection-method branch from 1ab657e to 3985097 Compare October 13, 2025 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants