Instant Privacy: Default status is incorrect

[KarenChen-Linksys]

Preconditions:
Instant Privacy physical button has been deactivated.

Steps:

1. Go to Menu.
2. Observe the Instant Privacy status.

Actual Result:
The Instant Privacy status is enabled (it allows new clients to connect to the DUT).

Expected Result:
The Instant Privacy status is disabled.

Device:
Pinnacle 2.0 FW: 1.2.1.26061108
Linksys Now Version: 2.4.0.700510

Screenshots

Additional context
log.txt

[AustinChangLinksys]

🔍 Automated investigation — observation (confidence: Medium)

Reviewed the attached screenshot against build 2.4.0.700510. This is a confirmed-behavior report; root-cause code investigation is still pending.

Observed behavior (from the attached screenshot):

• On the Menu page (#/uspMenu), the "Instant Privacy" tile ("Lock network to currently connected devices") shows its toggle as On.
• Per the report, the physical button state is deactivated, so the Menu's enabled state and the actual device state disagree.

So the symptom is a state-display mismatch for Instant Privacy between the Menu tile and the actual (physical-button) state.

Backend: the attached log shows no error responses, non-200 statuses, or USP failure codes around this — consistent with a front-end state-sync/read issue rather than a backend error.

Next step: root cause (which source the Menu tile reads for Instant Privacy state, and why it doesn't reflect the deactivated state) requires reading the relevant provider/service code; that code-level investigation is pending and will be added in a follow-up.

Automated triage — observation only. No root cause asserted yet, no timeline, ownership, or fix decision implied.

[HankYuLinksys]

Root cause identified — this is a surface symptom of a deeper firmware bug.

The underlying issue is that Instant Privacy's MAC whitelist (AllowedMACAddress) is completely ineffective at the firmware execution layer. The feature only has two actual states: "block all" or "allow all", regardless of the whitelist content.

The incorrect default display (showing ON after factory reset) happens because the firmware defaults MACAddressControlEnabled = 1 with a sentinel 00:00:00:00:00:00 list, but filtering is never actually activated — so the functional behavior is accidentally correct (off), while the app misreads the flag.

Full investigation and test results: #1115