diff options
author | lesl <lesl@google.com> | 2020-06-22 16:22:44 +0800 |
---|---|---|
committer | lesl <lesl@google.com> | 2020-06-23 16:52:07 +0800 |
commit | e81be4c68c3d0bd693dc42220a95f61aa01ba559 (patch) | |
tree | 98280988b7e4ce9631b34113511b4f5ae7f3059b /libs | |
parent | dfdf77373982a9b3da32784b3705ef713f4fd2c8 (diff) |
wifi: Support blocked list when ClientControlEnabled is false
Control whether framework should disconnect a new/unknown client(MAC)
initially or not based on the ClientControlEnabled flag.
ClientControlEnabled (false) -> New/unknown Clients will be allowed
to connect initially i.e. framework will not blindly disconnect a new client.
Framework will instead only provide a callback notification
about new client connection.
Clients would be disconnected only after user action
i.e. user decides to adds the new client to Blocklist
This avoids unnecessarily client disconnect in the case user
chooses *not* to add client to Blocklist.
ClientControlEnabled (true) -> New/unknown Clients will *not* be allowed
to connect initially until user approval
i.e. framework will disconnect the new client and provide callback
notification about new client connection.
Clients would be allowed (next attempt) only after user/setting
approves the new client to be added to "allow list".
Impact:
No impact for ClientControlEnabled is enable.
No impact for non-supported client control feature device because it
will check overlay config: OFTAP_FEATURE_CLIENT_FORCE_DISCONNECT,
i.e. No impact with Pixel.
Bug: 159582750
Test: atest FrameworksWifiTests
Change-Id: I1c8fdbcdbacfb1bca418584bf7480192dc0a9951
Diffstat (limited to 'libs')
0 files changed, 0 insertions, 0 deletions