Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-23 15:49:28 +01:00
Code Releases Activity
891b78e9e8
iwd/src/knownnetworks.h

132 lines
4.8 KiB
C
Raw Normal View History

knownnetworks: Implement KnownNetworks interface knownnetworks.c/.h implements the KnownNetworks interface and loads the known networks from storage on startup. The list of all the networks including information on whether a network is known is managed in network.c to avoid having two separate lists of network_info structures and keeping them in sync. That turns out to be difficult because the network.c list is sorted by connected_time and connected_time changes can be triggered in both network.c or knownnetworks.c. Both can also trigger a network_info to be removed completely.
2016-06-17 00:54:15 +02:00
/*
*
* Wireless daemon for Linux
*
network: Introduce a concept of known frequencies Each known network (previously connected) will have a set of known frequencies associated with it, e.g. a set of frequencies from all BSSs observed. The list of known frequencies is sorted with the most recently observed frequency in the head.
2019-04-11 21:14:25 +02:00
* Copyright (C) 2016-2019 Intel Corporation. All rights reserved.
knownnetworks: Implement KnownNetworks interface knownnetworks.c/.h implements the KnownNetworks interface and loads the known networks from storage on startup. The list of all the networks including information on whether a network is known is managed in network.c to avoid having two separate lists of network_info structures and keeping them in sync. That turns out to be difficult because the network.c list is sorted by connected_time and connected_time changes can be triggered in both network.c or knownnetworks.c. Both can also trigger a network_info to be removed completely.
2016-06-17 00:54:15 +02:00
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*
*/
network: Refactor and move Known Networks management Until now network.c managed the list of network_info structs including for known networks and networks that are seen in at least one device's scan results, with the is_known flag to distinguish known networks. Each time the list was processed though the code was either interested in one subset of networks or the other. Split the list into a Known Networks list and the list of other networks seen in scans. Move all code related to Known Networks to knownnetworks.c, this simplifies network.h. It also gets rid of network_info_get_known which actually returned the list of all network_infos (not just for known networks), which logically should have been private to network.c. Update device.c and scan.c to use functions specific to Known Networks instead of filtering the lists by the is_known flag. This will also allow knownnetworks.c to export DBus objects and/or properties for the Known Networks information because it now knows when Known Networks are added, removed or modified by IWD.
2018-07-22 14:15:18 +02:00
enum security;
knownnetworks: Add lookup API for recent frequencies The returned scan_freq_set contains the known frequencies from the top most recently connected networks.
2019-04-16 23:51:41 +02:00
struct scan_freq_set;
network: knownnetworks: introduce network_info_ops The known network APIs all revolved around the ssid/security matching to do any operations on the provisioning file. In the near future hotspot provisioning files (managed by hotspot.c) will be incorporated into the known network list. Since these hotspot files do not use the ssid as the file name hotspot.c will need other ways of matching. This patch adds network_info_ops to the network object. This ops structure will hold function pointers which operate on network_info rather than ssid/security. This will allow hotspot and known networks to both register their own operation routines. For now open, touch, sync, remove, free, and get_path were added. Wrappers were added for accessing these operations outside of knownnetworks.c.
2019-08-15 22:15:13 +02:00
struct network_info;
network: Refactor and move Known Networks management Until now network.c managed the list of network_info structs including for known networks and networks that are seen in at least one device's scan results, with the is_known flag to distinguish known networks. Each time the list was processed though the code was either interested in one subset of networks or the other. Split the list into a Known Networks list and the list of other networks seen in scans. Move all code related to Known Networks to knownnetworks.c, this simplifies network.h. It also gets rid of network_info_get_known which actually returned the list of all network_infos (not just for known networks), which logically should have been private to network.c. Update device.c and scan.c to use functions specific to Known Networks instead of filtering the lists by the is_known flag. This will also allow knownnetworks.c to export DBus objects and/or properties for the Known Networks information because it now knows when Known Networks are added, removed or modified by IWD.
2018-07-22 14:15:18 +02:00
knownnetworks: add watch API's Modules can watch for known network addition and removal.
2019-08-09 18:28:42 +02:00
enum known_networks_event {
KNOWN_NETWORKS_EVENT_ADDED,
KNOWN_NETWORKS_EVENT_REMOVED,
};
network: knownnetworks: introduce network_info_ops The known network APIs all revolved around the ssid/security matching to do any operations on the provisioning file. In the near future hotspot provisioning files (managed by hotspot.c) will be incorporated into the known network list. Since these hotspot files do not use the ssid as the file name hotspot.c will need other ways of matching. This patch adds network_info_ops to the network object. This ops structure will hold function pointers which operate on network_info rather than ssid/security. This will allow hotspot and known networks to both register their own operation routines. For now open, touch, sync, remove, free, and get_path were added. Wrappers were added for accessing these operations outside of knownnetworks.c.
2019-08-15 22:15:13 +02:00
struct network_info_ops {
struct l_settings *(*open)(struct network_info *info);
int (*touch)(struct network_info *info);
void (*sync)(struct network_info *info, struct l_settings *settings);
void (*remove)(struct network_info *info);
void (*free)(struct network_info *info);
const char *(*get_path)(const struct network_info *info);
knownnetworks: add get_name and get_type ops
2019-08-21 21:06:13 +02:00
const char *(*get_name)(const struct network_info *info);
const char *(*get_type)(const struct network_info *info);
knownnetworks: add get_vendor_ies operation This will provide the hotspot module with enough info for it to build the required vendor IEs to be provided with (Re)Association.
2019-09-09 18:49:08 +02:00
const struct iovec *(*get_extra_ies)(const struct network_info *info,
struct scan_bss *bss,
size_t *num_elems);
knownnetworks: add get_file_path op Gets the provisioning file path stored on disk
2019-09-12 18:53:32 +02:00
char *(*get_file_path)(const struct network_info *info);
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
bool (*match_hessid)(const struct network_info *info,
const uint8_t *hessid);
knownnetworks: get matched RC on match_roaming_consortium The HS20 module had its own getter for returning the matched roaming consortium. Since we already have the network_info op for matching we might as well return the matched RC rather than just a bool. This allows the RC to be included in (Re)Association without the need for a specific getter.
2019-09-06 20:11:01 +02:00
const uint8_t *(*match_roaming_consortium)(
const struct network_info *info,
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
const uint8_t *rc_ie,
knownnetworks: get matched RC on match_roaming_consortium The HS20 module had its own getter for returning the matched roaming consortium. Since we already have the network_info op for matching we might as well return the matched RC rather than just a bool. This allows the RC to be included in (Re)Association without the need for a specific getter.
2019-09-06 20:11:01 +02:00
size_t rc_len,
size_t *rc_len_out);
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
bool (*match_nai_realms)(const struct network_info *info,
const char **nai_realms);
network: knownnetworks: introduce network_info_ops The known network APIs all revolved around the ssid/security matching to do any operations on the provisioning file. In the near future hotspot provisioning files (managed by hotspot.c) will be incorporated into the known network list. Since these hotspot files do not use the ssid as the file name hotspot.c will need other ways of matching. This patch adds network_info_ops to the network object. This ops structure will hold function pointers which operate on network_info rather than ssid/security. This will allow hotspot and known networks to both register their own operation routines. For now open, touch, sync, remove, free, and get_path were added. Wrappers were added for accessing these operations outside of knownnetworks.c.
2019-08-15 22:15:13 +02:00
};
knownnetworks: move network_info into knownnetworks
2019-08-15 22:15:12 +02:00
struct network_info {
network: knownnetworks: introduce network_info_ops The known network APIs all revolved around the ssid/security matching to do any operations on the provisioning file. In the near future hotspot provisioning files (managed by hotspot.c) will be incorporated into the known network list. Since these hotspot files do not use the ssid as the file name hotspot.c will need other ways of matching. This patch adds network_info_ops to the network object. This ops structure will hold function pointers which operate on network_info rather than ssid/security. This will allow hotspot and known networks to both register their own operation routines. For now open, touch, sync, remove, free, and get_path were added. Wrappers were added for accessing these operations outside of knownnetworks.c.
2019-08-15 22:15:13 +02:00
const struct network_info_ops *ops;
knownnetworks: move network_info into knownnetworks
2019-08-15 22:15:12 +02:00
char ssid[33];
enum security type;
struct l_queue *known_frequencies;
knownnetworks: use l_path_get_mtime Rather than using timespec directly, ELL has a convenient API to get the elapsed microseconds as a uint64_t. This can then be used with the other l_time_ APIs for comparison. This patch removes timespec from network_info and updates to use l_time_* API's for sorting.
2019-08-21 21:06:10 +02:00
uint64_t connected_time; /* Time last connected */
knownnetworks: move network_info into knownnetworks
2019-08-15 22:15:12 +02:00
int seen_count; /* Ref count for network.info */
knownnetwork: track/optimize UUID for known networks The UUID was being generated every time we synced which is wasteful. Instead we can track the UUID inside network_info and only generate it once when needed. Two new network_info APIs were added: network_info_set_uuid network_info_get_uuid The setter is used when the frequency file is loaded. If a valid UUID is found in the frequency file this UUID is set and used. network_info_get_uuid will not just get the UUID, but actually generate it if one has not been set yet. This will allow other modules to get/generate the UUID if one has no been loaded from the frequency file.
2019-09-13 19:27:26 +02:00
uint8_t uuid[16];
knownnetworks: move network_info into knownnetworks
2019-08-15 22:15:12 +02:00
bool is_hidden:1;
bool is_autoconnectable:1;
knownnetworks: add hotspot flag to network_info Hotspot will start adding its own known networks and other modules need a way of differentiating between the two network types.
2019-08-15 22:15:15 +02:00
bool is_hotspot:1;
knownnetwork: track/optimize UUID for known networks The UUID was being generated every time we synced which is wasteful. Instead we can track the UUID inside network_info and only generate it once when needed. Two new network_info APIs were added: network_info_set_uuid network_info_get_uuid The setter is used when the frequency file is loaded. If a valid UUID is found in the frequency file this UUID is set and used. network_info_get_uuid will not just get the UUID, but actually generate it if one has not been set yet. This will allow other modules to get/generate the UUID if one has no been loaded from the frequency file.
2019-09-13 19:27:26 +02:00
bool has_uuid:1;
knownnetworks: move network_info into knownnetworks
2019-08-15 22:15:12 +02:00
};
network: Refactor and move Known Networks management Until now network.c managed the list of network_info structs including for known networks and networks that are seen in at least one device's scan results, with the is_known flag to distinguish known networks. Each time the list was processed though the code was either interested in one subset of networks or the other. Split the list into a Known Networks list and the list of other networks seen in scans. Move all code related to Known Networks to knownnetworks.c, this simplifies network.h. It also gets rid of network_info_get_known which actually returned the list of all network_infos (not just for known networks), which logically should have been private to network.c. Update device.c and scan.c to use functions specific to Known Networks instead of filtering the lists by the is_known flag. This will also allow knownnetworks.c to export DBus objects and/or properties for the Known Networks information because it now knows when Known Networks are added, removed or modified by IWD.
2018-07-22 14:15:18 +02:00
typedef bool (*known_networks_foreach_func_t)(const struct network_info *info,
void *user_data);
knownnetworks: add watch API's Modules can watch for known network addition and removal.
2019-08-09 18:28:42 +02:00
typedef void (*known_networks_watch_func_t)(enum known_networks_event event,
const struct network_info *info,
void *user_data);
typedef void (*known_networks_destroy_func_t)(void *user_data);
network: Introduce a concept of known frequencies Each known network (previously connected) will have a set of known frequencies associated with it, e.g. a set of frequencies from all BSSs observed. The list of known frequencies is sorted with the most recently observed frequency in the head.
2019-04-11 21:14:25 +02:00
struct known_frequency {
uint32_t frequency;
};
network: Move network offset calculation network_find_rank_index was used to find the offset of the selected network_info among known networks so as to compute a modifier based on the rankmod table. Instead of using known_networks_foreach for this, moove it to knownnetworks.c where it can be coded and optimized separately. For now provide a simple for loop implementation.
2019-08-09 08:06:10 +02:00
int known_network_offset(const struct network_info *target);
network: Refactor and move Known Networks management Until now network.c managed the list of network_info structs including for known networks and networks that are seen in at least one device's scan results, with the is_known flag to distinguish known networks. Each time the list was processed though the code was either interested in one subset of networks or the other. Split the list into a Known Networks list and the list of other networks seen in scans. Move all code related to Known Networks to knownnetworks.c, this simplifies network.h. It also gets rid of network_info_get_known which actually returned the list of all network_infos (not just for known networks), which logically should have been private to network.c. Update device.c and scan.c to use functions specific to Known Networks instead of filtering the lists by the is_known flag. This will also allow knownnetworks.c to export DBus objects and/or properties for the Known Networks information because it now knows when Known Networks are added, removed or modified by IWD.
2018-07-22 14:15:18 +02:00
bool known_networks_foreach(known_networks_foreach_func_t function,
void *user_data);
bool known_networks_has_hidden(void);
struct network_info *known_networks_find(const char *ssid,
enum security security);
knownnetworks: Add lookup API for recent frequencies The returned scan_freq_set contains the known frequencies from the top most recently connected networks.
2019-04-16 23:51:41 +02:00
struct scan_freq_set *known_networks_get_recent_frequencies(
uint8_t num_networks_tosearch);
network: Move known_frequency queue management Isolate the known_frequency queue management to a function and place that function in knownnetworks.c where it now belongs. Since we no longer have network_info objects for unknown networks, only frequencies for known networks are tracked
2019-08-09 18:40:07 +02:00
int known_network_add_frequency(struct network_info *info, uint32_t frequency);
knownnetwork: track/optimize UUID for known networks The UUID was being generated every time we synced which is wasteful. Instead we can track the UUID inside network_info and only generate it once when needed. Two new network_info APIs were added: network_info_set_uuid network_info_get_uuid The setter is used when the frequency file is loaded. If a valid UUID is found in the frequency file this UUID is set and used. network_info_get_uuid will not just get the UUID, but actually generate it if one has not been set yet. This will allow other modules to get/generate the UUID if one has no been loaded from the frequency file.
2019-09-13 19:27:26 +02:00
void known_network_frequency_sync(struct network_info *info);
knownnetworks: add watch API's Modules can watch for known network addition and removal.
2019-08-09 18:28:42 +02:00
uint32_t known_networks_watch_add(known_networks_watch_func_t func,
void *user_data,
known_networks_destroy_func_t destroy);
void known_networks_watch_remove(uint32_t id);
network: knownnetworks: introduce network_info_ops The known network APIs all revolved around the ssid/security matching to do any operations on the provisioning file. In the near future hotspot provisioning files (managed by hotspot.c) will be incorporated into the known network list. Since these hotspot files do not use the ssid as the file name hotspot.c will need other ways of matching. This patch adds network_info_ops to the network object. This ops structure will hold function pointers which operate on network_info rather than ssid/security. This will allow hotspot and known networks to both register their own operation routines. For now open, touch, sync, remove, free, and get_path were added. Wrappers were added for accessing these operations outside of knownnetworks.c.
2019-08-15 22:15:13 +02:00
struct l_settings *network_info_open_settings(struct network_info *info);
int network_info_touch(struct network_info *info);
const char *network_info_get_path(const struct network_info *info);
knownnetworks: add get_name and get_type ops
2019-08-21 21:06:13 +02:00
const char *network_info_get_name(const struct network_info *info);
const char *network_info_get_type(const struct network_info *info);
knownnetworks: add get_vendor_ies operation This will provide the hotspot module with enough info for it to build the required vendor IEs to be provided with (Re)Association.
2019-09-09 18:49:08 +02:00
const struct iovec *network_info_get_extra_ies(const struct network_info *info,
struct scan_bss *bss,
size_t *num_elems);
knownnetwork: track/optimize UUID for known networks The UUID was being generated every time we synced which is wasteful. Instead we can track the UUID inside network_info and only generate it once when needed. Two new network_info APIs were added: network_info_set_uuid network_info_get_uuid The setter is used when the frequency file is loaded. If a valid UUID is found in the frequency file this UUID is set and used. network_info_get_uuid will not just get the UUID, but actually generate it if one has not been set yet. This will allow other modules to get/generate the UUID if one has no been loaded from the frequency file.
2019-09-13 19:27:26 +02:00
/* Gets the UUID, or generates one if not yet created */
const uint8_t *network_info_get_uuid(struct network_info *info);
void network_info_set_uuid(struct network_info *info, const uint8_t *uuid);
knownnetworks: add roam frequency getter Gets a newly created scan_freq_set containing the most recent frequencies for the network. The currently connected BSS frequency (passed as a parameters) will not be included in the set.
2019-09-16 22:14:13 +02:00
struct scan_freq_set *network_info_get_roam_frequencies(
const struct network_info *info,
uint32_t current_freq,
uint8_t max);
knownnetworks: add known_networks_{add,remove} These two API's have been added to allow hotspot to add its own networks to the known network list. This will allow any added networks to behave exactly like they do now, including all the dbus and watchlist functionality.
2019-08-15 22:15:16 +02:00
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
bool network_info_match_hessid(const struct network_info *info,
const uint8_t *hessid);
knownnetworks: get matched RC on match_roaming_consortium The HS20 module had its own getter for returning the matched roaming consortium. Since we already have the network_info op for matching we might as well return the matched RC rather than just a bool. This allows the RC to be included in (Re)Association without the need for a specific getter.
2019-09-06 20:11:01 +02:00
const uint8_t *network_info_match_roaming_consortium(
const struct network_info *info,
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
const uint8_t *rc,
knownnetworks: get matched RC on match_roaming_consortium The HS20 module had its own getter for returning the matched roaming consortium. Since we already have the network_info op for matching we might as well return the matched RC rather than just a bool. This allows the RC to be included in (Re)Association without the need for a specific getter.
2019-09-06 20:11:01 +02:00
size_t rc_len,
size_t *rc_len_out);
knownnetworks: add matching ops to network_info These operations will allow the hotspot module to implement matching HESSID, Roaming Consortium, and NAI realms. This offloads the matching details into the hotspot module.
2019-08-19 20:11:56 +02:00
bool network_info_match_nai_realm(const struct network_info *info,
const char **nai_realms);
knownnetworks: add known_networks_{add,remove} These two API's have been added to allow hotspot to add its own networks to the known network list. This will allow any added networks to behave exactly like they do now, including all the dbus and watchlist functionality.
2019-08-15 22:15:16 +02:00
void known_networks_add(struct network_info *info);
knownnetworks: refactor to expose known_network_update known_network_update was being used to both update and create known networks as they appeared on the file system. Hotspot needs updating capabilities so known_network_update was exposed and updated with one major difference; it no longer can be used to create new known networks. For creation, a new API was added (known_network_new) which will create and add to the queue.
2019-08-28 18:34:10 +02:00
void known_network_update(struct network_info *info,
knownneetworks: React to mtime updates We track mtime as the 'LastConnectedTime' of the network, and also sort the known network list according to the last connected time. Unfortunately we were never reacting to ATTRIB changes, and so were never updating the network_info->connected_time whenever a network was connected to. Rework the logic to address this. This also fixes a small bug where the connected_time was not set properly prior to removal / re-insertion of the network_info.
2020-01-27 21:28:08 +01:00
struct l_settings *settings);
void known_network_set_connected_time(struct network_info *network,
knownnetworks: refactor to expose known_network_update known_network_update was being used to both update and create known networks as they appeared on the file system. Hotspot needs updating capabilities so known_network_update was exposed and updated with one major difference; it no longer can be used to create new known networks. For creation, a new API was added (known_network_new) which will create and add to the queue.
2019-08-28 18:34:10 +02:00
uint64_t connected_time);
knownnetworks: add known_networks_{add,remove} These two API's have been added to allow hotspot to add its own networks to the known network list. This will allow any added networks to behave exactly like they do now, including all the dbus and watchlist functionality.
2019-08-15 22:15:16 +02:00
void known_networks_remove(struct network_info *info);
Copy Permalink