fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-20 15:10:05 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/libnm/libnm.ver

1743 lines
56 KiB
Text
Raw Normal View History

libnm/build: add versioning to linker script https://bugzilla.gnome.org/show_bug.cgi?id=741069
2014-10-06 17:12:38 +02:00
libnm_1_0_0 {
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
global:
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_802_11_ap_flags_get_type;
nm_802_11_ap_security_flags_get_type;
nm_802_11_mode_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_access_point_connection_valid;
nm_access_point_filter_connections;
nm_access_point_get_bssid;
nm_access_point_get_flags;
nm_access_point_get_frequency;
nm_access_point_get_max_bitrate;
nm_access_point_get_mode;
nm_access_point_get_rsn_flags;
nm_access_point_get_ssid;
nm_access_point_get_strength;
nm_access_point_get_type;
nm_access_point_get_wpa_flags;
nm_active_connection_get_connection;
nm_active_connection_get_connection_type;
nm_active_connection_get_default6;
nm_active_connection_get_default;
nm_active_connection_get_devices;
nm_active_connection_get_dhcp4_config;
nm_active_connection_get_dhcp6_config;
nm_active_connection_get_id;
nm_active_connection_get_ip4_config;
nm_active_connection_get_ip6_config;
nm_active_connection_get_master;
libnm: fix NMActiveConnection object-path-valued properties NMActiveConnection:connection was an object path rather than an NMRemoteConnection because in the past the NMObject property system wasn't capable of handling NMRemoteConnection-valued properties. NMActiveConnection:master was an object path rather than an NMDevice entirely by accident. Fix both. NMActiveConnection:specific-object can't currently be converted to an object, because we don't know ahead of time what object type it is, and NMObject can't deal with that. Instead, we rename it to :specific-object-path (and likewise for its get function), both to emphasize that it doesn't behave like other properties, and to leave the old name open for an actual object-valued property later on.
2014-10-09 09:24:05 -04:00
nm_active_connection_get_specific_object_path;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_active_connection_get_state;
nm_active_connection_get_type;
nm_active_connection_get_uuid;
nm_active_connection_get_vpn;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_active_connection_state_get_type;
libnm-core, settings: move NMAgentManagerError to nm-errors Move the definition of NMAgentManagerError to nm-errors, register it with D-Bus, and verify in the tests that it maps correctly.
2014-10-15 15:27:25 -04:00
nm_agent_manager_error_get_type;
nm_agent_manager_error_quark;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_bluetooth_capabilities_get_type;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_client_activate_connection_async;
nm_client_activate_connection_finish;
nm_client_add_and_activate_connection_async;
nm_client_add_and_activate_connection_finish;
libnm: merge NMRemoteSettings into NMClient Make NMRemoteSettings internal and have NMClient wrap all of its APIs, just like it does with NMManager.
2014-09-29 10:58:16 -04:00
nm_client_add_connection_async;
nm_client_add_connection_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_check_connectivity;
nm_client_check_connectivity_async;
nm_client_check_connectivity_finish;
nm_client_deactivate_connection;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_client_deactivate_connection_async;
nm_client_deactivate_connection_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_error_get_type;
nm_client_error_quark;
nm_client_get_activating_connection;
nm_client_get_active_connections;
libnm: merge NMRemoteSettings into NMClient Make NMRemoteSettings internal and have NMClient wrap all of its APIs, just like it does with NMManager.
2014-09-29 10:58:16 -04:00
nm_client_get_connection_by_id;
nm_client_get_connection_by_path;
nm_client_get_connection_by_uuid;
libnm: change GSList to GPtrArray in libnm methods libnm mostly used GPtrArrays in its APIs, except that arrays of connections were usually GSLists. Fix this and make them GPtrArrays too (and rename nm_client_list_connections() to nm_client_get_connections() to match everything else).
2014-10-22 12:32:46 -04:00
nm_client_get_connections;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_get_connectivity;
nm_client_get_device_by_iface;
nm_client_get_device_by_path;
nm_client_get_devices;
nm_client_get_logging;
libnm: synchronize NMClient and NMRemoteSettings "is NM running" properties Rename NMClient:manager-running and NMRemoteSettings:service-running to both be :nm-running.
2014-08-05 10:05:26 -04:00
nm_client_get_nm_running;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_get_permission_result;
nm_client_get_primary_connection;
nm_client_get_startup;
nm_client_get_state;
nm_client_get_type;
nm_client_get_version;
libnm: merge NMRemoteSettings into NMClient Make NMRemoteSettings internal and have NMClient wrap all of its APIs, just like it does with NMManager.
2014-09-29 10:58:16 -04:00
nm_client_load_connections;
nm_client_load_connections_async;
nm_client_load_connections_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_networking_get_enabled;
nm_client_networking_set_enabled;
nm_client_new;
nm_client_new_async;
nm_client_new_finish;
nm_client_permission_get_type;
nm_client_permission_result_get_type;
libnm: merge NMRemoteSettings into NMClient Make NMRemoteSettings internal and have NMClient wrap all of its APIs, just like it does with NMManager.
2014-09-29 10:58:16 -04:00
nm_client_reload_connections;
nm_client_reload_connections_async;
nm_client_reload_connections_finish;
nm_client_save_hostname;
nm_client_save_hostname_async;
nm_client_save_hostname_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_client_set_logging;
nm_client_wimax_get_enabled;
nm_client_wimax_hardware_get_enabled;
nm_client_wimax_set_enabled;
nm_client_wireless_get_enabled;
nm_client_wireless_hardware_get_enabled;
nm_client_wireless_set_enabled;
nm_client_wwan_get_enabled;
nm_client_wwan_hardware_get_enabled;
nm_client_wwan_set_enabled;
nm_connection_add_setting;
nm_connection_clear_secrets;
nm_connection_clear_secrets_with_flags;
libnm-core: clean up nm_connection_replace_settings()'s semantics On failure, nm_connection_replace_settings() would leave the connection in an undefined state. Fix it so that either (a) the settings are replaced and the resulting connection is valid and we return TRUE, or (b) the connection is untouched and we return FALSE and an error. (And add a test case for this.)
2014-08-22 10:14:38 -04:00
nm_connection_clear_settings;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_connection_compare;
nm_connection_diff;
nm_connection_dump;
nm_connection_error_get_type;
nm_connection_error_quark;
nm_connection_for_each_setting_value;
nm_connection_get_connection_type;
nm_connection_get_id;
nm_connection_get_interface_name;
nm_connection_get_path;
nm_connection_get_setting;
nm_connection_get_setting_802_1x;
nm_connection_get_setting_adsl;
nm_connection_get_setting_bluetooth;
nm_connection_get_setting_bond;
nm_connection_get_setting_bridge;
nm_connection_get_setting_bridge_port;
nm_connection_get_setting_by_name;
nm_connection_get_setting_cdma;
nm_connection_get_setting_connection;
nm_connection_get_setting_dcb;
nm_connection_get_setting_generic;
nm_connection_get_setting_gsm;
nm_connection_get_setting_infiniband;
nm_connection_get_setting_ip4_config;
nm_connection_get_setting_ip6_config;
nm_connection_get_setting_olpc_mesh;
nm_connection_get_setting_ppp;
nm_connection_get_setting_pppoe;
nm_connection_get_setting_serial;
nm_connection_get_setting_team;
nm_connection_get_setting_team_port;
nm_connection_get_setting_vlan;
nm_connection_get_setting_vpn;
nm_connection_get_setting_wimax;
nm_connection_get_setting_wired;
nm_connection_get_setting_wireless;
nm_connection_get_setting_wireless_security;
nm_connection_get_type;
nm_connection_get_uuid;
nm_connection_get_virtual_device_description;
nm_connection_is_type;
libnm-core: add nm_connection_is_virtual() Add a method to determine if a connection applies to a virtual device. Perhaps eventually the logic should be spread across the NMSetting classes, but for now it's better off having it in NMConnection than once in NMManager and once in nmcli.
2014-08-04 16:27:43 -04:00
nm_connection_is_virtual;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_connection_need_secrets;
nm_connection_normalize;
nm_connection_remove_setting;
nm_connection_replace_settings;
nm_connection_replace_settings_from_connection;
libnm-core: rename NMConnection to/from_hash methods Rename nm_connection_to_hash() to nm_connection_to_dbus(), and nm_connection_new_from_hash() to nm_connection_new_from_dbus(). In addition to clarifying that this is specifically the D-Bus serialization format, these names will also work better in the GDBus-based future where the serialization format is GVariant, not GHashTable. Also, move NMSettingHashFlags to nm-connection.h, and rename it NMConnectionSerializationFlags.
2014-08-06 19:35:31 -04:00
nm_connection_serialization_flags_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_connection_set_path;
libnm-core: rename NMConnection to/from_hash methods Rename nm_connection_to_hash() to nm_connection_to_dbus(), and nm_connection_new_from_hash() to nm_connection_new_from_dbus(). In addition to clarifying that this is specifically the D-Bus serialization format, these names will also work better in the GDBus-based future where the serialization format is GVariant, not GHashTable. Also, move NMSettingHashFlags to nm-connection.h, and rename it NMConnectionSerializationFlags.
2014-08-06 19:35:31 -04:00
nm_connection_to_dbus;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_connection_update_secrets;
nm_connection_verify;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_connectivity_state_get_type;
libnm-core: add nm-errors.[ch] Add nm-errors.[ch], and move libnm-core's two error domains (NMConnectionError and NMCryptoError) there. NMCryptoError wasn't previously visible, but it can be returned from some public API, so it should be.
2014-10-15 13:20:03 -04:00
nm_crypto_error_get_type;
nm_crypto_error_quark;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_adsl_get_carrier;
nm_device_adsl_get_type;
nm_device_bond_get_carrier;
nm_device_bond_get_hw_address;
nm_device_bond_get_slaves;
nm_device_bond_get_type;
nm_device_bridge_get_carrier;
nm_device_bridge_get_hw_address;
nm_device_bridge_get_slaves;
nm_device_bridge_get_type;
nm_device_bt_get_capabilities;
nm_device_bt_get_hw_address;
nm_device_bt_get_name;
nm_device_bt_get_type;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_device_capabilities_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_connection_compatible;
nm_device_connection_valid;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_device_delete;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_device_delete_async;
nm_device_delete_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_disambiguate_names;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_device_disconnect;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_device_disconnect_async;
nm_device_disconnect_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_error_get_type;
nm_device_error_quark;
nm_device_ethernet_get_carrier;
nm_device_ethernet_get_hw_address;
nm_device_ethernet_get_permanent_hw_address;
nm_device_ethernet_get_speed;
nm_device_ethernet_get_type;
nm_device_filter_connections;
nm_device_generic_get_hw_address;
nm_device_generic_get_type;
nm_device_get_active_connection;
nm_device_get_autoconnect;
nm_device_get_available_connections;
nm_device_get_capabilities;
nm_device_get_description;
nm_device_get_device_type;
nm_device_get_dhcp4_config;
nm_device_get_dhcp6_config;
nm_device_get_driver;
nm_device_get_driver_version;
nm_device_get_firmware_missing;
nm_device_get_firmware_version;
nm_device_get_hw_address;
nm_device_get_iface;
nm_device_get_ip4_config;
nm_device_get_ip6_config;
nm_device_get_ip_iface;
nm_device_get_managed;
nm_device_get_mtu;
nm_device_get_physical_port_id;
nm_device_get_product;
nm_device_get_setting_type;
nm_device_get_state;
nm_device_get_state_reason;
nm_device_get_type;
nm_device_get_type_description;
nm_device_get_udi;
nm_device_get_vendor;
nm_device_infiniband_get_carrier;
nm_device_infiniband_get_hw_address;
nm_device_infiniband_get_type;
nm_device_is_software;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_device_modem_capabilities_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_modem_get_current_capabilities;
nm_device_modem_get_modem_capabilities;
nm_device_modem_get_type;
nm_device_olpc_mesh_get_active_channel;
nm_device_olpc_mesh_get_companion;
nm_device_olpc_mesh_get_hw_address;
nm_device_olpc_mesh_get_type;
nm_device_set_autoconnect;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_device_state_get_type;
nm_device_state_reason_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_team_get_carrier;
nm_device_team_get_hw_address;
nm_device_team_get_slaves;
nm_device_team_get_type;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_device_type_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_vlan_get_carrier;
nm_device_vlan_get_hw_address;
libnm: add :parent property for VLAN devices
2014-08-27 16:42:46 +02:00
nm_device_vlan_get_parent;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_vlan_get_type;
nm_device_vlan_get_vlan_id;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_device_wifi_capabilities_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_wifi_get_access_point_by_path;
nm_device_wifi_get_access_points;
nm_device_wifi_get_active_access_point;
nm_device_wifi_get_bitrate;
nm_device_wifi_get_capabilities;
nm_device_wifi_get_hw_address;
nm_device_wifi_get_mode;
nm_device_wifi_get_permanent_hw_address;
nm_device_wifi_get_type;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_device_wifi_request_scan;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_device_wifi_request_scan_async;
nm_device_wifi_request_scan_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_device_wimax_get_active_nsp;
nm_device_wimax_get_bsid;
nm_device_wimax_get_center_frequency;
nm_device_wimax_get_cinr;
nm_device_wimax_get_hw_address;
nm_device_wimax_get_nsp_by_path;
nm_device_wimax_get_nsps;
nm_device_wimax_get_rssi;
nm_device_wimax_get_tx_power;
nm_device_wimax_get_type;
libnm: create NMDhcpConfig as parent of NMDhcp4Config and NMDhcp6Config As with NMIP4Config and NMIP6Config, merge the two DHCP config classes into one in the public API.
2014-10-22 13:48:18 -04:00
nm_dhcp_config_get_family;
nm_dhcp_config_get_one_option;
nm_dhcp_config_get_options;
nm_dhcp_config_get_type;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_address_equal;
nm_ip_address_get_address;
nm_ip_address_get_address_binary;
libnm-core: add NMIPAddress/NMIPRoute attributes, use for labels Add key-value attributes to NMIPAddress and NMIPRoute, and use them to store IPv4 address labels. Demote NMSettingIP4Config:address-labels to a D-Bus-only property, and arrange for :addresses setter to read the labels out of that property when creating the addresses.
2014-09-16 16:38:04 -04:00
nm_ip_address_get_attribute;
nm_ip_address_get_attribute_names;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_address_get_family;
nm_ip_address_get_prefix;
nm_ip_address_get_type;
nm_ip_address_new;
nm_ip_address_new_binary;
nm_ip_address_ref;
nm_ip_address_set_address;
nm_ip_address_set_address_binary;
libnm-core: add NMIPAddress/NMIPRoute attributes, use for labels Add key-value attributes to NMIPAddress and NMIPRoute, and use them to store IPv4 address labels. Demote NMSettingIP4Config:address-labels to a D-Bus-only property, and arrange for :addresses setter to read the labels out of that property when creating the addresses.
2014-09-16 16:38:04 -04:00
nm_ip_address_set_attribute;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_address_set_prefix;
nm_ip_address_unref;
libnm: create NMIPConfig as parent of NMIP4Config and NMIP6Config Create NMIPConfig as the parent of NMIP4Config and NMIP6Config, and remove the two subclasses from the public API; while it's convenient to still have both internally, they are now identical to the outside world.
2014-10-22 13:48:18 -04:00
nm_ip_config_get_addresses;
nm_ip_config_get_domains;
nm_ip_config_get_family;
nm_ip_config_get_gateway;
nm_ip_config_get_nameservers;
nm_ip_config_get_routes;
nm_ip_config_get_searches;
nm_ip_config_get_type;
nm_ip_config_get_wins_servers;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_route_equal;
libnm-core: add NMIPAddress/NMIPRoute attributes, use for labels Add key-value attributes to NMIPAddress and NMIPRoute, and use them to store IPv4 address labels. Demote NMSettingIP4Config:address-labels to a D-Bus-only property, and arrange for :addresses setter to read the labels out of that property when creating the addresses.
2014-09-16 16:38:04 -04:00
nm_ip_route_get_attribute;
nm_ip_route_get_attribute_names;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_route_get_dest;
nm_ip_route_get_dest_binary;
nm_ip_route_get_family;
nm_ip_route_get_metric;
nm_ip_route_get_next_hop;
nm_ip_route_get_next_hop_binary;
nm_ip_route_get_prefix;
nm_ip_route_get_type;
nm_ip_route_new;
nm_ip_route_new_binary;
nm_ip_route_ref;
libnm-core: add NMIPAddress/NMIPRoute attributes, use for labels Add key-value attributes to NMIPAddress and NMIPRoute, and use them to store IPv4 address labels. Demote NMSettingIP4Config:address-labels to a D-Bus-only property, and arrange for :addresses setter to read the labels out of that property when creating the addresses.
2014-09-16 16:38:04 -04:00
nm_ip_route_set_attribute;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_ip_route_set_dest;
nm_ip_route_set_dest_binary;
nm_ip_route_set_metric;
nm_ip_route_set_next_hop;
nm_ip_route_set_next_hop_binary;
nm_ip_route_set_prefix;
nm_ip_route_unref;
libnm-core, core: move NMManagerError to nm-errors Move the definition of NMManagerError to nm-errors, register it with D-Bus, and verify in the tests that it maps correctly. NM_MANAGER_ERROR_INTERNAL gets renamed to NM_MANAGER_ERROR_FAILED for consistency. NM_MANAGER_ERROR_UNMANAGED_DEVICE is dropped since that name doesn't really describe the one place it was previously used in. NM_MANAGER_ERROR_SYSTEM_CONNECTION is dropped because it was't being used. NM_MANAGER_ERROR_UNSUPPORTED_CONNECTION_TYPE is dropped because it can be replaced with an NM_CONNECTION_ERROR. NM_MANAGER_ERROR_AUTOCONNECT_NOT_ALLOWED is turned into the more generic NM_MANAGER_ERROR_CONNECTION_NOT_AVAILABLE. Also, remove the <tp:possible-errors> sections from nm-manager.xml, since they were completely out of date.
2014-10-15 15:27:25 -04:00
nm_manager_error_get_type;
nm_manager_error_quark;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_object_get_path;
nm_object_get_type;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_remote_connection_commit_changes;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_remote_connection_commit_changes_async;
nm_remote_connection_commit_changes_finish;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_remote_connection_delete;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_remote_connection_delete_async;
nm_remote_connection_delete_finish;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_remote_connection_get_secrets;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_remote_connection_get_secrets_async;
nm_remote_connection_get_secrets_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_remote_connection_get_type;
nm_remote_connection_get_unsaved;
libnm: add NMRemoteConnection:visible property Rather than having a private "visible" signal, have a public "visible" property.
2014-07-20 12:42:59 -04:00
nm_remote_connection_get_visible;
libnm: add some missing sync/async method variants Add the missing variant in most places in the API where previously there was either only a synchronous version or only an asynchronous version. There is not yet a synchronous nm_client_activate_connection(), nm_client_add_and_activate_connection(), or nm_remote_settings_add_connection(), because the existing async code depends on waiting for other asynchronous events, so making them run synchronously is slightly more complicated. But these APIs can be added later.
2014-09-11 16:27:13 -04:00
nm_remote_connection_save;
libnm: make sync/async APIs more GLib-like Make synchronous APIs take GCancellables, and make asynchronous APIs use GAsyncReadyCallbacks and have names ending in "_async", with "_finish" functions to retrieve the results. Also, make nm_client_activate_connection_finish(), nm_client_add_and_activate_finish(), and nm_remote_settings_add_connection_finish() be (transfer full) rather than (transfer none), because the refcounting semantics become slightly confusing in some edge cases otherwise.
2014-09-11 16:27:13 -04:00
nm_remote_connection_save_async;
nm_remote_connection_save_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_secret_agent_capabilities_get_type;
nm_secret_agent_error_get_type;
nm_secret_agent_error_quark;
nm_secret_agent_get_secrets_flags_get_type;
libnm: rename NMSecretAgent to NMSecretAgentOld As with NMVpnPluginOld, rename NMSecretAgent to NMSecretAgentOld, to leave the name "NMSecretAgent" open for a new-and-improved version in NM 1.2.
2014-11-20 11:53:19 -05:00
nm_secret_agent_old_delete_secrets;
nm_secret_agent_old_get_registered;
nm_secret_agent_old_get_secrets;
nm_secret_agent_old_get_type;
nm_secret_agent_old_register;
nm_secret_agent_old_register_async;
nm_secret_agent_old_register_finish;
nm_secret_agent_old_save_secrets;
nm_secret_agent_old_unregister;
nm_secret_agent_old_unregister_async;
nm_secret_agent_old_unregister_finish;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_802_1x_add_altsubject_match;
nm_setting_802_1x_add_eap_method;
nm_setting_802_1x_add_phase2_altsubject_match;
nm_setting_802_1x_ck_format_get_type;
nm_setting_802_1x_ck_scheme_get_type;
nm_setting_802_1x_clear_altsubject_matches;
nm_setting_802_1x_clear_eap_methods;
nm_setting_802_1x_clear_phase2_altsubject_matches;
nm_setting_802_1x_get_altsubject_match;
nm_setting_802_1x_get_anonymous_identity;
nm_setting_802_1x_get_ca_cert_blob;
nm_setting_802_1x_get_ca_cert_path;
nm_setting_802_1x_get_ca_cert_scheme;
nm_setting_802_1x_get_ca_path;
nm_setting_802_1x_get_client_cert_blob;
nm_setting_802_1x_get_client_cert_path;
nm_setting_802_1x_get_client_cert_scheme;
nm_setting_802_1x_get_eap_method;
nm_setting_802_1x_get_identity;
nm_setting_802_1x_get_num_altsubject_matches;
nm_setting_802_1x_get_num_eap_methods;
nm_setting_802_1x_get_num_phase2_altsubject_matches;
nm_setting_802_1x_get_pac_file;
nm_setting_802_1x_get_password;
nm_setting_802_1x_get_password_flags;
nm_setting_802_1x_get_password_raw;
nm_setting_802_1x_get_password_raw_flags;
nm_setting_802_1x_get_phase1_fast_provisioning;
nm_setting_802_1x_get_phase1_peaplabel;
nm_setting_802_1x_get_phase1_peapver;
nm_setting_802_1x_get_phase2_altsubject_match;
nm_setting_802_1x_get_phase2_auth;
nm_setting_802_1x_get_phase2_autheap;
nm_setting_802_1x_get_phase2_ca_cert_blob;
nm_setting_802_1x_get_phase2_ca_cert_path;
nm_setting_802_1x_get_phase2_ca_cert_scheme;
nm_setting_802_1x_get_phase2_ca_path;
nm_setting_802_1x_get_phase2_client_cert_blob;
nm_setting_802_1x_get_phase2_client_cert_path;
nm_setting_802_1x_get_phase2_client_cert_scheme;
nm_setting_802_1x_get_phase2_private_key_blob;
nm_setting_802_1x_get_phase2_private_key_format;
nm_setting_802_1x_get_phase2_private_key_password;
nm_setting_802_1x_get_phase2_private_key_password_flags;
nm_setting_802_1x_get_phase2_private_key_path;
nm_setting_802_1x_get_phase2_private_key_scheme;
nm_setting_802_1x_get_phase2_subject_match;
nm_setting_802_1x_get_pin;
nm_setting_802_1x_get_pin_flags;
nm_setting_802_1x_get_private_key_blob;
nm_setting_802_1x_get_private_key_format;
nm_setting_802_1x_get_private_key_password;
nm_setting_802_1x_get_private_key_password_flags;
nm_setting_802_1x_get_private_key_path;
nm_setting_802_1x_get_private_key_scheme;
nm_setting_802_1x_get_subject_match;
nm_setting_802_1x_get_system_ca_certs;
nm_setting_802_1x_get_type;
nm_setting_802_1x_new;
nm_setting_802_1x_remove_altsubject_match;
nm_setting_802_1x_remove_altsubject_match_by_value;
nm_setting_802_1x_remove_eap_method;
nm_setting_802_1x_remove_eap_method_by_value;
nm_setting_802_1x_remove_phase2_altsubject_match;
nm_setting_802_1x_remove_phase2_altsubject_match_by_value;
nm_setting_802_1x_set_ca_cert;
nm_setting_802_1x_set_client_cert;
nm_setting_802_1x_set_phase2_ca_cert;
nm_setting_802_1x_set_phase2_client_cert;
nm_setting_802_1x_set_phase2_private_key;
nm_setting_802_1x_set_private_key;
nm_setting_adsl_get_encapsulation;
nm_setting_adsl_get_password;
nm_setting_adsl_get_password_flags;
nm_setting_adsl_get_protocol;
nm_setting_adsl_get_type;
nm_setting_adsl_get_username;
nm_setting_adsl_get_vci;
nm_setting_adsl_get_vpi;
nm_setting_adsl_new;
nm_setting_bluetooth_get_bdaddr;
nm_setting_bluetooth_get_connection_type;
nm_setting_bluetooth_get_type;
nm_setting_bluetooth_new;
nm_setting_bond_add_option;
nm_setting_bond_get_num_options;
nm_setting_bond_get_option;
nm_setting_bond_get_option_by_name;
nm_setting_bond_get_option_default;
nm_setting_bond_get_type;
nm_setting_bond_get_valid_options;
nm_setting_bond_new;
nm_setting_bond_remove_option;
nm_setting_bond_validate_option;
nm_setting_bridge_get_ageing_time;
nm_setting_bridge_get_forward_delay;
nm_setting_bridge_get_hello_time;
nm_setting_bridge_get_mac_address;
nm_setting_bridge_get_max_age;
nm_setting_bridge_get_priority;
nm_setting_bridge_get_stp;
nm_setting_bridge_get_type;
nm_setting_bridge_new;
nm_setting_bridge_port_get_hairpin_mode;
nm_setting_bridge_port_get_path_cost;
nm_setting_bridge_port_get_priority;
nm_setting_bridge_port_get_type;
nm_setting_bridge_port_new;
nm_setting_cdma_get_number;
nm_setting_cdma_get_password;
nm_setting_cdma_get_password_flags;
nm_setting_cdma_get_type;
nm_setting_cdma_get_username;
nm_setting_cdma_new;
nm_setting_compare;
nm_setting_compare_flags_get_type;
nm_setting_connection_add_permission;
nm_setting_connection_add_secondary;
nm_setting_connection_get_autoconnect;
libnm: add NMSettingConnection:autoconnect-priority setting The autoconnect priority has only any relevance, if the connection is autoconnect too. The priority defaults to zero, with higher numbers meaning preferred. The valid range is limited to [-999,999]. Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-25 20:39:40 +02:00
nm_setting_connection_get_autoconnect_priority;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_connection_get_connection_type;
nm_setting_connection_get_gateway_ping_timeout;
nm_setting_connection_get_id;
nm_setting_connection_get_interface_name;
nm_setting_connection_get_master;
nm_setting_connection_get_num_permissions;
nm_setting_connection_get_num_secondaries;
nm_setting_connection_get_permission;
nm_setting_connection_get_read_only;
nm_setting_connection_get_secondary;
nm_setting_connection_get_slave_type;
nm_setting_connection_get_timestamp;
nm_setting_connection_get_type;
nm_setting_connection_get_uuid;
nm_setting_connection_get_zone;
nm_setting_connection_is_slave_type;
nm_setting_connection_new;
nm_setting_connection_permissions_user_allowed;
nm_setting_connection_remove_permission;
nm_setting_connection_remove_permission_by_value;
nm_setting_connection_remove_secondary;
nm_setting_connection_remove_secondary_by_value;
nm_setting_dcb_flags_get_type;
nm_setting_dcb_get_app_fcoe_flags;
nm_setting_dcb_get_app_fcoe_mode;
nm_setting_dcb_get_app_fcoe_priority;
nm_setting_dcb_get_app_fip_flags;
nm_setting_dcb_get_app_fip_priority;
nm_setting_dcb_get_app_iscsi_flags;
nm_setting_dcb_get_app_iscsi_priority;
nm_setting_dcb_get_priority_bandwidth;
nm_setting_dcb_get_priority_flow_control;
nm_setting_dcb_get_priority_flow_control_flags;
nm_setting_dcb_get_priority_group_bandwidth;
nm_setting_dcb_get_priority_group_flags;
nm_setting_dcb_get_priority_group_id;
nm_setting_dcb_get_priority_strict_bandwidth;
nm_setting_dcb_get_priority_traffic_class;
nm_setting_dcb_get_type;
nm_setting_dcb_new;
nm_setting_dcb_set_priority_bandwidth;
nm_setting_dcb_set_priority_flow_control;
nm_setting_dcb_set_priority_group_bandwidth;
nm_setting_dcb_set_priority_group_id;
nm_setting_dcb_set_priority_strict_bandwidth;
nm_setting_dcb_set_priority_traffic_class;
nm_setting_diff;
nm_setting_diff_result_get_type;
nm_setting_duplicate;
nm_setting_enumerate_values;
nm_setting_generic_get_type;
nm_setting_generic_new;
libnm: fix nm-setting-docs.xml property types Add nm_setting_get_dbus_property_type(), and use this to get the correct type for properties in nm-seting-docs.xml, in situations where the D-Bus and GObject property types don't match. In the case of enum/flags-valued properties, give both the enum name and the underlying D-Bus type.
2014-11-16 16:13:06 -05:00
nm_setting_get_dbus_property_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_get_name;
nm_setting_get_secret_flags;
nm_setting_get_type;
nm_setting_gsm_get_apn;
nm_setting_gsm_get_home_only;
nm_setting_gsm_get_network_id;
nm_setting_gsm_get_number;
nm_setting_gsm_get_password;
nm_setting_gsm_get_password_flags;
nm_setting_gsm_get_pin;
nm_setting_gsm_get_pin_flags;
nm_setting_gsm_get_type;
nm_setting_gsm_get_username;
nm_setting_gsm_new;
nm_setting_infiniband_get_mac_address;
nm_setting_infiniband_get_mtu;
nm_setting_infiniband_get_p_key;
nm_setting_infiniband_get_parent;
nm_setting_infiniband_get_transport_mode;
nm_setting_infiniband_get_type;
libnm-core: drop nm_{setting,connection}_get_virtual_iface_name() Since we enforce the fact that bond, bridge, team, and vlan interface-name properties match NMSettingConnection:interface-name, nm_connection_get_virtual_iface_name() can be replaced with nm_connection_get_interface_name() basically everywhere. The one place this doesn't work is with InfiniBand partitions (where get_virtual_iface_name() was actually computing the name), but for the most part we only need to care about the interface names of InfiniBand partitions in places where we also already need to do some other InfiniBand-specific handling as well, so we can use an InfiniBand-specific method (nm_setting_infiniband_get_virtual_interface_name()) to get it. (Also, while updating nm_device_get_virtual_device_description(), fix it to handle InfiniBand partitions too.)
2014-08-07 10:47:56 -04:00
nm_setting_infiniband_get_virtual_interface_name;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_infiniband_new;
nm_setting_ip4_config_get_dhcp_client_id;
nm_setting_ip4_config_get_type;
nm_setting_ip4_config_new;
nm_setting_ip6_config_get_ip6_privacy;
nm_setting_ip6_config_get_type;
nm_setting_ip6_config_new;
nm_setting_ip6_config_privacy_get_type;
libnm-core: extract NMSettingIPConfig superclass out of IP4, IP6 classes Split a base NMSettingIPConfig class out of NMSettingIP4Config and NMSettingIP6Config, and update things accordingly. Further simplifications of now-redundant IPv4-vs-IPv6 code are possible, and should happen in the future.
2014-10-19 17:30:10 -04:00
nm_setting_ip_config_add_address;
nm_setting_ip_config_add_dns;
nm_setting_ip_config_add_dns_search;
nm_setting_ip_config_add_route;
nm_setting_ip_config_clear_addresses;
nm_setting_ip_config_clear_dns;
nm_setting_ip_config_clear_dns_searches;
nm_setting_ip_config_clear_routes;
nm_setting_ip_config_get_address;
nm_setting_ip_config_get_dhcp_hostname;
nm_setting_ip_config_get_dhcp_send_hostname;
nm_setting_ip_config_get_dns;
nm_setting_ip_config_get_dns_search;
libnm-core: add NMSettingIPConfig:gateway, drop NMIPAddress:gateway The gateway is a global property of the IPv4/IPv6 configuration, not an attribute of any particular address. So represent it as such in the API; remove the gateway from NMIPAddress, and add it to NMSettingIPConfig. Behind the scenes, the gateway is still serialized along with the first address in NMSettingIPConfig:addresses, and is deserialized from that if the settings dictionary doesn't contain a 'gateway' key. Adjust nmcli's interactive mode to prompt for IP addresses and gateway separately. (Patch partly from Jirka Klimeš.)
2014-10-20 21:30:56 -04:00
nm_setting_ip_config_get_gateway;
libnm-core: extract NMSettingIPConfig superclass out of IP4, IP6 classes Split a base NMSettingIPConfig class out of NMSettingIP4Config and NMSettingIP6Config, and update things accordingly. Further simplifications of now-redundant IPv4-vs-IPv6 code are possible, and should happen in the future.
2014-10-19 17:30:10 -04:00
nm_setting_ip_config_get_ignore_auto_dns;
nm_setting_ip_config_get_ignore_auto_routes;
nm_setting_ip_config_get_may_fail;
nm_setting_ip_config_get_method;
nm_setting_ip_config_get_never_default;
nm_setting_ip_config_get_num_addresses;
nm_setting_ip_config_get_num_dns;
nm_setting_ip_config_get_num_dns_searches;
nm_setting_ip_config_get_num_routes;
nm_setting_ip_config_get_route;
libnm: add NMSettingIPConfig:route-metric https://bugzilla.gnome.org/show_bug.cgi?id=735512 https://bugzilla.redhat.com/show_bug.cgi?id=663730 Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-27 19:57:24 +02:00
nm_setting_ip_config_get_route_metric;
libnm-core: extract NMSettingIPConfig superclass out of IP4, IP6 classes Split a base NMSettingIPConfig class out of NMSettingIP4Config and NMSettingIP6Config, and update things accordingly. Further simplifications of now-redundant IPv4-vs-IPv6 code are possible, and should happen in the future.
2014-10-19 17:30:10 -04:00
nm_setting_ip_config_get_type;
nm_setting_ip_config_remove_address;
nm_setting_ip_config_remove_address_by_value;
nm_setting_ip_config_remove_dns;
nm_setting_ip_config_remove_dns_by_value;
nm_setting_ip_config_remove_dns_search;
nm_setting_ip_config_remove_dns_search_by_value;
nm_setting_ip_config_remove_route;
nm_setting_ip_config_remove_route_by_value;
libnm-core: move some fake NMConnection methods over to NMSetting nm_connection_lookup_setting_type() and nm_connection_lookup_setting_type_by_quark() have nothing to do with NMConnection. So move them to NMSetting (and rename them to nm_setting_lookup_type() and nm_setting_lookup_type_by_quark()).
2014-08-12 17:25:26 -04:00
nm_setting_lookup_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_olpc_mesh_get_channel;
nm_setting_olpc_mesh_get_dhcp_anycast_address;
nm_setting_olpc_mesh_get_ssid;
nm_setting_olpc_mesh_get_type;
nm_setting_olpc_mesh_new;
nm_setting_ppp_get_baud;
nm_setting_ppp_get_crtscts;
nm_setting_ppp_get_lcp_echo_failure;
nm_setting_ppp_get_lcp_echo_interval;
nm_setting_ppp_get_mppe_stateful;
nm_setting_ppp_get_mru;
nm_setting_ppp_get_mtu;
nm_setting_ppp_get_no_vj_comp;
nm_setting_ppp_get_noauth;
nm_setting_ppp_get_nobsdcomp;
nm_setting_ppp_get_nodeflate;
nm_setting_ppp_get_refuse_chap;
nm_setting_ppp_get_refuse_eap;
nm_setting_ppp_get_refuse_mschap;
nm_setting_ppp_get_refuse_mschapv2;
nm_setting_ppp_get_refuse_pap;
nm_setting_ppp_get_require_mppe;
nm_setting_ppp_get_require_mppe_128;
nm_setting_ppp_get_type;
nm_setting_ppp_new;
nm_setting_pppoe_get_password;
nm_setting_pppoe_get_password_flags;
nm_setting_pppoe_get_service;
nm_setting_pppoe_get_type;
nm_setting_pppoe_get_username;
nm_setting_pppoe_new;
nm_setting_secret_flags_get_type;
nm_setting_serial_get_baud;
nm_setting_serial_get_bits;
nm_setting_serial_get_parity;
nm_setting_serial_get_send_delay;
nm_setting_serial_get_stopbits;
nm_setting_serial_get_type;
nm_setting_serial_new;
libnm-core: make NMSettingSerial:parity an enum NMSettingSerial:parity was defined as a char-typed property that could have the (case-sensitive!) values 'n', 'E', or 'o'. This is zany. Add an NMSettingSerialParity enum, and use that instead.
2014-09-24 09:12:46 -04:00
nm_setting_serial_parity_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_setting_set_secret_flags;
nm_setting_team_get_config;
nm_setting_team_get_type;
nm_setting_team_new;
nm_setting_team_port_get_config;
nm_setting_team_port_get_type;
nm_setting_team_port_new;
nm_setting_to_string;
nm_setting_verify;
nm_setting_vlan_add_priority;
nm_setting_vlan_add_priority_str;
nm_setting_vlan_clear_priorities;
nm_setting_vlan_get_flags;
nm_setting_vlan_get_id;
nm_setting_vlan_get_num_priorities;
nm_setting_vlan_get_parent;
nm_setting_vlan_get_priority;
nm_setting_vlan_get_type;
nm_setting_vlan_new;
nm_setting_vlan_remove_priority;
nm_setting_vlan_remove_priority_by_value;
nm_setting_vlan_remove_priority_str_by_value;
nm_setting_vpn_add_data_item;
nm_setting_vpn_add_secret;
nm_setting_vpn_foreach_data_item;
nm_setting_vpn_foreach_secret;
nm_setting_vpn_get_data_item;
nm_setting_vpn_get_num_data_items;
nm_setting_vpn_get_num_secrets;
nm_setting_vpn_get_secret;
nm_setting_vpn_get_service_type;
nm_setting_vpn_get_type;
nm_setting_vpn_get_user_name;
nm_setting_vpn_new;
nm_setting_vpn_remove_data_item;
nm_setting_vpn_remove_secret;
nm_setting_wimax_get_mac_address;
nm_setting_wimax_get_network_name;
nm_setting_wimax_get_type;
nm_setting_wimax_new;
nm_setting_wired_add_mac_blacklist_item;
nm_setting_wired_add_s390_option;
nm_setting_wired_clear_mac_blacklist_items;
nm_setting_wired_get_auto_negotiate;
nm_setting_wired_get_cloned_mac_address;
nm_setting_wired_get_duplex;
nm_setting_wired_get_mac_address;
nm_setting_wired_get_mac_address_blacklist;
nm_setting_wired_get_mac_blacklist_item;
nm_setting_wired_get_mtu;
nm_setting_wired_get_num_mac_blacklist_items;
nm_setting_wired_get_num_s390_options;
nm_setting_wired_get_port;
nm_setting_wired_get_s390_nettype;
nm_setting_wired_get_s390_option;
nm_setting_wired_get_s390_option_by_key;
nm_setting_wired_get_s390_subchannels;
nm_setting_wired_get_speed;
nm_setting_wired_get_type;
nm_setting_wired_get_valid_s390_options;
nm_setting_wired_new;
nm_setting_wired_remove_mac_blacklist_item;
nm_setting_wired_remove_mac_blacklist_item_by_value;
nm_setting_wired_remove_s390_option;
nm_setting_wireless_add_mac_blacklist_item;
nm_setting_wireless_add_seen_bssid;
nm_setting_wireless_ap_security_compatible;
nm_setting_wireless_clear_mac_blacklist_items;
nm_setting_wireless_get_band;
nm_setting_wireless_get_bssid;
nm_setting_wireless_get_channel;
nm_setting_wireless_get_cloned_mac_address;
nm_setting_wireless_get_hidden;
nm_setting_wireless_get_mac_address;
nm_setting_wireless_get_mac_address_blacklist;
nm_setting_wireless_get_mac_blacklist_item;
nm_setting_wireless_get_mode;
nm_setting_wireless_get_mtu;
nm_setting_wireless_get_num_mac_blacklist_items;
nm_setting_wireless_get_num_seen_bssids;
nm_setting_wireless_get_rate;
nm_setting_wireless_get_seen_bssid;
nm_setting_wireless_get_ssid;
nm_setting_wireless_get_tx_power;
nm_setting_wireless_get_type;
nm_setting_wireless_new;
nm_setting_wireless_remove_mac_blacklist_item;
nm_setting_wireless_remove_mac_blacklist_item_by_value;
nm_setting_wireless_security_add_group;
nm_setting_wireless_security_add_pairwise;
nm_setting_wireless_security_add_proto;
nm_setting_wireless_security_clear_groups;
nm_setting_wireless_security_clear_pairwise;
nm_setting_wireless_security_clear_protos;
nm_setting_wireless_security_get_auth_alg;
nm_setting_wireless_security_get_group;
nm_setting_wireless_security_get_key_mgmt;
nm_setting_wireless_security_get_leap_password;
nm_setting_wireless_security_get_leap_password_flags;
nm_setting_wireless_security_get_leap_username;
nm_setting_wireless_security_get_num_groups;
nm_setting_wireless_security_get_num_pairwise;
nm_setting_wireless_security_get_num_protos;
nm_setting_wireless_security_get_pairwise;
nm_setting_wireless_security_get_proto;
nm_setting_wireless_security_get_psk;
nm_setting_wireless_security_get_psk_flags;
nm_setting_wireless_security_get_type;
nm_setting_wireless_security_get_wep_key;
nm_setting_wireless_security_get_wep_key_flags;
nm_setting_wireless_security_get_wep_key_type;
nm_setting_wireless_security_get_wep_tx_keyidx;
nm_setting_wireless_security_new;
nm_setting_wireless_security_remove_group;
nm_setting_wireless_security_remove_group_by_value;
nm_setting_wireless_security_remove_pairwise;
nm_setting_wireless_security_remove_pairwise_by_value;
nm_setting_wireless_security_remove_proto;
nm_setting_wireless_security_remove_proto_by_value;
nm_setting_wireless_security_set_wep_key;
libnm-core, settings: move NMSettingsError to nm-errors Move the definition of NMSettingsError to nm-errors, register it with D-Bus, and verify in the tests that it maps correctly. Remove a few unused error codes, simplify a few others, and rename GENERAL to FAILED and HOSTNAME_INVALID to INVALID_HOSTNAME, for consistency.
2014-10-15 15:27:25 -04:00
nm_settings_error_get_type;
nm_settings_error_quark;
libnm-core, libnm, core: make NMConnection an interface The fact that NMRemoteConnection has to be an NMConnection and therefore can't be an NMObject means that it needs to reimplement bits of NMObject functionality (and likewise NMObject needs some special magic to deal with it). Likewise, we will need a daemon-side equivalent of NMObject as part of the gdbus port, and we would want NMSettingsConnection to be able to inherit from this as well. Solve this problem by making NMConnection into an interface, and having NMRemoteConnection and NMSettingsConnection implement it. (We use some hacks to keep the GHashTable of NMSettings objects inside nm-connection.c rather than having to be implemented by the implementations.) Since NMConnection is no longer an instantiable type, this adds NMSimpleConnection to replace the various non-D-Bus-based uses of NMConnection throughout the code. nm_connection_new() becomes nm_simple_connection_new(), nm_connection_new_from_hash() becomes nm_simple_connection_new_from_hash(), and nm_connection_duplicate() becomes nm_simple_connection_new_clone().
2014-08-13 14:34:29 -04:00
nm_simple_connection_get_type;
nm_simple_connection_new;
nm_simple_connection_new_clone;
libnm-core: rename NMConnection to/from_hash methods Rename nm_connection_to_hash() to nm_connection_to_dbus(), and nm_connection_new_from_hash() to nm_connection_new_from_dbus(). In addition to clarifying that this is specifically the D-Bus serialization format, these names will also work better in the GDBus-based future where the serialization format is GVariant, not GHashTable. Also, move NMSettingHashFlags to nm-connection.h, and rename it NMConnectionSerializationFlags.
2014-08-06 19:35:31 -04:00
nm_simple_connection_new_from_dbus;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_state_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_ap_mode_security_valid;
nm_utils_bin2hexstr;
nm_utils_check_virtual_device_compatibility;
nm_utils_escape_ssid;
libnm-core: add nm_utils_file_is_certificate() and _file_is_private_key() Add nm-utils methods to check if a file is a certificate or private key file. nm-applet currently has its own internal versions of these, but they ended up having to duplicate a bunch of logic that we already have in crypto.c.
2014-10-30 11:15:44 -04:00
nm_utils_file_is_certificate;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_file_is_pkcs12;
libnm-core: add nm_utils_file_is_certificate() and _file_is_private_key() Add nm-utils methods to check if a file is a certificate or private key file. nm-applet currently has its own internal versions of these, but they ended up having to duplicate a bunch of logic that we already have in crypto.c.
2014-10-30 11:15:44 -04:00
nm_utils_file_is_private_key;
libnm: add function nm_utils_file_search_in_paths() We now also use a similar function in VPN plugins. It makes sense to provide a generic implementation in libnm. Signed-off-by: Thomas Haller <thaller@redhat.com> https://bugzilla.gnome.org/show_bug.cgi?id=740783
2014-11-25 23:01:55 +01:00
nm_utils_file_search_in_paths;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_hexstr2bin;
nm_utils_hwaddr_atoba;
nm_utils_hwaddr_aton;
libnm-core: add nm_utils_hwaddr_canonical() Add a helper function for converting hardware addresses to canonical form.
2014-10-28 08:32:25 -04:00
nm_utils_hwaddr_canonical;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_hwaddr_len;
libnm-core, etc: add nm_utils_hwaddr_matches() Add nm_utils_hwaddr_matches(), for comparing hardware addresses for equality, allowing either binary or ASCII hardware addresses to be passed, and handling the special rules for InfiniBand hardware addresses automatically. Update code to use it.
2014-06-16 11:30:47 -04:00
nm_utils_hwaddr_matches;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_hwaddr_ntoa;
nm_utils_hwaddr_valid;
nm_utils_iface_valid_name;
nm_utils_inet4_ntop;
nm_utils_inet6_ntop;
libnm-core: add GVariant-based versions of IP structure-manipulating utilities
2014-09-06 17:57:39 -04:00
nm_utils_ip4_addresses_from_variant;
nm_utils_ip4_addresses_to_variant;
nm_utils_ip4_dns_from_variant;
nm_utils_ip4_dns_to_variant;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_ip4_get_default_prefix;
nm_utils_ip4_netmask_to_prefix;
nm_utils_ip4_prefix_to_netmask;
libnm-core: add GVariant-based versions of IP structure-manipulating utilities
2014-09-06 17:57:39 -04:00
nm_utils_ip4_routes_from_variant;
nm_utils_ip4_routes_to_variant;
nm_utils_ip6_addresses_from_variant;
nm_utils_ip6_addresses_to_variant;
nm_utils_ip6_dns_from_variant;
nm_utils_ip6_dns_to_variant;
nm_utils_ip6_routes_from_variant;
nm_utils_ip6_routes_to_variant;
libnm-core, all: merge IPv4 and IPv6 address/route types Merge NMIP4Address and NMIP6Address into NMIPAddress, and NMIP4Route and NMIP6Route into NMIPRoute. The new types represent IP addresses as strings, rather than in binary, and so are address-family agnostic.
2014-09-16 16:42:46 -04:00
nm_utils_ipaddr_valid;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_is_empty_ssid;
nm_utils_is_uuid;
nm_utils_same_ssid;
nm_utils_security_type_get_type;
nm_utils_security_valid;
nm_utils_ssid_to_utf8;
nm_utils_uuid_generate;
nm_utils_wep_key_valid;
nm_utils_wifi_channel_to_freq;
nm_utils_wifi_find_next_channel;
nm_utils_wifi_freq_to_channel;
nm_utils_wifi_is_channel_valid;
libnm-core: add nm_utils_wifi_strength_bars(), use it in nmcli and nmtui Add nm_utils_wifi_strength_bars(), which figures out whether the terminal can display graphical wifi strength bars, and converts a numerical value to the appropriate Unicode or ASCII characters. This also now takes into consideration the fact that the console font doesn't contain all of the necessary characters, so we can't display the graphical bars there. (rh #1131491)
2014-09-19 16:51:07 -04:00
nm_utils_wifi_strength_bars;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_utils_wpa_psk_valid;
nm_vlan_flags_get_type;
nm_vlan_priority_map_get_type;
nm_vpn_connection_get_banner;
nm_vpn_connection_get_type;
nm_vpn_connection_get_vpn_state;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_vpn_connection_state_get_type;
nm_vpn_connection_state_reason_get_type;
libnm: rename NMVpnPluginUiInterface, add to NetworkManager.h Rename NMVpnPluginUiInterface to NMVpnEditorPlugin (to clarify that it's unrelated to NMVpnPlugin), and add it to NetworkManager.h. Rename NMVpnPluginUiWidgetInterface to NMVpnEditor, because it's not a widget, and will soon be used for non-gui editing too. (Also, add a placeholder for the method that non-gui editing will use.) Fix the typedefs to not mix up the (dummy) NMVpnEditorPlugin and NMVpnEditor types with the types of their interface structs. Update to use G_DEFINE_INTERFACE. Drop NMVpnPluginUiInterfaceProp; it doesn't matter what codes plugin implementations use for the interface properties that they implement.
2014-11-05 11:01:09 -05:00
nm_vpn_editor_get_type;
nm_vpn_editor_get_widget;
nm_vpn_editor_plugin_capability_get_type;
nm_vpn_editor_plugin_export;
nm_vpn_editor_plugin_get_capabilities;
nm_vpn_editor_plugin_get_editor;
nm_vpn_editor_plugin_get_suggested_filename;
nm_vpn_editor_plugin_get_type;
nm_vpn_editor_plugin_import;
nm_vpn_editor_update_connection;
libnm: merge libnm-vpn into libnm There's not much point in keeping them separate: all existing libnm-glib-vpn users also link against libnm-glib, and the amount of extra code added to libnm by merging in libnm-vpn is negligible. Additionally, nm-vpn-plugin will later need access to some libnm-internal APIs. So, merge them together.
2014-09-10 15:46:46 -04:00
nm_vpn_plugin_error_get_type;
nm_vpn_plugin_error_quark;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_vpn_plugin_failure_get_type;
libnm,vpn: restore export of deprecated NMVpnPluginOld symbols Deprecated of course, but shouldn't have been removed from the ABI. Fixes: 867227dd4aac8371b3cacc366b32a3fa96eba42a
2016-01-20 10:53:54 -06:00
nm_vpn_plugin_old_disconnect;
nm_vpn_plugin_old_failure;
nm_vpn_plugin_old_get_connection;
nm_vpn_plugin_old_get_secret_flags;
nm_vpn_plugin_old_get_state;
nm_vpn_plugin_old_get_type;
nm_vpn_plugin_old_read_vpn_details;
nm_vpn_plugin_old_secrets_required;
nm_vpn_plugin_old_set_ip4_config;
nm_vpn_plugin_old_set_login_banner;
nm_vpn_plugin_old_set_state;
libnm: add NetworkManager.h and NetworkManagerVPN.h to enum-types
2014-06-26 16:47:46 -04:00
nm_vpn_service_state_get_type;
libnm: add libnm/libnm-core (part 2) This fixes up the code from the previous "clean" import, and adds build infrastructure. [There are two slightly orthogonal sets of changes in this patch. First, the files added in the previous commit were modified as followed: # Replace internal references to "libnm-util" and "libnm-glib" with "libnm" perl -pi -e 's/libnm-(util|glib)/libnm/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] # Fix includes of the enum-types files perl -pi -e 's/nm-utils-enum-types/nm-core-enum-types/;' libnm-core/*.[ch] libnm-core/tests/*.[ch] libnm/*.[ch] libnm/tests/*.[ch] perl -pi -e 's/nm-glib-enum-types/nm-enum-types/;' libnm/*.[ch] libnm/tests/*.[ch] # Fix some python example code perl -pi -e 's/import NMClient/import NM/;' -e 's/NMClient.Client\(\)/NM.Client()/;' libnm/nm-client.c Then, the build infrastructure was added (without further modifying any existing files in libnm-core or libnm.) Note: to regenerate libnm.ver after rebase: (head -2 libnm-util/libnm-util.ver; (grep -h '\s'nm_ libnm-util/libnm-util.ver libnm-glib/libnm-glib.ver | env LANG=C sort); tail -3 libnm-util/libnm-util.ver) > libnm/libnm.ver ]
2014-07-04 13:26:57 -04:00
nm_wep_key_type_get_type;
nm_wimax_nsp_connection_valid;
nm_wimax_nsp_filter_connections;
nm_wimax_nsp_get_name;
nm_wimax_nsp_get_network_type;
nm_wimax_nsp_get_signal_quality;
nm_wimax_nsp_get_type;
nm_wimax_nsp_network_type_get_type;
libnm: remove __libnm_local section from version script I had argued for putting the local symbols in their own section, since it doesn't make sense to have local symbols introduced in 1.2 in the libnm_1_0_0 section... but apparently even if the section has no exported symbols, rpm's find-provides still picks it up if it's there, creating an ugly additional "provides" for libnm. So get rid of that.
2014-12-15 15:49:39 -05:00
local:
*;
};
libnm: fix versioning on new APIs, bump soname The newly added bond mode APIs in nm-utils will be new in 1.2, so mark them as such in the headers and docs, move them to a new section in libnm.ver. Since we're adding the new section to libnm.ver, this also seems like a good time to bump the soname.
2015-01-15 16:42:26 -05:00
libnm: backport autoconnect-slaves symbols to libnm_1_0_4 https://bugzilla.gnome.org/show_bug.cgi?id=751535
2015-06-26 11:44:15 +02:00
libnm_1_0_4 {
#nm_setting_connection_autoconnect_slaves_get_type@libnm_1_0_4;
#nm_setting_connection_get_autoconnect_slaves@libnm_1_0_4;
} libnm_1_0_0;
libnm: backport symbols for metered connections support to 1.0.6 Backport to 1.0.6 the following symbols: - nm_device_get_metered - nm_metered_get_type - nm_setting_connection_get_metered
2015-07-21 19:02:12 +02:00
libnm_1_0_6 {
libnm: backport symbol nm_access_point_get_last_seen@libnm_1_0_6 nm_access_point_get_last_seen() was backported for 1.0.6 in commit fade4ded37e16e44ff75947dd22d054789c5a2a7.
2015-08-09 12:12:43 +02:00
#nm_access_point_get_last_seen@libnm_1_0_6;
libnm: backport symbols for metered connections support to 1.0.6 Backport to 1.0.6 the following symbols: - nm_device_get_metered - nm_metered_get_type - nm_setting_connection_get_metered
2015-07-21 19:02:12 +02:00
#nm_device_get_metered@libnm_1_0_6;
libnm: symbols for request scanning backported to 1.0.6 Backport to 1.0.6 the following symbols: - nm_device_wifi_request_scan_options - nm_device_wifi_request_scan_options_async Backported by commit 91c0555afaac57234744f42024d95bde46ba170e
2015-08-14 14:24:16 +02:00
#nm_device_wifi_request_scan_options@libnm_1_0_6;
#nm_device_wifi_request_scan_options_async@libnm_1_0_6;
libnm: backport symbols for metered connections support to 1.0.6 Backport to 1.0.6 the following symbols: - nm_device_get_metered - nm_metered_get_type - nm_setting_connection_get_metered
2015-07-21 19:02:12 +02:00
#nm_metered_get_type@libnm_1_0_6;
#nm_setting_connection_get_metered@libnm_1_0_6;
libnm: backport NMSettingWired Wake-on-LAN symbols to 1.0.6 Backport to 1.0.6 the following symbols: - nm_setting_wired_get_wake_on_lan - nm_setting_wired_get_wake_on_lan_password - nm_setting_wired_wake_on_lan_get_type added to 1.0.6 with commit d449d823046ac02f19d086575a19be7f40278bd0
2015-08-21 18:56:47 +02:00
#nm_setting_wired_get_wake_on_lan@libnm_1_0_6;
#nm_setting_wired_get_wake_on_lan_password@libnm_1_0_6;
#nm_setting_wired_wake_on_lan_get_type@libnm_1_0_6;
libnm: backport enum conversion utilities to 1.0.6 Backport to 1.0.6 the following symbols: - nm_utils_enum_from_str - nm_utils_enum_to_str added to 1.0.6 with commit f4ce6760e0ebb66aee3df35e9618be656355f318
2015-08-21 18:44:32 +02:00
#nm_utils_enum_from_str@libnm_1_0_6;
#nm_utils_enum_to_str@libnm_1_0_6;
libnm: symbols for getting Wi-Fi frequencies have been backported to 1.0.6 Backport to 1.0.6 the following symbols: - nm_utils_wifi_2ghz_freqs; - nm_utils_wifi_5ghz_freqs; Backported by commit 77bf69c3dc6ef6c17741cdf0f81af911378596e0
2015-08-21 10:22:31 +02:00
#nm_utils_wifi_2ghz_freqs@libnm_1_0_6;
#nm_utils_wifi_5ghz_freqs@libnm_1_0_6;
libnm: backport symbols for metered connections support to 1.0.6 Backport to 1.0.6 the following symbols: - nm_device_get_metered - nm_metered_get_type - nm_setting_connection_get_metered
2015-07-21 19:02:12 +02:00
} libnm_1_0_4;
libnm: fix versioning on new APIs, bump soname The newly added bond mode APIs in nm-utils will be new in 1.2, so mark them as such in the headers and docs, move them to a new section in libnm.ver. Since we're adding the new section to libnm.ver, this also seems like a good time to bump the soname.
2015-01-15 16:42:26 -05:00
libnm_1_2_0 {
global:
libnm: add Wi-Fi AP 'last-seen' property
2015-04-27 12:50:39 -05:00
nm_access_point_get_last_seen;
libnm: keep symbols sorted in libnm.ver
2016-01-11 09:32:10 +01:00
nm_client_get_all_devices;
libnm-core: add NMSettingIPTunnel Add a generic NMSettingTunnel which describes properties of tunnels over IPv4 and IPv6 (GRE, SIT, IPIP, IPIP6, IP6GRE, etc.). Since those tunnel types all have similar properties it makes sense to have a single setting type for them.
2015-09-01 14:06:00 +02:00
nm_connection_get_setting_ip_tunnel;
libnm-core: add NMSettingMacvlan The setting contains properties that are specific to macvlans and macvtaps.
2015-09-17 18:13:49 +02:00
nm_connection_get_setting_macvlan;
libnm-core: add NMSettingVxlan Add a new NMSettingVxlan which describes properties of VXLAN connections.
2015-10-13 09:09:54 +02:00
nm_connection_get_setting_vxlan;
libnm: add nm_setting_verify_secrets() and nm_connection_verify_secrets() for verifying the secrets, because it is not done in plain nm_setting_verify(). For simple verification of free-form string secrets, _nm_setting_verify_secret_string() helper is used.
2015-11-10 14:36:20 +01:00
nm_connection_verify_secrets;
libnm: add 390-subchannels property to NMDeviceEthernet
2015-09-23 14:55:55 +02:00
nm_device_ethernet_get_s390_subchannels;
libnm: add nm_device_get_applied_connection() function
2016-02-11 12:00:30 +01:00
nm_device_get_applied_connection;
nm_device_get_applied_connection_async;
nm_device_get_applied_connection_finish;
libnm: add LLDP support Add functions to libnm for retrieving a list of LLDP neighbors and accessor functions to get their attributes.
2015-10-07 11:48:44 +02:00
nm_device_get_lldp_neighbors;
core,libnm: add 'metered' property to NMDevice
2015-04-29 16:34:38 +02:00
nm_device_get_metered;
libnm: keep symbols sorted in libnm.ver
2016-01-11 09:32:10 +01:00
nm_device_get_nm_plugin_missing;
libnm: add NMDeviceIPTunnel
2015-11-12 17:46:39 +01:00
nm_device_ip_tunnel_get_encapsulation_limit;
nm_device_ip_tunnel_get_flow_label;
nm_device_ip_tunnel_get_input_key;
nm_device_ip_tunnel_get_local;
nm_device_ip_tunnel_get_mode;
nm_device_ip_tunnel_get_output_key;
nm_device_ip_tunnel_get_parent;
nm_device_ip_tunnel_get_path_mtu_discovery;
nm_device_ip_tunnel_get_remote;
nm_device_ip_tunnel_get_tos;
nm_device_ip_tunnel_get_ttl;
nm_device_ip_tunnel_get_type;
libnm: keep symbols sorted in libnm.ver
2016-01-11 09:32:10 +01:00
nm_device_is_real;
libnm: add NMDeviceMacvlan
2015-12-09 11:51:43 +01:00
nm_device_macvlan_get_hw_address;
nm_device_macvlan_get_mode;
nm_device_macvlan_get_no_promisc;
nm_device_macvlan_get_parent;
nm_device_macvlan_get_tap;
nm_device_macvlan_get_type;
libnm: keep symbols sorted in libnm.ver
2016-01-11 09:32:10 +01:00
nm_device_reapply;
nm_device_reapply_async;
nm_device_reapply_finish;
libnm,libnm-glib: add Device.Managed setter
2015-03-23 13:31:10 +01:00
nm_device_set_managed;
libnm: add NMDeviceTun
2015-09-04 18:11:15 +02:00
nm_device_tun_get_group;
nm_device_tun_get_hw_address;
nm_device_tun_get_mode;
nm_device_tun_get_multi_queue;
nm_device_tun_get_owner;
nm_device_tun_get_no_pi;
nm_device_tun_get_type;
nm_device_tun_get_vnet_hdr;
libnm: add NMDeviceVxlan
2015-10-15 21:57:11 +02:00
nm_device_vxlan_get_ageing;
nm_device_vxlan_get_dst_port;
nm_device_vxlan_get_group;
nm_device_vxlan_get_hw_address;
nm_device_vxlan_get_id;
nm_device_vxlan_get_l2miss;
nm_device_vxlan_get_l3miss;
nm_device_vxlan_get_learning;
nm_device_vxlan_get_limit;
nm_device_vxlan_get_local;
nm_device_vxlan_get_parent;
nm_device_vxlan_get_proxy;
nm_device_vxlan_get_src_port_max;
nm_device_vxlan_get_src_port_min;
nm_device_vxlan_get_tos;
nm_device_vxlan_get_ttl;
nm_device_vxlan_get_type;
libnm: add new functions allowing passing options to RequestScan() D-Bus call nm_device_wifi_request_scan_options() nm_device_wifi_request_scan_options_async()
2015-07-14 09:46:55 +02:00
nm_device_wifi_request_scan_options;
nm_device_wifi_request_scan_options_async;
libnm-core: add NMSettingIPTunnel Add a generic NMSettingTunnel which describes properties of tunnels over IPv4 and IPv6 (GRE, SIT, IPIP, IPIP6, IP6GRE, etc.). Since those tunnel types all have similar properties it makes sense to have a single setting type for them.
2015-09-01 14:06:00 +02:00
nm_ip_tunnel_mode_get_type;
libnm: add LLDP support Add functions to libnm for retrieving a list of LLDP neighbors and accessor functions to get their attributes.
2015-10-07 11:48:44 +02:00
nm_lldp_neighbor_get_attr_names;
nm_lldp_neighbor_get_attr_string_value;
nm_lldp_neighbor_get_attr_type;
nm_lldp_neighbor_get_attr_uint_value;
libnm: define NMLldpNeighbor as boxed type GLib introspection requires all types returned by public functions to be GObjects, basic types or boxed types in order to correctly manage resources. NMLldpNeighbor was a plain struct and GI complained with: Warning: NM: nm_lldp_neighbor_new: return value: Invalid non-constant return of bare structure or union; register as boxed type or (skip) To fix this define NMLldpNeighbor as a boxed type. Fixes: d3d2b494008322a4f1452cf873393ca85166022b
2015-10-16 16:11:42 +02:00
nm_lldp_neighbor_get_type;
libnm: add LLDP support Add functions to libnm for retrieving a list of LLDP neighbors and accessor functions to get their attributes.
2015-10-07 11:48:44 +02:00
nm_lldp_neighbor_new;
nm_lldp_neighbor_ref;
nm_lldp_neighbor_unref;
core,libnm: add 'metered' property to NMDevice
2015-04-29 16:34:38 +02:00
nm_metered_get_type;
libnm: add function nm_setting_802_1x_check_cert_scheme() When setting the certificate glib properties directly, we raise a g_warning() when the binary data is invalid. But since the caller has no access to the validation function, he cannot easily check whether his action will result in a warning. Add nm_setting_802_1x_check_cert_scheme() for that.
2015-02-26 10:12:11 +01:00
nm_setting_802_1x_check_cert_scheme;
libnm-core: add domain-suffix-match properties to NMSetting8021x The new domain-suffix-match and phase2-domain-suffix-match properties can be used to match against a given server domain suffix in the dNSName elements or in the SubjectName CN of the server certificate. Also, add a comment to the old subject-match properties documentation to suggest that they are deprecated and should not be used anymore.
2016-03-03 22:42:35 +01:00
nm_setting_802_1x_get_domain_suffix_match;
nm_setting_802_1x_get_phase2_domain_suffix_match;
libnm-core: add multicast-snooping property to bridge setting
2015-02-20 12:32:23 +01:00
nm_setting_bridge_get_multicast_snooping;
libnm: add autoconnect-slaves property to NMSettingConnection The property is used for controlling whether slaves should be brought up with a master connection. If 0, activating the master will not activate slaves. But if set to 1, activating the master will bring up slaves as well. The property can have the third state (-1), meaning that the value is default. That is either a value set in the configuration file for the property, or 0.
2015-05-06 10:54:35 +02:00
nm_setting_connection_autoconnect_slaves_get_type;
nm_setting_connection_get_autoconnect_slaves;
libnm: add 'lldp' property to NMSettingConnection Add the 'lldp' property to NMSettingConnection, which specifies whether the reception and parsing of LLDP frames to discover neighbor devices should be enabled.
2015-10-07 11:48:30 +02:00
nm_setting_connection_get_lldp;
libnm-core: add 'metered' property to NMSettingConnection Add a 'metered' enum property to NMSettingConnection with possible values: unknown,yes,no. The value indicates the presence of limitations in the amount of traffic flowing through the connection.
2015-04-27 17:45:53 +02:00
nm_setting_connection_get_metered;
libnm: add 'lldp' property to NMSettingConnection Add the 'lldp' property to NMSettingConnection, which specifies whether the reception and parsing of LLDP frames to discover neighbor devices should be enabled.
2015-10-07 11:48:30 +02:00
nm_setting_connection_lldp_get_type;
libnm/wwan: add GSM setting device-id, sim-id, and sim-operator-id properties These properties limit whether the connection applies to a certain WWAN modem based on the modem's device ID or SIM ID (as reported by the WWAN management service), or through the MCC/MNC ID of the operator that issued the SIM card.
2015-10-01 12:44:28 -05:00
nm_setting_gsm_get_device_id;
nm_setting_gsm_get_sim_id;
nm_setting_gsm_get_sim_operator_id;
libnm-core: add a 'dhcp-fqdn' property to NMSettingIP4Config The property contains the fully qualified domain name to be sent to DHCP server using the FQDN option. The property is mutually exclusive with 'dhcp-hostname'.
2015-10-13 14:10:01 +02:00
nm_setting_ip4_config_get_dhcp_fqdn;
setting-ip6-config: add addr-gen-mode property
2015-09-08 20:22:17 +02:00
nm_setting_ip6_config_addr_gen_mode_get_type;
nm_setting_ip6_config_get_addr_gen_mode;
libnm: fix libnm.ver by putting new symbols into appropriate section Fixes: 019943bb5d9efea52392610b207dececafa6fdb3
2015-05-20 14:57:06 +02:00
nm_setting_ip_config_add_dns_option;
nm_setting_ip_config_clear_dns_options;
libnm: add NMSettingIPConfig 'dad-timeout' property The property is used to control duplicate address detection: * -1 means default value * 0 means no DAD is performed * > 0 means timeout (in milliseconds) for arping responses [bgalvani: moved setting from NMSettingIP4Config]
2015-09-07 18:00:10 +02:00
nm_setting_ip_config_get_dad_timeout;
libnm,core,cli: move dhcp-timeout property to generic NMSettingIPConfig The property applies to both IPv4 and IPv6 and so it should not be in NMSettingIP4Config but in the base class.
2016-02-03 11:12:07 +01:00
nm_setting_ip_config_get_dhcp_timeout;
libnm: fix libnm.ver by putting new symbols into appropriate section Fixes: 019943bb5d9efea52392610b207dececafa6fdb3
2015-05-20 14:57:06 +02:00
nm_setting_ip_config_get_dns_option;
nm_setting_ip_config_get_num_dns_options;
libnm: make dns-options support an "undefined" default value We want to distinguish between "no-options/empty" and "unset/default". The latter can be interpreted by NM to use a default set of options.
2015-05-20 13:19:35 +02:00
nm_setting_ip_config_has_dns_options;
libnm: fix libnm.ver by putting new symbols into appropriate section Fixes: 019943bb5d9efea52392610b207dececafa6fdb3
2015-05-20 14:57:06 +02:00
nm_setting_ip_config_remove_dns_option;
nm_setting_ip_config_remove_dns_option_by_value;
libnm-core: add NMSettingIPTunnel Add a generic NMSettingTunnel which describes properties of tunnels over IPv4 and IPv6 (GRE, SIT, IPIP, IPIP6, IP6GRE, etc.). Since those tunnel types all have similar properties it makes sense to have a single setting type for them.
2015-09-01 14:06:00 +02:00
nm_setting_ip_tunnel_get_input_key;
nm_setting_ip_tunnel_get_local;
nm_setting_ip_tunnel_get_mode;
ip-tunnel: add a MTU property Add a new ip-tunnel.mtu property which can be used to change the MTU of the tunnel interface.
2015-12-16 11:31:58 +01:00
nm_setting_ip_tunnel_get_mtu;
libnm-core: add NMSettingIPTunnel Add a generic NMSettingTunnel which describes properties of tunnels over IPv4 and IPv6 (GRE, SIT, IPIP, IPIP6, IP6GRE, etc.). Since those tunnel types all have similar properties it makes sense to have a single setting type for them.
2015-09-01 14:06:00 +02:00
nm_setting_ip_tunnel_get_output_key;
nm_setting_ip_tunnel_get_parent;
nm_setting_ip_tunnel_get_path_mtu_discovery;
nm_setting_ip_tunnel_get_remote;
nm_setting_ip_tunnel_get_tos;
nm_setting_ip_tunnel_get_type;
nm_setting_ip_tunnel_get_ttl;
nm_setting_ip_tunnel_new;
libnm: add Wi-Fi MAC address randomization property
2015-10-06 17:42:15 -04:00
nm_setting_mac_randomization_get_type;
libnm-core: add NMSettingTun Add a new NMSettingTun which contains configuration properties for TUN/TAP interfaces.
2015-09-14 22:56:51 +02:00
nm_setting_tun_get_group;
nm_setting_tun_get_mode;
nm_setting_tun_get_multi_queue;
nm_setting_tun_get_owner;
nm_setting_tun_get_pi;
nm_setting_tun_get_type;
nm_setting_tun_get_vnet_hdr;
nm_setting_tun_mode_get_type;
nm_setting_tun_new;
libnm: add nm_setting_verify_secrets() and nm_connection_verify_secrets() for verifying the secrets, because it is not done in plain nm_setting_verify(). For simple verification of free-form string secrets, _nm_setting_verify_secret_string() helper is used.
2015-11-10 14:36:20 +01:00
nm_setting_verify_secrets;
libnm-core: add vpn.timeout property for establishing connections [1] https://mail.gnome.org/archives/networkmanager-list/2015-April/msg00007.html
2015-09-16 09:34:33 +02:00
nm_setting_vpn_get_timeout;
libnm-core: add NMSettingMacvlan The setting contains properties that are specific to macvlans and macvtaps.
2015-09-17 18:13:49 +02:00
nm_setting_macvlan_get_mode;
nm_setting_macvlan_get_parent;
nm_setting_macvlan_get_promiscuous;
nm_setting_macvlan_get_tap;
nm_setting_macvlan_get_type;
nm_setting_macvlan_mode_get_type;
nm_setting_macvlan_new;
libnm-core: add NMSettingVxlan Add a new NMSettingVxlan which describes properties of VXLAN connections.
2015-10-13 09:09:54 +02:00
nm_setting_vxlan_get_ageing;
nm_setting_vxlan_get_destination_port;
nm_setting_vxlan_get_id;
nm_setting_vxlan_get_l2_miss;
nm_setting_vxlan_get_l3_miss;
nm_setting_vxlan_get_learning;
nm_setting_vxlan_get_limit;
nm_setting_vxlan_get_local;
nm_setting_vxlan_get_parent;
nm_setting_vxlan_get_proxy;
nm_setting_vxlan_get_remote;
nm_setting_vxlan_get_rsc;
nm_setting_vxlan_get_source_port_max;
nm_setting_vxlan_get_source_port_min;
nm_setting_vxlan_get_tos;
nm_setting_vxlan_get_ttl;
nm_setting_vxlan_get_type;
nm_setting_vxlan_new;
libnm-core: add Wake-on-LAN properties to NMSettingWired
2015-05-11 21:59:51 +02:00
nm_setting_wired_get_wake_on_lan;
nm_setting_wired_get_wake_on_lan_password;
nm_setting_wired_wake_on_lan_get_type;
libnm: fix version script to add new API to proper linker section Fixes: 5293683e4a01df1dc47e884ead3a6c6c9493b1f9
2015-02-26 10:18:19 +01:00
nm_setting_wireless_get_powersave;
libnm: add Wi-Fi MAC address randomization property
2015-10-06 17:42:15 -04:00
nm_setting_wireless_get_mac_address_randomization;
wifi: don't touch by default current powersave setting Some drivers (or things outside NM like 'powertop') may turn powersave on, so don't touch it unless explicitly configured by user. To achieve this, add new 'default' and 'ignore' options; the former can be used to fall back to a globally configured setting, while the latter tells NM not to touch the current setting. When 'default' is specified, a missing global default configuration is equivalent to 'ignore'. It is possible to enable Wi-Fi power saving for all connections by dropping a file in /etc/NetworkManager/conf.d with the following content: [connection] wifi.powersave=3 https://bugzilla.gnome.org/show_bug.cgi?id=760125
2016-02-10 16:46:34 +01:00
nm_setting_wireless_powersave_get_type;
libnm: fix versioning on new APIs, bump soname The newly added bond mode APIs in nm-utils will be new in 1.2, so mark them as such in the headers and docs, move them to a new section in libnm.ver. Since we're adding the new section to libnm.ver, this also seems like a good time to bump the soname.
2015-01-15 16:42:26 -05:00
nm_utils_bond_mode_int_to_string;
nm_utils_bond_mode_string_to_int;
libnm-core: add enum conversion utilities Add functions nm_utils_enum_to_str() and nm_utils_enum_from_str() which can be used to perform conversions between enum values and strings, passing the GType automatically generated for every enum by glib-mkenums.
2015-06-04 15:05:33 +02:00
nm_utils_enum_from_str;
nm_utils_enum_to_str;
libnm-core: add nm_utils_enum_get_values() Add function nm_utils_enum_get_values() which returns a string array containing the enum values. It can be used, for example, to build a list of allowed values for user.
2015-09-06 13:11:11 +02:00
nm_utils_enum_get_values;
libnm: add utility functions for getting 2.4 GHz and 5 GHz Wi-Fi frequencies nm_utils_wifi_2ghz_freqs() nm_utils_wifi_5ghz_freqs()
2015-08-18 09:37:48 +02:00
nm_utils_wifi_2ghz_freqs;
nm_utils_wifi_5ghz_freqs;
libnm: add nm_vpn_editor_plugin_load_from_file() function
2015-05-28 22:16:00 +02:00
nm_vpn_editor_plugin_load_from_file;
libnm: add NMVpnPluginInfo class NMVpnPluginInfo is little more then a wrapper around the GKeyFile that describes the VPN plugin settings, i.e. the name files under "/etc/NetworkManager/VPN/". Add this class to make the VPN API more explicit. Clients now can use NMVpnPluginInfo instead of concerning themselves with loading the keyfile and the meaning of its properties. Also add support for a new VPN plugins directory "/usr/lib/NetworkManager/VPN", which should replace "/etc/NetworkManager/VPN" in the future. But we have to consider both locations for backward compatibility. The content of the VPN directory is not user configuration, hence it should not be under "/etc". See related bug 738853.
2015-05-22 13:26:40 +02:00
nm_vpn_plugin_info_get_filename;
libnm: add load method to NMVpnPluginInfo https://bugzilla.gnome.org/show_bug.cgi?id=749877
2015-05-28 22:12:31 +02:00
nm_vpn_plugin_info_get_editor_plugin;
libnm: add NMVpnPluginInfo class NMVpnPluginInfo is little more then a wrapper around the GKeyFile that describes the VPN plugin settings, i.e. the name files under "/etc/NetworkManager/VPN/". Add this class to make the VPN API more explicit. Clients now can use NMVpnPluginInfo instead of concerning themselves with loading the keyfile and the meaning of its properties. Also add support for a new VPN plugins directory "/usr/lib/NetworkManager/VPN", which should replace "/etc/NetworkManager/VPN" in the future. But we have to consider both locations for backward compatibility. The content of the VPN directory is not user configuration, hence it should not be under "/etc". See related bug 738853.
2015-05-22 13:26:40 +02:00
nm_vpn_plugin_info_get_name;
nm_vpn_plugin_info_get_plugin;
nm_vpn_plugin_info_get_program;
nm_vpn_plugin_info_get_type;
libnm: add load method to NMVpnPluginInfo https://bugzilla.gnome.org/show_bug.cgi?id=749877
2015-05-28 22:12:31 +02:00
nm_vpn_plugin_info_load_editor_plugin;
libnm: add NMVpnPluginInfo class NMVpnPluginInfo is little more then a wrapper around the GKeyFile that describes the VPN plugin settings, i.e. the name files under "/etc/NetworkManager/VPN/". Add this class to make the VPN API more explicit. Clients now can use NMVpnPluginInfo instead of concerning themselves with loading the keyfile and the meaning of its properties. Also add support for a new VPN plugins directory "/usr/lib/NetworkManager/VPN", which should replace "/etc/NetworkManager/VPN" in the future. But we have to consider both locations for backward compatibility. The content of the VPN directory is not user configuration, hence it should not be under "/etc". See related bug 738853.
2015-05-22 13:26:40 +02:00
nm_vpn_plugin_info_lookup_property;
nm_vpn_plugin_info_new_from_file;
nm_vpn_plugin_info_new_with_data;
libnm: add load method to NMVpnPluginInfo https://bugzilla.gnome.org/show_bug.cgi?id=749877
2015-05-28 22:12:31 +02:00
nm_vpn_plugin_info_set_editor_plugin;
libnm: add NMVpnPluginInfo class NMVpnPluginInfo is little more then a wrapper around the GKeyFile that describes the VPN plugin settings, i.e. the name files under "/etc/NetworkManager/VPN/". Add this class to make the VPN API more explicit. Clients now can use NMVpnPluginInfo instead of concerning themselves with loading the keyfile and the meaning of its properties. Also add support for a new VPN plugins directory "/usr/lib/NetworkManager/VPN", which should replace "/etc/NetworkManager/VPN" in the future. But we have to consider both locations for backward compatibility. The content of the VPN directory is not user configuration, hence it should not be under "/etc". See related bug 738853.
2015-05-22 13:26:40 +02:00
nm_vpn_plugin_info_validate_filename;
nm_vpn_plugin_info_list_add;
nm_vpn_plugin_info_list_find_by_filename;
nm_vpn_plugin_info_list_find_by_name;
nm_vpn_plugin_info_list_find_by_service;
nm_vpn_plugin_info_list_load;
nm_vpn_plugin_info_list_remove;
libnm/vpn: add new NMVpnServicePlugin class After copying "nm-vpn-plugin-old.*" to "nm-vpn-service-plugin.*", rename the class and add it to the Makefile. This will become the new VPN Service API for libnm 1.2. No changes done yet except renaming of the classes and functions. Rename the previous classes NMVpnPlugin(Old) to NMVpnServicePlugin to have a distinct name from NMVpnEditorPlugin. Buth are plugins, but with a different use. https://bugzilla.gnome.org/show_bug.cgi?id=749951
2015-06-02 10:50:29 +02:00
nm_vpn_service_plugin_disconnect;
nm_vpn_service_plugin_failure;
nm_vpn_service_plugin_get_connection;
nm_vpn_service_plugin_get_secret_flags;
nm_vpn_service_plugin_get_type;
nm_vpn_service_plugin_read_vpn_details;
nm_vpn_service_plugin_secrets_required;
libnm: export nm_vpn_service_plugin_set_{ip6_,}config Seems to be forgotten.
2015-08-25 14:46:12 +02:00
nm_vpn_service_plugin_set_config;
libnm/vpn: add new NMVpnServicePlugin class After copying "nm-vpn-plugin-old.*" to "nm-vpn-service-plugin.*", rename the class and add it to the Makefile. This will become the new VPN Service API for libnm 1.2. No changes done yet except renaming of the classes and functions. Rename the previous classes NMVpnPlugin(Old) to NMVpnServicePlugin to have a distinct name from NMVpnEditorPlugin. Buth are plugins, but with a different use. https://bugzilla.gnome.org/show_bug.cgi?id=749951
2015-06-02 10:50:29 +02:00
nm_vpn_service_plugin_set_ip4_config;
libnm: export nm_vpn_service_plugin_set_{ip6_,}config Seems to be forgotten.
2015-08-25 14:46:12 +02:00
nm_vpn_service_plugin_set_ip6_config;
libnm/vpn: add new NMVpnServicePlugin class After copying "nm-vpn-plugin-old.*" to "nm-vpn-service-plugin.*", rename the class and add it to the Makefile. This will become the new VPN Service API for libnm 1.2. No changes done yet except renaming of the classes and functions. Rename the previous classes NMVpnPlugin(Old) to NMVpnServicePlugin to have a distinct name from NMVpnEditorPlugin. Buth are plugins, but with a different use. https://bugzilla.gnome.org/show_bug.cgi?id=749951
2015-06-02 10:50:29 +02:00
nm_vpn_service_plugin_set_login_banner;
libnm: fix versioning on new APIs, bump soname The newly added bond mode APIs in nm-utils will be new in 1.2, so mark them as such in the headers and docs, move them to a new section in libnm.ver. Since we're adding the new section to libnm.ver, this also seems like a good time to bump the soname.
2015-01-15 16:42:26 -05:00
} libnm_1_0_0;
libnm/vpn: add nm_vpn_editor_plugin_load() function Contrary to nm_vpn_editor_plugin_load_from_file(), this allows to specify a library name without path. In this case, g_module_open() (dlopen()) will search for a library in various system directories.
2016-04-18 18:26:28 +02:00
libnm: backport symbols nm_setting_ip_config_get_dns_priority to libnm_1_2_4 Commit bdd0e7fec0a2af12331b815bfaf3de182ed6eebb which added symbol nm_setting_ip_config_get_dns_priority to libnm_1_4_0 was backported to nm-1-2 in commit ad1cdcf6571da23e3197b09f1b4b14d23b8899d1. Add the backported symbol to master to allow seemless upgrading from 1.2.4 to 1.4.0.
2016-06-10 11:28:44 +02:00
libnm_1_2_4 {
#nm_setting_ip_config_get_dns_priority@libnm_1_2_4;
} libnm_1_2_0;
libnm/vpn: add nm_vpn_editor_plugin_load() function Contrary to nm_vpn_editor_plugin_load_from_file(), this allows to specify a library name without path. In this case, g_module_open() (dlopen()) will search for a library in various system directories.
2016-04-18 18:26:28 +02:00
libnm_1_4_0 {
global:
team: expose current device configuration through D-Bus and nmcli Add a new "Config" property to the D-Bus interface for team devices and show its value through "nmcli device show". The property contains the full JSON configuration from teamd for the device. https://bugzilla.redhat.com/show_bug.cgi?id=1310435
2016-05-16 14:42:41 +02:00
nm_device_team_get_config;
libnm: add NMSettingConnection:stable-id property This new property be used as token to generate stable-ids instead of the connection's UUID. Later, this will be used by ipv6.addr-gen-mode=stable-privacy, ethernet.cloned-mac-address=stable, and wifi.cloned-mac-address=stable setting. Those generate stable addresses based on the connection's UUID, but allow to use the stable-id instead. This allows multiple connections to generate the same addresses -- on the same machine, because in the above cases a machine dependant key is also hashed.
2016-06-21 16:41:05 +02:00
nm_setting_connection_get_stable_id;
libnm: export nm_setting_ip6_config_get_token() symbol Fixes: 954d937b2f6bfe5a513497c6ea13d0651a0c0b16
2016-05-30 18:27:21 +02:00
nm_setting_ip6_config_get_token;
libnm-core: add dns-priority to NMSettingIPConfig
2016-04-23 15:57:04 +02:00
nm_setting_ip_config_get_dns_priority;
all: make MAC address randomization algorithm configurable For the per-connection settings "ethernet.cloned-mac-address" and "wifi.cloned-mac-address", and for the per-device setting "wifi.scan-rand-mac-address", we may generate MAC addresses using either the "random" or "stable" algorithm. Add new properties "generate-mac-address-mask" that allow to configure which bits of the MAC address will be scrambled. By default, the "random" and "stable" algorithms scamble all bits of the MAC address, including the OUI part and generate a locally- administered, unicast address. By specifying a MAC address mask, we can now configure to perserve parts of the current MAC address of the device. For example, setting "FF:FF:FF:00:00:00" will preserve the first 3 octects of the current MAC address. One can also explicitly specify a MAC address to use instead of the current MAC address. For example, "FF:FF:FF:00:00:00 68:F7:28:00:00:00" sets the OUI part of the MAC address to "68:F7:28" while scrambling the last 3 octects. Similarly, "02:00:00:00:00:00 00:00:00:00:00:00" will scamble all bits of the MAC address, except clearing the second-least significant bit. Thus, creating a burned-in address, globally administered. One can also supply a list of MAC addresses like "FF:FF:FF:00:00:00 68:F7:28:00:00:00 00:0C:29:00:00:00 ..." in which case a MAC address is choosen randomly. To fully scamble the MAC address one can configure "02:00:00:00:00:00 00:00:00:00:00:00 02:00:00:00:00:00". which also randomly creates either a locally or globally administered address. With this, the following macchanger options can be implemented: `macchanger --random` This is the default if no mask is configured. -> "" while is the same as: -> "00:00:00:00:00:00" -> "02:00:00:00:00:00 02:00:00:00:00:00" `macchanger --random --bia` -> "02:00:00:00:00:00 00:00:00:00:00:00" `macchanger --ending` This option cannot be fully implemented, because macchanger uses the current MAC address but also implies --bia. -> "FF:FF:FF:00:00:00" This would yields the same result only if the current MAC address is already a burned-in address too. Otherwise, it has not the same effect as --ending. -> "FF:FF:FF:00:00:00 <MAC_ADDR>" Alternatively, instead of using the current MAC address, spell the OUI part out. But again, that is not really the same as macchanger does because you explictly have to name the OUI part to use. `machanger --another` `machanger --another_any` -> "FF:FF:FF:00:00:00 <MAC_ADDR> <MAC_ADDR> ..." "$(printf "FF:FF:FF:00:00:00 %s\n" "$(sed -n 's/^\([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) \([0-9a-fA-F][0-9a-fA-F]\) .*/\1:\2:\3:00:00:00/p' /usr/share/macchanger/wireless.list | xargs)")"
2016-06-22 20:31:39 +02:00
nm_setting_wired_get_generate_mac_address_mask;
nm_setting_wireless_get_generate_mac_address_mask;
libnm/vpn: pass NMVpnPluginInfo to the NMVpnEditorPlugin instance The NMVpnPluginInfo is essentially the .name file, that is, a configuration file about the plugin itself. Via NMVpnPluginInfo instance, the NMVpnEditorPlugin can be created. Usually, one would create a NMVpnPluginInfo (that is, reading the .name file) and then create a NMVpnEditorPlugin instance from there. In this case, usually the editor-plugin is owned by the plugin-info instance (although the API allows for creating the editor-plugin independently). Now, pass the NMVpnPluginInfo to the editor-plugin too. This is useful, because then the editor-plugin can look at the .name file. The .name file is not user configuration. Instead it is configuration about the plugin itself. Although the .name file is part of the plugin build artefacts, it is useful to allow the plugin to access the .name file. The reason is, that this can allow the user to easily change a configuration knob of the plugin without requiring to patch or the plugin.
2016-06-09 00:50:40 +02:00
nm_vpn_editor_plugin_get_plugin_info;
libnm/vpn: add nm_vpn_editor_plugin_load_vt() Let VPN plugins return a virtual function table to extend the API while bypassing libnm. This allows to add and use new functionality to VPN plugins without updating libnm. The actual definitions are in a header-only file "nm-vpn-editor-plugin-call.h", which can be copied to the caller/plugin.
2016-06-13 11:47:58 +02:00
nm_vpn_editor_plugin_get_vt;
libnm/vpn: add nm_vpn_editor_plugin_load() function Contrary to nm_vpn_editor_plugin_load_from_file(), this allows to specify a library name without path. In this case, g_module_open() (dlopen()) will search for a library in various system directories.
2016-04-18 18:26:28 +02:00
nm_vpn_editor_plugin_load;
libnm/vpn: pass NMVpnPluginInfo to the NMVpnEditorPlugin instance The NMVpnPluginInfo is essentially the .name file, that is, a configuration file about the plugin itself. Via NMVpnPluginInfo instance, the NMVpnEditorPlugin can be created. Usually, one would create a NMVpnPluginInfo (that is, reading the .name file) and then create a NMVpnEditorPlugin instance from there. In this case, usually the editor-plugin is owned by the plugin-info instance (although the API allows for creating the editor-plugin independently). Now, pass the NMVpnPluginInfo to the editor-plugin too. This is useful, because then the editor-plugin can look at the .name file. The .name file is not user configuration. Instead it is configuration about the plugin itself. Although the .name file is part of the plugin build artefacts, it is useful to allow the plugin to access the .name file. The reason is, that this can allow the user to easily change a configuration knob of the plugin without requiring to patch or the plugin.
2016-06-09 00:50:40 +02:00
nm_vpn_editor_plugin_set_plugin_info;
libnm/vpn: add nm_vpn_plugin_info_get_aliases
2016-06-03 16:43:26 +02:00
nm_vpn_plugin_info_get_aliases;
libnm/vpn: add nm_vpn_plugin_info_get_auth_dialog()
2016-04-20 16:18:05 +02:00
nm_vpn_plugin_info_get_auth_dialog;
libnm/vpn: add nm_vpn_plugin_info_get_service() Re-add nm_vpn_plugin_info_get_service(). This function *is* useful and could be used by nm-applet. This reverts commit 3517084b92aa64817ce8cd82163e5ab6e1947017.
2016-04-20 16:04:13 +02:00
nm_vpn_plugin_info_get_service;
libnm/vpn: add nm_vpn_plugin_info_list_find_service_name() function
2016-06-07 11:11:30 +02:00
nm_vpn_plugin_info_list_get_service_types;
nm_vpn_plugin_info_list_find_service_type;
libnm/vpn: add nm_vpn_plugin_info_new_search_file()
2016-04-22 09:12:54 +02:00
nm_vpn_plugin_info_new_search_file;
libnm/vpn: add nm_vpn_plugin_info_supports_hints()
2016-04-20 16:24:54 +02:00
nm_vpn_plugin_info_supports_hints;
libnm/vpn: add nm_vpn_editor_plugin_load() function Contrary to nm_vpn_editor_plugin_load_from_file(), this allows to specify a library name without path. In this case, g_module_open() (dlopen()) will search for a library in various system directories.
2016-04-18 18:26:28 +02:00
} libnm_1_2_0;
libnm: fix symbol versioning Already released versions must not be extended or modified. The new symbol is part of upcomming 1.6.0 release.
2016-09-23 13:18:32 +02:00
libnm_1_6_0 {
cli: reject team.config from files with '\0' The team-config must be valid utf-8. First of all, JSON is also defined for other unicode encodings, but libjansson can only handle utf-8. So, just require that. A file with a '\0' truncates part of the file and is thus invalid.
2016-09-27 11:21:44 +02:00
global:
libnm: fix symbol versioning Already released versions must not be extended or modified. The new symbol is part of upcomming 1.6.0 release.
2016-09-23 13:18:32 +02:00
nm_capability_get_type;
libnm: implement support for DNS manager properties
2016-10-25 11:11:12 +02:00
nm_client_get_dns_configuration;
nm_client_get_dns_mode;
nm_client_get_dns_rc_manager;
libnm-core: add NMSettingMacsec The new NMSettingMacsec contains information necessary to establish a MACsec connection. At the moment we support two different MACsec modes, both using wpa_supplicant: PSK and EAP. PSK mode is based on a static CAK key for the MACsec key agreement protocol, while EAP mode derives keys from a 802.1x authentication and thus requires the presence of a NMSetting8021x in the connection.
2016-06-30 18:20:43 +02:00
nm_connection_get_setting_macsec;
libnm: API for Proxy Feature libnm-core has been expanded to include proxy settings which clients like nmcli, nm-connection-editor use to configure proxy in PacRunner. It offers three modes i.e 'auto', 'manual'and 'none' and accordingly take data to configure PacRunner. The modes matches on the PacRunner side too.
2016-08-16 05:55:55 +05:30
nm_connection_get_setting_proxy;
core,libnm: introduce NMDeviceMacsec At the moment the device only exposes the current link status, but cannot create new links.
2016-06-30 18:20:22 +02:00
nm_device_macsec_get_cipher_suite;
nm_device_macsec_get_encoding_sa;
nm_device_macsec_get_encrypt;
nm_device_macsec_get_es;
nm_device_macsec_get_hw_address;
nm_device_macsec_get_icv_length;
nm_device_macsec_get_include_sci;
nm_device_macsec_get_protect;
nm_device_macsec_get_replay_protect;
nm_device_macsec_get_scb;
nm_device_macsec_get_sci;
nm_device_macsec_get_type;
nm_device_macsec_get_validation;
nm_device_macsec_get_window;
libnm: implement support for DNS manager properties
2016-10-25 11:11:12 +02:00
nm_dns_entry_get_domains;
nm_dns_entry_get_interface;
nm_dns_entry_get_nameservers;
nm_dns_entry_get_priority;
nm_dns_entry_get_type;
nm_dns_entry_get_vpn;
nm_dns_entry_unref;
libnm-core: introduce connection.autoconnect-retries property While technically it's already possible to implement a fail-over mechanism using multiple connections (for example, defining a higher priority DHCP connection with short DHCP timeout and a lower priority one with static address), in practice this doesn't work well as we try to autoactivate each connection 4 times before switching to the next one. Introduce a connection.autoconnect-retries property that can be used to change the number of retries. The special value 0 means infinite and can be used to try the connection forever. A -1 value means the global configured default, which is equal to 4 unless overridden. https://bugzilla.gnome.org/show_bug.cgi?id=763524
2016-10-08 10:27:15 +02:00
nm_setting_connection_get_autoconnect_retries;
libnm-core: add NMSettingMacsec The new NMSettingMacsec contains information necessary to establish a MACsec connection. At the moment we support two different MACsec modes, both using wpa_supplicant: PSK and EAP. PSK mode is based on a static CAK key for the MACsec key agreement protocol, while EAP mode derives keys from a 802.1x authentication and thus requires the presence of a NMSetting8021x in the connection.
2016-06-30 18:20:43 +02:00
nm_setting_macsec_get_encrypt;
nm_setting_macsec_get_mka_cak;
nm_setting_macsec_get_mka_cak_flags;
nm_setting_macsec_get_mka_ckn;
nm_setting_macsec_get_mode;
nm_setting_macsec_get_parent;
nm_setting_macsec_get_port;
nm_setting_macsec_get_type;
nm_setting_macsec_get_validation;
nm_setting_macsec_mode_get_type;
nm_setting_macsec_new;
nm_setting_macsec_validation_get_type;
libnm: API for Proxy Feature libnm-core has been expanded to include proxy settings which clients like nmcli, nm-connection-editor use to configure proxy in PacRunner. It offers three modes i.e 'auto', 'manual'and 'none' and accordingly take data to configure PacRunner. The modes matches on the PacRunner side too.
2016-08-16 05:55:55 +05:30
nm_setting_proxy_get_type;
nm_setting_proxy_new;
nm_setting_proxy_get_method;
nm_setting_proxy_method_get_type;
nm_setting_proxy_get_browser_only;
nm_setting_proxy_get_pac_url;
proxy: remove unnecessary APIs Unnecessary APIs have been removed from nm-setting-proxy, client like nm-connection-editor are expected to create a PAC script snippet the load the location of file in NM.
2016-09-05 21:34:27 +05:30
nm_setting_proxy_get_pac_script;
libnm-core/8021x: add pkcs11: scheme for certificates and keys The getters just return the whole URI as-is, without any mangling.
2016-12-19 12:47:15 +01:00
nm_setting_802_1x_get_ca_cert_uri;
nm_setting_802_1x_get_phase2_ca_cert_uri;
nm_setting_802_1x_get_client_cert_uri;
nm_setting_802_1x_get_phase2_client_cert_uri;
nm_setting_802_1x_get_private_key_uri;
nm_setting_802_1x_get_phase2_private_key_uri;
libnm: expose nm_utils_is_json_object() utility function Since we possibly already link against libjansson, we can also expose some helper utils which allows nmcli to do basic validation of JSON without requiring to duplicate the effort of using libjansson. Also, tighten up the cecks to ensure that we have a JSON object at hand. We are really interested in that and not of arrays or literals.
2016-09-23 10:30:50 +02:00
nm_utils_is_json_object;
libnm: add nm_utils_version() function to query libnm version at runtime if (nm_utils_version () < NM_ENCODE_VERSION (1, 5, 0)) g_error ("Requires at least version 1.5.0");
2016-12-20 16:36:15 +01:00
nm_utils_version;
libnm-core: add nm_utils_is_valid_iface_name() Version of nm_utils_iface_valid_name() with error reporting.
2016-12-23 12:52:41 +01:00
nm_utils_is_valid_iface_name;
libnm: fix symbol versioning Already released versions must not be extended or modified. The new symbol is part of upcomming 1.6.0 release.
2016-09-23 13:18:32 +02:00
} libnm_1_4_0;
core/8021x: add password properties for certificates Useful for certificates that are stored on PKCS#11 tokens. We fail verification if someone tries tu specify a password for a blob or a flat file.
2017-02-01 12:53:34 +00:00
libnm_1_8_0 {
global:
active-connection: emit a StateChanged signal on state changes It includes a reason code that makes it possible for the clients to be more reasonable about error messages. The reason code is essentially copied from the VPN, plus three more reasons that were useful for non-VPN connections.
2017-03-05 15:30:24 +01:00
nm_active_connection_state_reason_get_type;
libnm/active-connection: track reason for state changes Note that the reason tracking starts as soon as the object exists (which is immediately after GDBusObject is created), not when the asynchronous NMObject initialization finishes. That is so that we the reason changes in between are not lost. The vpn-connection should probably be doing the same.
2017-03-05 17:20:27 +01:00
nm_active_connection_get_state_reason;
libnm-core: add dummy connection setting The setting must be present in connections with type=dummy. It does not contain any property.
2017-01-31 14:13:35 +01:00
nm_connection_get_setting_dummy;
core: add support for dummy devices Add support for creating dummy devices. This commit adds a D-Bus interface 'org.freedesktop.NetworkManager.Device.Dummy' which is used primarily for determining the device type but does not carry any properties.
2017-01-31 14:14:33 +01:00
nm_device_dummy_get_type;
libnm-core: define known route attribute names and validation function This adds definition of a set of known route option attributes to libnm-core and helper functions. nm_ip_route_attribute_validate() performs the validation of the attribute type and, in case of a formatted string attribute, of its content. nm_ip_route_get_variant_attribute_spec() returns the attribute format specifier to be passed to nm_utils_parse_variant_attributes(). Since at the moment NMIPRoute is the only user of NMVariantAttributeSpec and the type is opaque to users of the library, the struct is extended to carry some other data useful for validation.
2017-02-15 15:06:24 +01:00
nm_ip_route_get_variant_attribute_spec;
nm_ip_route_attribute_validate;
libnm-core/8021x: add phase1-auth-flags configuration items
2017-02-08 22:02:19 +07:00
nm_setting_802_1x_auth_flags_get_type;
libnm-core: add auth-timeout property to the 802.1x setting The property can be used to tune the authentication timeout. It's especially useful to speed up the failure in case the port doesn't support 802.1X and make NM try a different, non-authenticated connection.
2017-01-19 17:25:19 +01:00
nm_setting_802_1x_get_auth_timeout;
core/8021x: add password properties for certificates Useful for certificates that are stored on PKCS#11 tokens. We fail verification if someone tries tu specify a password for a blob or a flat file.
2017-02-01 12:53:34 +00:00
nm_setting_802_1x_get_ca_cert_password;
nm_setting_802_1x_get_ca_cert_password_flags;
nm_setting_802_1x_get_client_cert_password;
nm_setting_802_1x_get_client_cert_password_flags;
libnm-core/8021x: add phase1-auth-flags configuration items
2017-02-08 22:02:19 +07:00
nm_setting_802_1x_get_phase1_auth_flags;
core/8021x: add password properties for certificates Useful for certificates that are stored on PKCS#11 tokens. We fail verification if someone tries tu specify a password for a blob or a flat file.
2017-02-01 12:53:34 +00:00
nm_setting_802_1x_get_phase2_ca_cert_password;
nm_setting_802_1x_get_phase2_ca_cert_password_flags;
nm_setting_802_1x_get_phase2_client_cert_password;
nm_setting_802_1x_get_phase2_client_cert_password_flags;
libnm-core: add mtu property to cdma setting
2016-10-26 10:32:06 +02:00
nm_setting_cdma_get_mtu;
libnm-core: add dummy connection setting The setting must be present in connections with type=dummy. It does not contain any property.
2017-01-31 14:13:35 +01:00
nm_setting_dummy_get_type;
nm_setting_dummy_new;
libnm-core: add mtu property to gsm setting
2016-10-26 10:05:46 +02:00
nm_setting_gsm_get_mtu;
libnm: add NMSettingUser This only adds new API for a NMSettingUser. The setting class is still entirely unused. The point is getting the new API into 1.8.0 release of libnm. It's easier to backport the use of the API to a stable branch then backporting public API. https://bugzilla.gnome.org/show_bug.cgi?id=776276 https://bugzilla.redhat.com/show_bug.cgi?id=1421429
2017-03-24 12:41:04 +01:00
nm_setting_user_check_key;
nm_setting_user_check_val;
nm_setting_user_get_data;
nm_setting_user_get_keys;
nm_setting_user_get_type;
nm_setting_user_new;
nm_setting_user_set_data;
libnm-core: add attribute parsing/format helpers Various libnm objects (addresses, routes) carry an hash table of attributes represented as GVariants indexed by name. Add common routines to convert to and from a string representation. To parse a string, a knowledge of the supported attributes (and their types) is needed: we represent it as an opaque type NMVariantAttributeSpec that callers must query to the library for the specific object type and pass to the parse function.
2017-03-02 11:08:34 +01:00
nm_utils_format_variant_attributes;
nm_utils_parse_variant_attributes;
core/8021x: add password properties for certificates Useful for certificates that are stored on PKCS#11 tokens. We fail verification if someone tries tu specify a password for a blob or a flat file.
2017-02-01 12:53:34 +00:00
} libnm_1_6_0;
libnm-core: add pmf property to wireless-security setting Add a 'pmf' property to enable or disable Protected Management Frames (802.11w) for the connection.
2017-04-27 09:30:58 +02:00
libnm_1_10_0 {
global:
libnm: add NMActivationStateFlags No flags yet implemented. https://bugzilla.redhat.com/show_bug.cgi?id=1454883
2017-09-25 19:06:02 +02:00
nm_activation_state_flags_get_type;
nm_active_connection_get_state_flags;
libnm/connectivity: fix exporting new connectivity ABI in linker version script Fixes: 0480dae7492adfea5fb8f60b366a22cdd7df4927
2017-08-17 23:26:08 +02:00
nm_client_connectivity_check_get_available;
nm_client_connectivity_check_get_enabled;
nm_client_connectivity_check_set_enabled;
libnm: add nm_connection_get_settings() There is no API to get all settings. You can only ask for settings explicitly, but that requires you to probe for them and know which ones may exist. The alternative API might be nm_connection_for_each_setting_value(), but that only iterates over settings' properties. If a setting has no properties, it is ignored.
2017-10-28 17:46:26 +02:00
nm_connection_get_settings;
libnm: add 'hw-address' property to NMDeviceDummy Dummy devices have a MAC address; expose it in the D-Bus interface.
2017-06-30 18:35:09 +02:00
nm_device_dummy_get_hw_address;
libnm: add support for ovs-bridge devices
2017-10-10 11:04:32 +02:00
nm_device_ovs_bridge_get_type;
libnm: add support for ovs-interface devices
2017-10-10 11:04:32 +02:00
nm_device_ovs_interface_get_type;
libnm: add support for ovs-port devices
2017-10-10 11:04:32 +02:00
nm_device_ovs_port_get_type;
device: add NMDevicePPP The new device type represents a PPP interface, and will implement the activation of new-style PPPoE connections, i.e. the ones that don't claim the parent device.
2017-06-06 15:55:08 +02:00
nm_device_ppp_get_type;
libnm: add nm_ip_route_equal_full() function Expose previously internal function nm_ip_route_equal_full(). It's just useful API. However, add a @cmp_flags argument, so that in the future we could extend it.
2017-09-27 12:40:43 +02:00
nm_ip_route_equal_full;
bridge: introduce a bridge.group-forward-mask connection property https://bugzilla.redhat.com/show_bug.cgi?id=1358615
2017-07-21 17:55:30 +02:00
nm_setting_bridge_get_group_forward_mask;
all: move setting 802-1x.auth-retries to connection.auth-retries The number of authentication retires is useful also for passwords aside 802-1x settings. For example, src/devices/wifi/nm-device-wifi.c also has a retry counter and uses a hard-coded value of 3. Move the setting, so that it can be used in general. Although it is still not implemented for other settings. This is an API and ABI break.
2017-11-02 09:25:40 +01:00
nm_setting_connection_get_auth_retries;
all: rework configuring route table support by adding "route-table" setting We added "ipv4.route-table-sync" and "ipv6.route-table-sync" to not change behavior for users that configured policy routing outside of NetworkManager, for example, via a dispatcher script. Users had to explicitly opt-in for NetworkManager to fully manage all routing tables. These settings were awkward. Replace them with new settings "ipv4.route-table" and "ipv6.route-table". Note that this commit breaks API/ABI on the unstable development branch by removing recently added API. As before, a connection will have no route-table set by default. This has the meaning that policy-routing is not enabled and only the main table will be fully synced. Once the user sets a table, we recognize that and NetworkManager manages all routing tables. The new route-table setting has other important uses: analog to "ipv4.route-metric", it is the default that applies to all routes. Currently it only works for static routes, not DHCP, SLAAC, default-route, etc. That will be implemented later. For static routes, each route still can explicitly set a table, and overwrite the per-connection setting in "ipv4.route-table" and "ipv6.route-table".
2017-09-28 08:40:41 +02:00
nm_setting_ip_config_get_route_table;
libnm-core: add ovs-bridge setting
2017-08-01 18:36:34 +02:00
nm_setting_ovs_bridge_get_fail_mode;
nm_setting_ovs_bridge_get_mcast_snooping_enable;
nm_setting_ovs_bridge_get_rstp_enable;
nm_setting_ovs_bridge_get_stp_enable;
nm_setting_ovs_bridge_get_type;
nm_setting_ovs_bridge_new;
libnm-core: add ovs-interface setting
2017-08-01 18:36:34 +02:00
nm_setting_ovs_interface_get_interface_type;
nm_setting_ovs_interface_get_type;
nm_setting_ovs_interface_new;
libnm-core: add ovs-patch setting
2017-08-01 18:36:34 +02:00
nm_setting_ovs_patch_get_peer;
nm_setting_ovs_patch_get_type;
nm_setting_ovs_patch_new;
libnm-core: add ovs-port setting
2017-10-02 09:03:19 +02:00
nm_setting_ovs_port_get_bond_downdelay;
nm_setting_ovs_port_get_bond_mode;
nm_setting_ovs_port_get_bond_updelay;
nm_setting_ovs_port_get_lacp;
nm_setting_ovs_port_get_tag;
nm_setting_ovs_port_get_type;
nm_setting_ovs_port_get_vlan_mode;
nm_setting_ovs_port_new;
libnm,clients: add 'parent' property to PPPoE setting When the property is set, it specifies the device on which PPPoE is to be started. The ppp interface will be named as the connection.interface-name property. When the property is not set the previous behavior will be retained, i.e. the PPPoE connection will be started on connection.interface-name and the PPP interface will have a random name.
2017-06-30 13:58:23 +02:00
nm_setting_pppoe_get_parent;
libnm-core: add pmf property to wireless-security setting Add a 'pmf' property to enable or disable Protected Management Frames (802.11w) for the connection.
2017-04-27 09:30:58 +02:00
nm_setting_wireless_security_get_pmf;
setting-wireless: add wps-method property This property will be used to decide if it makes sense to attempt a WPS enrollment on connection activation.
2017-04-30 22:52:19 +02:00
nm_setting_wireless_security_get_wps_method;
libnm-core: add pmf property to wireless-security setting Add a 'pmf' property to enable or disable Protected Management Frames (802.11w) for the connection.
2017-04-27 09:30:58 +02:00
nm_setting_wireless_security_pmf_get_type;
setting-wireless: add wps-method property This property will be used to decide if it makes sense to attempt a WPS enrollment on connection activation.
2017-04-30 22:52:19 +02:00
nm_setting_wireless_security_wps_method_get_type;
libnm-core: add pmf property to wireless-security setting Add a 'pmf' property to enable or disable Protected Management Frames (802.11w) for the connection.
2017-04-27 09:30:58 +02:00
} libnm_1_8_0;
libnm: add checkpoint support
2017-10-21 16:05:19 +02:00
build: adjust libnm symbol versioning after backporting update2 API for 1.10.2 The update2 API was backported to nm-1-10 branch, with commit ad7f1d18a0eafb1352d305035cd138f43a47b955. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although they are first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbol.
2017-12-06 09:42:35 +01:00
libnm_1_10_2 {
libnm: fix libnm.ver file to export libnm_1_10_2 ABI Fixes: cb9facdfef4d94588761d72f8d0518375f4aaba7
2017-12-08 13:43:34 +01:00
global:
build: adjust libnm symbol versioning after backporting update2 API for 1.10.2 The update2 API was backported to nm-1-10 branch, with commit ad7f1d18a0eafb1352d305035cd138f43a47b955. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although they are first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbol.
2017-12-06 09:42:35 +01:00
nm_remote_connection_update2;
nm_remote_connection_update2_finish;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_settings_update2_flags_get_type;
nm_setting_tc_config_add_qdisc;
nm_setting_tc_config_add_tfilter;
nm_setting_tc_config_clear_qdiscs;
nm_setting_tc_config_clear_tfilters;
nm_setting_tc_config_get_num_qdiscs;
nm_setting_tc_config_get_num_tfilters;
nm_setting_tc_config_get_qdisc;
nm_setting_tc_config_get_tfilter;
nm_setting_tc_config_get_type;
nm_setting_tc_config_new;
nm_setting_tc_config_remove_qdisc;
nm_setting_tc_config_remove_qdisc_by_value;
nm_setting_tc_config_remove_tfilter;
nm_setting_tc_config_remove_tfilter_by_value;
libnm-core: team: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team configuration.
2017-11-06 15:47:32 +01:00
nm_setting_team_add_link_watcher;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_add_runner_tx_hash;
libnm-core: team: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team configuration.
2017-11-06 15:47:32 +01:00
nm_setting_team_clear_link_watchers;
nm_setting_team_get_link_watcher;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_get_mcast_rejoin_count;
nm_setting_team_get_mcast_rejoin_interval;
nm_setting_team_get_notify_peers_count;
nm_setting_team_get_notify_peers_interval;
libnm-core: team: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team configuration.
2017-11-06 15:47:32 +01:00
nm_setting_team_get_num_link_watchers;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_get_num_runner_tx_hash;
nm_setting_team_get_runner;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_setting_team_get_runner_active;
nm_setting_team_get_runner_agg_select_policy;
nm_setting_team_get_runner_fast_rate;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_get_runner_hwaddr_policy;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_setting_team_get_runner_min_ports;
nm_setting_team_get_runner_sys_prio;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_get_runner_tx_balancer;
nm_setting_team_get_runner_tx_balancer_interval;
nm_setting_team_get_runner_tx_hash;
libnm-core: team-port: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team port configuration.
2017-11-16 18:54:06 +01:00
nm_setting_team_port_add_link_watcher;
nm_setting_team_port_clear_link_watchers;
libnm-core: add explicit team properties to NMSettingTeamPort
2017-10-30 12:27:58 +01:00
nm_setting_team_port_get_lacp_key;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_setting_team_port_get_lacp_prio;
libnm-core: team-port: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team port configuration.
2017-11-16 18:54:06 +01:00
nm_setting_team_port_get_link_watcher;
nm_setting_team_port_get_num_link_watchers;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_setting_team_port_get_prio;
nm_setting_team_port_get_queue_id;
nm_setting_team_port_get_sticky;
libnm-core: team-port: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team port configuration.
2017-11-16 18:54:06 +01:00
nm_setting_team_port_remove_link_watcher;
nm_setting_team_port_remove_link_watcher_by_value;
libnm-core: team: expose the new link-watchers property It will allow explicit configuration of link-watchers in the team configuration.
2017-11-06 15:47:32 +01:00
nm_setting_team_remove_link_watcher;
nm_setting_team_remove_link_watcher_by_value;
libnm-core: add explicit team properties to NMSettingTeam
2017-10-12 12:02:06 +02:00
nm_setting_team_remove_runner_tx_hash;
nm_setting_team_remove_runner_tx_hash_by_value;
libnm: move symbols that were backported to 1.10.2 before 1.12 to libnm_1_10_2 See also: ae5af6b368141a5ff6fa758ed6e930e668237ca4
2017-12-11 20:21:46 +01:00
nm_tc_action_dup;
nm_tc_action_equal;
nm_tc_action_get_attribute;
nm_tc_action_get_attribute_names;
nm_tc_action_get_kind;
nm_tc_action_get_type;
nm_tc_action_new;
nm_tc_action_ref;
nm_tc_action_set_attribute;
nm_tc_action_unref;
nm_tc_qdisc_dup;
nm_tc_qdisc_equal;
nm_tc_qdisc_get_handle;
nm_tc_qdisc_get_kind;
nm_tc_qdisc_get_parent;
nm_tc_qdisc_get_type;
nm_tc_qdisc_new;
nm_tc_qdisc_ref;
nm_tc_qdisc_set_handle;
nm_tc_qdisc_unref;
nm_tc_tfilter_dup;
nm_tc_tfilter_equal;
nm_tc_tfilter_get_handle;
nm_tc_tfilter_get_kind;
nm_tc_tfilter_get_parent;
nm_tc_tfilter_get_type;
nm_tc_tfilter_new;
nm_tc_tfilter_ref;
nm_tc_tfilter_set_handle;
nm_tc_tfilter_unref;
libnm-core: team: add NMTeamLinkWatcher boxed type Team allows to specify multiple link watchers for each link. Define a link watcher object in order to allow to specify multiple ones for each Team configuration.
2017-11-02 17:13:46 +01:00
nm_team_link_watcher_arp_ping_flags_get_type;
nm_team_link_watcher_dup;
nm_team_link_watcher_equal;
nm_team_link_watcher_get_delay_down;
nm_team_link_watcher_get_delay_up;
nm_team_link_watcher_get_flags;
nm_team_link_watcher_get_init_wait;
nm_team_link_watcher_get_interval;
nm_team_link_watcher_get_missed_max;
nm_team_link_watcher_get_name;
nm_team_link_watcher_get_source_host;
nm_team_link_watcher_get_target_host;
nm_team_link_watcher_get_type;
nm_team_link_watcher_new_arp_ping;
nm_team_link_watcher_new_ethtool;
nm_team_link_watcher_new_nsna_ping;
nm_team_link_watcher_ref;
nm_team_link_watcher_unref;
libnm-core: add functionality for dealing with tc-style action specifiers Tailored to fit both nmcli and keyfile needs.
2017-11-28 09:22:49 +01:00
nm_utils_tc_action_from_str;
nm_utils_tc_action_to_str;
libnm-core: add functionality for dealing with tc-style qdisc specifiers Tailored to fit both nmcli and keyfile needs.
2017-11-18 17:17:24 +01:00
nm_utils_tc_qdisc_from_str;
nm_utils_tc_qdisc_to_str;
libnm-core: add functionality for dealing with tc-style traffic filter specifiers Tailored to fit both nmcli and keyfile needs.
2017-11-28 09:26:14 +01:00
nm_utils_tc_tfilter_from_str;
nm_utils_tc_tfilter_to_str;
libnm: add checkpoint support
2017-10-21 16:05:19 +02:00
} libnm_1_10_0;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
libnm: add mdns backported symbols from 1.10.14 Add to master branch mdns symbols that were backported to 1.10.14 to allow seamless upgrading from 1.10 to 1.16.
2018-10-19 19:12:53 +02:00
libnm_1_10_14 {
#nm_setting_connection_get_mdns@libnm_1_10_14;
#nm_setting_connection_mdns_get_type@libnm_1_10_14;
} libnm_1_10_2;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
libnm_1_12_0 {
global:
checkpoint: generate GIR information for NMCheckpointCreateFlags Note that this changes API for checkpoint_create_async() in Python via GIR. Previously it would require an integer argument, now a flags argument. But this API is still unstable, it will be introduced with 1.12.
2018-03-28 17:24:30 +02:00
nm_checkpoint_create_flags_get_type;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
nm_checkpoint_get_created;
nm_checkpoint_get_devices;
nm_checkpoint_get_rollback_timeout;
nm_checkpoint_get_type;
checkpoint: allow resetting the rollback timeout via D-Bus This allows to adjust the timeout of an existing checkpoint. The main usecase of checkpoints, is to have a fail-safe when configuring the network remotely. By allowing to reset the timeout, the user can perform a series of actions, and keep bumping the timeout. That way, the entire series is still guarded by the same checkpoint, but the user can start with short timeout, and re-adjust the timeout as he goes along. The libnm API only implements the async form (at least for now). Sync methods are fundamentally wrong with D-Bus, and it's probably not needed. Also, follow glib convenction, where the async form doesn't have the _async name suffix. Also, accept a D-Bus path as argument, not a NMCheckpoint instance. The libnm API should not be more restricted than the underlying D-Bus API. It would be cumbersome to require the user to lookup the NMCheckpoint instance first, especially since libnm doesn't provide an efficient or convenient lookup-by-path method. On the other hand, retrieving the path from a NMCheckpoint instance is always possible.
2018-03-28 08:09:56 +02:00
nm_client_checkpoint_adjust_rollback_timeout;
nm_client_checkpoint_adjust_rollback_timeout_finish;
libnm: rework checkpoint API The libnm API fir checkpoints was only introduced with 1.11. It is not yet stable, so there is still time to adjust it. Note that this changes API/ABI of the development branch. Changes: - we only add async variants of the checkpoint functions. I believe that synchronous D-Bus methods are fundamentally flawed, because they mess up the ordering of events. Rename the async functions by removing the "_async" suffix. This matches glib style, for which the async form is also not specially marked. - for function that refere to a particular checkpoint (rollback and destroy), accept the D-Bus path as string, instead of an NMCheckpoint instance. This form is more flexible, because it allows to use the function without having a NMCheckpoint instance at hand. On the other hand, if one has a NMCheckpoint instance, he can trivially obtain the path to make the call.
2018-04-04 13:33:53 +02:00
nm_client_checkpoint_create;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
nm_client_checkpoint_create_finish;
libnm: rework checkpoint API The libnm API fir checkpoints was only introduced with 1.11. It is not yet stable, so there is still time to adjust it. Note that this changes API/ABI of the development branch. Changes: - we only add async variants of the checkpoint functions. I believe that synchronous D-Bus methods are fundamentally flawed, because they mess up the ordering of events. Rename the async functions by removing the "_async" suffix. This matches glib style, for which the async form is also not specially marked. - for function that refere to a particular checkpoint (rollback and destroy), accept the D-Bus path as string, instead of an NMCheckpoint instance. This form is more flexible, because it allows to use the function without having a NMCheckpoint instance at hand. On the other hand, if one has a NMCheckpoint instance, he can trivially obtain the path to make the call.
2018-04-04 13:33:53 +02:00
nm_client_checkpoint_destroy;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
nm_client_checkpoint_destroy_finish;
libnm: rework checkpoint API The libnm API fir checkpoints was only introduced with 1.11. It is not yet stable, so there is still time to adjust it. Note that this changes API/ABI of the development branch. Changes: - we only add async variants of the checkpoint functions. I believe that synchronous D-Bus methods are fundamentally flawed, because they mess up the ordering of events. Rename the async functions by removing the "_async" suffix. This matches glib style, for which the async form is also not specially marked. - for function that refere to a particular checkpoint (rollback and destroy), accept the D-Bus path as string, instead of an NMCheckpoint instance. This form is more flexible, because it allows to use the function without having a NMCheckpoint instance at hand. On the other hand, if one has a NMCheckpoint instance, he can trivially obtain the path to make the call.
2018-04-04 13:33:53 +02:00
nm_client_checkpoint_rollback;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
nm_client_checkpoint_rollback_finish;
nm_client_get_checkpoints;
libnm: export nm_connection_get_setting_tc_config() Fixes: da13c7a1a4b91e95bbbe3014ecb6f36800c20dc8
2018-05-05 10:45:33 +02:00
nm_connection_get_setting_tc_config;
ip-tunnel: add support for tunnel flags Implement support for IP tunnel flags. Currently only some IPv6 tunnel flags are supported. Example: # nmcli connection add type ip-tunnel mode ip6ip6 \ ip-tunnel.flags ip6-ign-encap-limit,ip6-use-orig-tclass \ ifname abc ip-tunnel.parent ens8 ipv4.method disabled \ ipv6.method manual ipv6.address ::8888 remote ::42 # ip -d l 61: abc@ens8: <NOARP,UP,LOWER_UP> mtu 1460 qdisc noqueue ... link/tunnel6 :: brd ::42 promiscuity 0 ip6tnl ip6ip6 remote ::42 local :: dev ens8 encaplimit none hoplimit 0 tclass inherit ... https://bugzilla.gnome.org/show_bug.cgi?id=791846
2017-12-22 10:24:25 +01:00
nm_device_ip_tunnel_get_flags;
wifi: expose the LastScan property This is the time when the last Wi-Fi scan finished. It will help clients decide whether the AP list is fresh enough.
2018-02-25 14:53:44 +01:00
nm_device_wifi_get_last_scan;
ip-tunnel: add support for tunnel flags Implement support for IP tunnel flags. Currently only some IPv6 tunnel flags are supported. Example: # nmcli connection add type ip-tunnel mode ip6ip6 \ ip-tunnel.flags ip6-ign-encap-limit,ip6-use-orig-tclass \ ifname abc ip-tunnel.parent ens8 ipv4.method disabled \ ipv6.method manual ipv6.address ::8888 remote ::42 # ip -d l 61: abc@ens8: <NOARP,UP,LOWER_UP> mtu 1460 qdisc noqueue ... link/tunnel6 :: brd ::42 promiscuity 0 ip6tnl ip6ip6 remote ::42 local :: dev ens8 encaplimit none hoplimit 0 tclass inherit ... https://bugzilla.gnome.org/show_bug.cgi?id=791846
2017-12-22 10:24:25 +01:00
nm_ip_tunnel_flags_get_type;
libnm/remote-connection: add filename property
2018-05-28 09:23:58 +02:00
nm_remote_connection_get_filename;
all: add D-Bus property "Flags" for Settings.Connection interface The D-Bus interface already has a boolean property "Unsaved". While that is nicer too look at (in the API), adding a new flag is very cumbersome, and also has more overhead. For example, it requires extending the D-Bus API, all the way down to libnm. Add a flags argument, that will allow to add future boolean flags easier.
2018-04-05 20:06:03 +02:00
nm_remote_connection_get_flags;
mdns: add new connection property. Add support for mDNS as a connection-level property. Update ifcfg-rh and keyfile plugins to support it.
2017-11-10 14:49:27 +02:00
nm_setting_connection_get_mdns;
nm_setting_connection_mdns_get_type;
ip-tunnel: add support for tunnel flags Implement support for IP tunnel flags. Currently only some IPv6 tunnel flags are supported. Example: # nmcli connection add type ip-tunnel mode ip6ip6 \ ip-tunnel.flags ip6-ign-encap-limit,ip6-use-orig-tclass \ ifname abc ip-tunnel.parent ens8 ipv4.method disabled \ ipv6.method manual ipv6.address ::8888 remote ::42 # ip -d l 61: abc@ens8: <NOARP,UP,LOWER_UP> mtu 1460 qdisc noqueue ... link/tunnel6 :: brd ::42 promiscuity 0 ip6tnl ip6ip6 remote ::42 local :: dev ens8 encaplimit none hoplimit 0 tclass inherit ... https://bugzilla.gnome.org/show_bug.cgi?id=791846
2017-12-22 10:24:25 +01:00
nm_setting_ip_tunnel_get_flags;
libnm-core: add ipv6.dhcp-duid property allow to specify the DUID to be used int the DHCPv6 client identifier option: the dhcp-duid property accepts either a hex string or the special values "lease", "llt", "ll", "stable-llt", "stable-ll" and "stable-uuid". "lease": give priority to the DUID available in the lease file if any, otherwise fallback to a global default dependant on the dhcp client used. This is the default and reflects how the DUID was managed previously. "ll": enforce generation and use of LL type DUID based on the current hardware address. "llt": enforce generation and use of LLT type DUID based on the current hardware address and a stable time field. "stable-ll": enforce generation and use of LL type DUID based on a link layer address derived from the stable id. "stable-llt": enforce generation and use of LLT type DUID based on a link layer address and a timestamp both derived from the stable id. "stable-uuid": enforce generation and use of a UUID type DUID based on a uuid generated from the stable id.
2018-03-06 16:10:01 +01:00
nm_setting_ip6_config_get_dhcp_duid;
macsec: enable send-sci by default and make the option configurable It is safer to enable send-sci by default because, at the cost of 8-byte overhead, it makes MACsec work over bridges (note that kernel also enables it by default). While at it, also make the option configurable. https://bugzilla.redhat.com/show_bug.cgi?id=1588041
2018-06-06 15:26:17 +02:00
nm_setting_macsec_get_send_sci;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
nm_setting_vpn_get_data_keys;
nm_setting_vpn_get_secret_keys;
wifi: add support for FILS The FILS(Fast Initial Link Setup) is a specification defined by IEEE 802.11ai to speed up roaming. This patch adds support of it. I have tested with these cases. +-----+-------------------------+----------------+ | STA | AP | | |FILS | key-mgmt | result | +-----+-------------------------+----------------+ | 1 | WPA-EAP | O | +-----+-------------------------+----------------+ | 1 | WPA-EAP-SHA256 | O | +-----+-------------------------+----------------+ | 1 | FILS-SHA256 | X | +-----+-------------------------+----------------+ | 1 | FILS-SHA384 | X | +-----+-------------------------+----------------+ | 1 | WPA-EAP WPA-EAP-SHA256 | O | | | FILS-SHA256 FILS-SHA384 | WPA-EAP-SHA256 | +-----+-------------------------+----------------+ | 2 | WPA-EAP | O | +-----+-------------------------+----------------+ | 2 | WPA-EAP-SHA256 | O | +-----+-------------------------+----------------+ | 2 | FILS-SHA256 | O | +-----+-------------------------+----------------+ | 2 | FILS-SHA384 | O | +-----+-------------------------+----------------+ | 2 | WPA-EAP WPA-EAP-SHA256 | O | | | FILS-SHA256 FILS-SHA384 | FILS-SHA384 | +-----+-------------------------+----------------+ | 3 | WPA-EAP | X | +-----+-------------------------+----------------+ | 3 | WPA-EAP-SHA256 | X | +-----+-------------------------+----------------+ | 3 | FILS-SHA256 | O | +-----+-------------------------+----------------+ | 3 | FILS-SHA384 | O | +-----+-------------------------+----------------+ | 3 | WPA-EAP WPA-EAP-SHA256 | O | | | FILS-SHA256 FILS-SHA384 | FILS-SHA384 | +-----+-------------------------+----------------+ Signed-off-by: Masashi Honma <masashi.honma@gmail.com>
2018-01-16 06:28:33 +09:00
nm_setting_wireless_security_get_fils;
nm_setting_wireless_security_fils_get_type;
libnm-core: add wake-on-wlan configuration items Co-authored-by: Alfonso Sanchez-Beato <alfonso.sanchez-beato@canonical.com>
2018-05-25 16:44:52 +02:00
nm_setting_wireless_get_wake_on_wlan;
nm_setting_wireless_wake_on_wlan_get_type;
all: add D-Bus property "Flags" for Settings.Connection interface The D-Bus interface already has a boolean property "Unsaved". While that is nicer too look at (in the API), adding a new flag is very cumbersome, and also has more overhead. For example, it requires extending the D-Bus API, all the way down to libnm. Add a flags argument, that will allow to add future boolean flags easier.
2018-04-05 20:06:03 +02:00
nm_settings_connection_flags_get_type;
libnm: add nm_utils_get_timestamp_msec()
2018-06-15 14:15:27 +02:00
nm_utils_get_timestamp_msec;
libnm: add nm_vpn_service_plugin_shutdown() API Otherwise, the only way to disconnect the NMVpnServicePlugin instance is by completely unrefing it. However, often it is not so easy to ensure that nobody else is still keeping the instance alive, after the point where we no longer want to handle D-Bus requests. nm_vpn_service_plugin_shutdown() to the rescue.
2018-01-15 15:23:39 +01:00
nm_vpn_service_plugin_shutdown;
libnm: adjust symbol versioning after backporting team API to 1.10.2 The team API was backported to nm-1-10 branch. It will be released both as 1.12.0 and 1.10.2. To ensure the upgrade path from 1.10.2+ to 1.12+ works, the symbols in libnm must be present on both versions. Usually, we would duplicate the symbols on master via NM_BACKPORT_SYMBOL() macro. However, as we are sure that we will release 1.10.2 before 1.12.0, we can just update the linker version of these symbols. So, although the symbols will be first released on major release 1.12.0, their linker version tag is libnm_1_10_2, to ease upgrade and to avoid duplicating the symbols.
2017-12-08 13:47:34 +01:00
} libnm_1_10_0;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
libnm: fix missing symbols in libnm ABI Also backport the ABI to 1.12.2 (and thus, don't bother initially adding the API as libnm_1_14_0).
2018-06-30 11:51:56 +02:00
libnm_1_12_2 {
nm_connection_get_setting_ovs_bridge;
nm_connection_get_setting_ovs_interface;
nm_connection_get_setting_ovs_patch;
nm_connection_get_setting_ovs_port;
nm_connection_get_setting_tun;
libnm: add nm_device_ovs_*_get_slaves() They were missing. Add them to the 1.12.2 node, because they've been backported. See-also: https://github.com/NetworkManager/NetworkManager/pull/172
2018-07-24 19:14:05 +02:00
nm_device_ovs_bridge_get_slaves;
nm_device_ovs_port_get_slaves;
libnm: fix missing symbols in libnm ABI Also backport the ABI to 1.12.2 (and thus, don't bother initially adding the API as libnm_1_14_0).
2018-06-30 11:51:56 +02:00
} libnm_1_12_0;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
libnm_1_14_0 {
global:
all: add connection.multi-connect property for wildcard profiles Add a new option that allows to activate a profile multiple times (at the same time). Previoulsy, all profiles were implicitly NM_SETTING_CONNECTION_MULTI_CONNECT_SINGLE, meaning, that activating a profile that is already active will deactivate it first. This will make more sense, as we also add more match-options how profiles can be restricted to particular devices. We already have connection.type, connection.interface-name, and (ethernet|wifi).mac-address to restrict a profile to particular devices. For example, it is however not possible to specify a wildcard like "eth*" to match a profile to a set of devices by interface-name. That is another missing feature, and once we extend the matching capabilities, it makes more sense to activate a profile multiple times. See also https://bugzilla.redhat.com/show_bug.cgi?id=997998, which previously changed that a connection is restricted to a single activation at a time. This work relaxes that again. This only adds the new property, it is not used nor implemented yet. https://bugzilla.redhat.com/show_bug.cgi?id=1555012
2018-04-10 11:45:35 +02:00
nm_connection_multi_connect_get_type;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
nm_device_6lowpan_get_type;
libnm: introduce NMDeviceWireGuard
2018-03-13 13:42:38 +00:00
nm_device_wireguard_get_fwmark;
nm_device_wireguard_get_listen_port;
nm_device_wireguard_get_public_key;
nm_device_wireguard_get_type;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
nm_device_wpan_get_type;
nm_setting_6lowpan_get_type;
libnm-core: add connection.llmnr property
2018-08-31 10:48:18 +02:00
nm_setting_connection_get_llmnr;
all: add connection.multi-connect property for wildcard profiles Add a new option that allows to activate a profile multiple times (at the same time). Previoulsy, all profiles were implicitly NM_SETTING_CONNECTION_MULTI_CONNECT_SINGLE, meaning, that activating a profile that is already active will deactivate it first. This will make more sense, as we also add more match-options how profiles can be restricted to particular devices. We already have connection.type, connection.interface-name, and (ethernet|wifi).mac-address to restrict a profile to particular devices. For example, it is however not possible to specify a wildcard like "eth*" to match a profile to a set of devices by interface-name. That is another missing feature, and once we extend the matching capabilities, it makes more sense to activate a profile multiple times. See also https://bugzilla.redhat.com/show_bug.cgi?id=997998, which previously changed that a connection is restricted to a single activation at a time. This work relaxes that again. This only adds the new property, it is not used nor implemented yet. https://bugzilla.redhat.com/show_bug.cgi?id=1555012
2018-04-10 11:45:35 +02:00
nm_setting_connection_get_multi_connect;
libnm-core: add connection.llmnr property
2018-08-31 10:48:18 +02:00
nm_setting_connection_llmnr_get_type;
libnm, cli, ifcfg-rh: add NMSettingEthtool setting Note that in NetworkManager API (D-Bus, libnm, and nmcli), the features are called "feature-xyz". The "feature-" prefix is used, because NMSettingEthtool possibly will gain support for options that are not only -K|--offload|--features, for example -C|--coalesce. The "xzy" suffix is either how ethtool utility calls the feature ("tso", "rx"). Or, if ethtool utility specifies no alias for that feature, it's the name from kernel's ETH_SS_FEATURES ("tx-tcp6-segmentation"). If possible, we prefer ethtool utility's naming. Also note, how the features "feature-sg", "feature-tso", and "feature-tx" actually refer to multiple underlying kernel features at once. This too follows what ethtool utility does. The functionality is not yet implemented server-side.
2018-07-16 23:37:55 +02:00
nm_setting_ethtool_clear_features;
nm_setting_ethtool_get_feature;
nm_setting_ethtool_get_type;
nm_setting_ethtool_new;
nm_setting_ethtool_set_feature;
all: add 'match' setting Add a new 'match' setting containing properties to match a connection to devices. At the moment only the interface-name property is present and, contrary to connection.interface-name, it allows the use of wildcards.
2018-08-07 15:52:56 +02:00
nm_setting_match_add_interface_name;
nm_setting_match_clear_interface_names;
nm_setting_match_get_interface_name;
nm_setting_match_get_interface_names;
nm_setting_match_get_num_interface_names;
nm_setting_match_get_type;
nm_setting_match_remove_interface_name;
nm_setting_match_remove_interface_name_by_value;
libnm-core: add SR-IOV setting Add a setting containing SR-IOV parameters.
2018-05-25 12:05:24 +02:00
nm_setting_sriov_add_vf;
nm_setting_sriov_clear_vfs;
nm_setting_sriov_get_autoprobe_drivers;
nm_setting_sriov_get_num_vfs;
nm_setting_sriov_get_total_vfs;
nm_setting_sriov_get_type;
nm_setting_sriov_get_vf;
nm_setting_sriov_new;
nm_setting_sriov_remove_vf;
nm_setting_sriov_remove_vf_by_index;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
nm_setting_wpan_get_type;
libnm-core: add SR-IOV setting Add a setting containing SR-IOV parameters.
2018-05-25 12:05:24 +02:00
nm_sriov_vf_add_vlan;
nm_sriov_vf_dup;
nm_sriov_vf_equal;
nm_sriov_vf_get_attribute;
nm_sriov_vf_get_attribute_names;
nm_sriov_vf_get_index;
nm_sriov_vf_get_type;
nm_sriov_vf_get_vlan_ids;
nm_sriov_vf_get_vlan_protocol;
nm_sriov_vf_get_vlan_qos;
nm_sriov_vf_new;
nm_sriov_vf_ref;
nm_sriov_vf_remove_vlan;
nm_sriov_vf_set_attribute;
nm_sriov_vf_set_vlan_protocol;
nm_sriov_vf_set_vlan_qos;
nm_sriov_vf_unref;
nm_sriov_vf_vlan_protocol_get_type;
libnm: introduce NMTernary enum Add a new enum that can be used where we need a boolean value that can be overridden globally.
2018-05-24 13:43:32 +02:00
nm_ternary_get_type;
libnm-core: add SR-IOV setting Add a setting containing SR-IOV parameters.
2018-05-25 12:05:24 +02:00
nm_utils_sriov_vf_from_str;
nm_utils_sriov_vf_to_str;
libnm: fix symbol versioning for new symbols in 1.14 ABI Fixes: 191c9c7f0d941a34446d26637db535a3ec1c57d8
2018-06-30 12:03:30 +02:00
} libnm_1_12_0;
libnm: add support for per-device & per-AF connectivity status
2018-07-03 20:42:50 +02:00
libnm: belatedly expose nm_ethtool_optname_is_feature() in libnm Also, plan right away to backport this symbol all the way back to 1.14.8. As such, we only need to add it once, with the right linker version "libnm_1_14_8". But still, the symbols first appears on a major release 1.20.0.
2019-06-11 14:47:26 +02:00
libnm_1_14_8 {
nm_ethtool_optname_is_feature;
} libnm_1_14_0;
libnm: add support for per-device & per-AF connectivity status
2018-07-03 20:42:50 +02:00
libnm_1_16_0 {
global:
all: return output dictionary from "AddAndActivate2" Add a "a{sv}" output argument to "AddAndActivate2" D-Bus API. "AddAndActivate2" replaces "AddAndActivate" with more options. It also has a dictionary argument to be forward compatible so that we hopefully won't need an "AddAndActivate3". However, it lacked a similar output dictionary. Add it for future extensibility. I think this is really to workaround a shortcoming of D-Bus, which does provide strong typing and type information about its API, but does not allow to extend an existing API in a backward compatible manner. So we either resort to Method(), Method2(), Method3() variants, or a catch-all variant with a generic "a{sv}" input/output argument. In libnm, rename "nm_client_add_and_activate_connection_options()" to "nm_client_add_and_activate_connection2()". I think libnm API should have an obvious correspondence with D-Bus API. Or stated differently, if "AddAndActivateOptions" would be a better name, then the D-Bus API should be renamed. We should prefer one name over the other, but regardless of which is preferred, the naming for D-Bus and libnm API should correspond. In this case, I do think that AddAndActivate2() is a better name than AddAndActivateOptions(). Hence I rename the libnm API. Also, unless necessary, let libnm still call "AddAndActivate" instead of "AddAndActivate2". Our backward compatibility works the way that libnm requires a server version at least as new as itself. As such, libnm theoretically could assume that server version is new enough to support "AddAndActivate2" and could always use the more powerful variant. However, we don't need to break compatibility intentionally and for little gain. Here, it's easy to let libnm also handle old server API, by continuing to use "AddAndActivate" for nm_client_add_and_activate_connection(). Note that during package update, we don't restart the currently running NetworkManager instance. In such a scenario, it can easily happen that nmcli/libnm is newer than the server version. Let's try a bit harder to not break that. Changes as discussed in [1]. [1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/37#note_79876
2018-12-20 07:48:31 +01:00
nm_client_add_and_activate_connection2;
nm_client_add_and_activate_connection2_finish;
libnm: add support for per-device & per-AF connectivity status
2018-07-03 20:42:50 +02:00
nm_device_get_connectivity;
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
nm_device_wifi_p2p_get_hw_address;
nm_device_wifi_p2p_get_peers;
nm_device_wifi_p2p_get_type;
libnm: Add async start/stop routines for P2P find operations These were dropped earlier as new sync API must not be the primary way of calling new routines in libnm. In this particular case the DBus calls are simple and unlikely to fail. Most users should use the normal async API and call the finish routine. However, if the API user is not interested in the result, then they can simply set the callback to NULL to ignore it. [thaller@redhat.com: added options argument to start-find method]
2019-01-28 18:50:31 +01:00
nm_device_wifi_p2p_start_find;
nm_device_wifi_p2p_start_find_finish;
nm_device_wifi_p2p_stop_find;
nm_device_wifi_p2p_stop_find_finish;
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
nm_setting_wifi_p2p_get_peer;
nm_setting_wifi_p2p_get_type;
core/setting-wifi-p2p: Add WFD IEs property to P2P settings This is a protocol specific extension to Wi-Fi frames which need to be set in certain conditions. The P2P device will use this to update the corresponding wpa_supplicant property.
2019-02-18 10:25:34 +01:00
nm_setting_wifi_p2p_get_wfd_ies;
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
nm_setting_wifi_p2p_get_wps_method;
nm_setting_wifi_p2p_new;
libnm: add NMWireGuardPeer and libnm support for peers
2019-01-30 12:36:13 +01:00
nm_setting_wireguard_append_peer;
nm_setting_wireguard_clear_peers;
libnm,cli: add NMSettingWireGuard For now only add the core settings, no peers' data. To support peers and the allowed-ips of the peers is more complicated and will be done later. It's more complicated because these are nested lists (allowed-ips) inside a list (peers). That is quite unusual and to conveniently support that in D-Bus API, in keyfile format, in libnm, and nmcli, is a effort. Also, it's further complicated by the fact that each peer has a secret (the preshared-key). Thus we probably need secret flags for each peer, which is a novelty as well (until now we require a fixed set of secrets per profile that is well known).
2018-12-27 16:48:30 +01:00
nm_setting_wireguard_get_fwmark;
nm_setting_wireguard_get_listen_port;
wireguard: add "mtu" setting for WireGuard profiles This adds new API for 1.16.0 and is an ABI break since 1.16-rc1. (cherry picked from commit d5e93ae613fd355351bdf37530cae3d3dfb4e5ba)
2019-03-02 23:33:15 +01:00
nm_setting_wireguard_get_mtu;
libnm: add NMWireGuardPeer and libnm support for peers
2019-01-30 12:36:13 +01:00
nm_setting_wireguard_get_peer;
nm_setting_wireguard_get_peer_by_public_key;
wireguard: add "peer-routes" setting for WireGuard profiles This setting is not yet implemented. This adds new API for 1.16.0 and is an ABI break since 1.16-rc1. (cherry picked from commit d719ad31f096583c501af3bea01a01ffd72337d5)
2019-03-04 09:26:23 +01:00
nm_setting_wireguard_get_peer_routes;
libnm: add NMWireGuardPeer and libnm support for peers
2019-01-30 12:36:13 +01:00
nm_setting_wireguard_get_peers_len;
libnm,cli: add NMSettingWireGuard For now only add the core settings, no peers' data. To support peers and the allowed-ips of the peers is more complicated and will be done later. It's more complicated because these are nested lists (allowed-ips) inside a list (peers). That is quite unusual and to conveniently support that in D-Bus API, in keyfile format, in libnm, and nmcli, is a effort. Also, it's further complicated by the fact that each peer has a secret (the preshared-key). Thus we probably need secret flags for each peer, which is a novelty as well (until now we require a fixed set of secrets per profile that is well known).
2018-12-27 16:48:30 +01:00
nm_setting_wireguard_get_private_key;
nm_setting_wireguard_get_private_key_flags;
nm_setting_wireguard_get_type;
nm_setting_wireguard_new;
libnm: add NMWireGuardPeer and libnm support for peers
2019-01-30 12:36:13 +01:00
nm_setting_wireguard_remove_peer;
nm_setting_wireguard_set_peer;
team: add support for 'vlanid' link-watchers property Add support for the teaming arp_ping link watcher 'vlanid' property. Signed-off-by: Patrick Talbert <ptalbert@redhat.com> [thaller@redhat.com: minor fixes to original patch] https://bugzilla.redhat.com/show_bug.cgi?id=1652931
2018-12-05 15:26:50 +01:00
nm_team_link_watcher_get_vlanid;
nm_team_link_watcher_new_arp_ping2;
libnm: rename and expose nm_utils_base64secret_decode() in libnm A NetworkManager client requires an API to validate and decode a base64 secret -- like it is used by WireGuard. If we don't have this as part of the API, it's inconvenient. Expose it. Rename it from _nm_utils_wireguard_decode_key(), to give it a more general name. Also, rename _nm_utils_wireguard_normalize_key() to nm_utils_base64secret_normalize(). But this one we keep as internal API. The user will care more about validating and decoding the base64 key. To convert the key back to base64, we don't need a public API in libnm. This is another ABI change since 1.16-rc1. (cherry picked from commit e46ba0186720bfe5e31dcad9a5001a415deb9ce6)
2019-03-02 17:10:25 +01:00
nm_utils_base64secret_decode;
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
nm_wifi_p2p_peer_connection_valid;
nm_wifi_p2p_peer_filter_connections;
nm_wifi_p2p_peer_get_flags;
nm_wifi_p2p_peer_get_hw_address;
nm_wifi_p2p_peer_get_last_seen;
nm_wifi_p2p_peer_get_manufacturer;
nm_wifi_p2p_peer_get_model;
nm_wifi_p2p_peer_get_model_number;
nm_wifi_p2p_peer_get_name;
nm_wifi_p2p_peer_get_serial;
nm_wifi_p2p_peer_get_strength;
nm_wifi_p2p_peer_get_type;
nm_wifi_p2p_peer_get_wfd_ies;
libnm: add NMWireGuardPeer and libnm support for peers
2019-01-30 12:36:13 +01:00
nm_wireguard_peer_append_allowed_ip;
nm_wireguard_peer_clear_allowed_ips;
nm_wireguard_peer_cmp;
nm_wireguard_peer_get_allowed_ip;
nm_wireguard_peer_get_allowed_ips_len;
nm_wireguard_peer_get_endpoint;
nm_wireguard_peer_get_persistent_keepalive;
nm_wireguard_peer_get_preshared_key;
nm_wireguard_peer_get_preshared_key_flags;
nm_wireguard_peer_get_public_key;
nm_wireguard_peer_get_type;
nm_wireguard_peer_is_sealed;
nm_wireguard_peer_is_valid;
nm_wireguard_peer_new;
nm_wireguard_peer_new_clone;
nm_wireguard_peer_ref;
nm_wireguard_peer_remove_allowed_ip;
nm_wireguard_peer_seal;
nm_wireguard_peer_set_endpoint;
nm_wireguard_peer_set_persistent_keepalive;
nm_wireguard_peer_set_preshared_key;
nm_wireguard_peer_set_preshared_key_flags;
nm_wireguard_peer_set_public_key;
nm_wireguard_peer_unref;
libnm: add support for per-device & per-AF connectivity status
2018-07-03 20:42:50 +02:00
} libnm_1_14_0;
all: add vlan-filtering and vlan-default-pvid bridge properties
2019-03-15 08:53:37 +01:00
libnm_1_18_0 {
global:
libnm-core: add vlans property to bridge-port setting
2019-03-16 17:21:35 +01:00
nm_bridge_vlan_cmp;
libnm-core: add bridge vlan conversion utils
2019-03-19 15:35:28 +01:00
nm_bridge_vlan_from_str;
libnm-core: add vlans property to bridge-port setting
2019-03-16 17:21:35 +01:00
nm_bridge_vlan_get_type;
all: support bridge vlan ranges In some cases it is convenient to specify ranges of bridge vlans, as already supported by iproute2 and natively by kernel. With this commit it becomes possible to add a range in this way: nmcli connection modify eth0-slave +bridge-port.vlans "100-200 untagged" vlan ranges can't be PVIDs because only one PVID vlan can exist. https://bugzilla.redhat.com/show_bug.cgi?id=1652910 (cherry picked from commit 70935157771b1de39f27d20e50112efcc50d1f5c)
2019-04-15 15:14:33 +02:00
nm_bridge_vlan_get_vid_range;
libnm-core: add vlans property to bridge-port setting
2019-03-16 17:21:35 +01:00
nm_bridge_vlan_is_pvid;
nm_bridge_vlan_is_sealed;
nm_bridge_vlan_is_untagged;
nm_bridge_vlan_new;
nm_bridge_vlan_new_clone;
nm_bridge_vlan_ref;
nm_bridge_vlan_seal;
nm_bridge_vlan_set_pvid;
nm_bridge_vlan_set_untagged;
libnm-core: add bridge vlan conversion utils
2019-03-19 15:35:28 +01:00
nm_bridge_vlan_to_str;
libnm-core: add vlans property to bridge-port setting
2019-03-16 17:21:35 +01:00
nm_bridge_vlan_unref;
libnm: add NMIPRoutingRule API Add NMIPRoutingRule API with a few basic rule properties. More properties will be added later as we want to support them. Also, add to/from functions for string/GVariant representations. These will be needed to persist/load/exchange rules. The to-string format follows the `ip rule add` syntax, with the aim to be partially compatible. Full compatibility is not possible though, for various reasons (see code comment).
2019-03-13 09:18:49 +01:00
nm_ip_routing_rule_as_string_flags_get_type;
nm_ip_routing_rule_cmp;
nm_ip_routing_rule_from_string;
nm_ip_routing_rule_get_action;
nm_ip_routing_rule_get_addr_family;
nm_ip_routing_rule_get_destination_port_end;
nm_ip_routing_rule_get_destination_port_start;
nm_ip_routing_rule_get_from;
nm_ip_routing_rule_get_from_len;
nm_ip_routing_rule_get_fwmark;
nm_ip_routing_rule_get_fwmask;
nm_ip_routing_rule_get_iifname;
nm_ip_routing_rule_get_invert;
nm_ip_routing_rule_get_ipproto;
nm_ip_routing_rule_get_oifname;
nm_ip_routing_rule_get_priority;
nm_ip_routing_rule_get_source_port_end;
nm_ip_routing_rule_get_source_port_start;
nm_ip_routing_rule_get_table;
nm_ip_routing_rule_get_to;
nm_ip_routing_rule_get_to_len;
nm_ip_routing_rule_get_tos;
nm_ip_routing_rule_get_type;
nm_ip_routing_rule_is_sealed;
nm_ip_routing_rule_new;
nm_ip_routing_rule_new_clone;
nm_ip_routing_rule_ref;
nm_ip_routing_rule_seal;
nm_ip_routing_rule_set_action;
nm_ip_routing_rule_set_destination_port;
nm_ip_routing_rule_set_from;
nm_ip_routing_rule_set_fwmark;
nm_ip_routing_rule_set_iifname;
nm_ip_routing_rule_set_invert;
nm_ip_routing_rule_set_ipproto;
nm_ip_routing_rule_set_oifname;
nm_ip_routing_rule_set_priority;
nm_ip_routing_rule_set_source_port;
nm_ip_routing_rule_set_table;
nm_ip_routing_rule_set_to;
nm_ip_routing_rule_set_tos;
nm_ip_routing_rule_to_string;
nm_ip_routing_rule_unref;
nm_ip_routing_rule_validate;
libnm: add nm_lldp_neighbor_get_attr_value() The function provides access to the GVariant representing a LLDP attribute.
2019-01-21 11:53:48 +01:00
nm_lldp_neighbor_get_attr_value;
libnm-core: add vlans property to bridge setting
2019-03-21 16:49:55 +01:00
nm_setting_bridge_add_vlan;
nm_setting_bridge_clear_vlans;
nm_setting_bridge_get_num_vlans;
nm_setting_bridge_get_vlan;
all: add vlan-filtering and vlan-default-pvid bridge properties
2019-03-15 08:53:37 +01:00
nm_setting_bridge_get_vlan_default_pvid;
libnm: add NMIPRoutingRule API Add NMIPRoutingRule API with a few basic rule properties. More properties will be added later as we want to support them. Also, add to/from functions for string/GVariant representations. These will be needed to persist/load/exchange rules. The to-string format follows the `ip rule add` syntax, with the aim to be partially compatible. Full compatibility is not possible though, for various reasons (see code comment).
2019-03-13 09:18:49 +01:00
nm_setting_bridge_get_vlan_filtering;
libnm-core: add vlans property to bridge-port setting
2019-03-16 17:21:35 +01:00
nm_setting_bridge_port_add_vlan;
nm_setting_bridge_port_clear_vlans;
nm_setting_bridge_port_get_num_vlans;
nm_setting_bridge_port_get_vlan;
nm_setting_bridge_port_remove_vlan;
nm_setting_bridge_port_remove_vlan_by_vid;
libnm-core: add vlans property to bridge setting
2019-03-21 16:49:55 +01:00
nm_setting_bridge_remove_vlan;
nm_setting_bridge_remove_vlan_by_vid;
libnm: add API to NMSettingIPConfig for routing rules
2019-03-14 12:04:21 +01:00
nm_setting_ip_config_add_routing_rule;
nm_setting_ip_config_clear_routing_rules;
nm_setting_ip_config_get_num_routing_rules;
nm_setting_ip_config_get_routing_rule;
nm_setting_ip_config_remove_routing_rule;
core/qdisc: add support for attributes
2019-04-09 09:10:43 +02:00
nm_tc_qdisc_get_attribute;
nm_tc_qdisc_get_attribute_names;
nm_tc_qdisc_set_attribute;
all: add vlan-filtering and vlan-default-pvid bridge properties
2019-03-15 08:53:37 +01:00
} libnm_1_16_0;
libnm/modem: add device id getter
2019-05-06 17:45:30 +02:00
libnm_1_20_0 {
global:
core,libnm: add AddConnection2() D-Bus API to block autoconnect from the start It should be possible to add a profile with autoconnect blocked form the start. Update2() has a %NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT flag to block autoconnect, and so we need something similar when adding a connection. As the existing AddConnection() and AddConnectionUnsaved() API is not extensible, add AddConnection2() that has flags and room for additional arguments. Then add and implement the new flag %NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT for AddConnection2(). Note that libnm's nm_client_add_connection2() API can completely replace the existing nm_client_add_connection_async() call. In particular, it will automatically prefer to call the D-Bus methods AddConnection() and AddConnectionUnsaved(), in order to work with server versions older than 1.20. The purpose of this is that when upgrading the package, the running NetworkManager might still be older than the installed libnm. Anyway, so since nm_client_add_connection2_finish() also has a result output, the caller needs to decide whether he cares about that result. Hence it has an argument ignore_out_result, which allows to fallback to the old API. One might argue that a caller who doesn't care about the output results while still wanting to be backward compatible, should itself choose to call nm_client_add_connection_async() or nm_client_add_connection2(). But instead, it's more convenient if the new function can fully replace the old one, so that the caller does not need to switch which start/finish method to call. https://bugzilla.redhat.com/show_bug.cgi?id=1677068
2019-07-09 15:22:01 +02:00
nm_client_add_connection2;
nm_client_add_connection2_finish;
libnm,core: Add ConnectivityCheckUri property and accessors So that applications like GNOME Shell can hit the same URI to show the captive portal login page. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/209
2019-07-22 15:55:15 +01:00
nm_client_connectivity_check_get_uri;
libnm/modem: add APN getter
2019-05-06 17:47:01 +02:00
nm_device_modem_get_apn;
libnm/modem: add device id getter
2019-05-06 17:45:30 +02:00
nm_device_modem_get_device_id;
libnm/modem: add network id getter
2019-05-06 17:46:31 +02:00
nm_device_modem_get_operator_code;
libnm,core: add support for "suppress_prefixlength" rule attribute WireGuard's wq-quick configures such rules to avoid routing loops. While we currently don't have an automatic solution for this, at least we should support it via explicit user configuration. One problem is that suppress_prefixlength is relatively new and kernel might not support this attribute. That can lead to odd results, because the NetworkManager is valid but it cannot be configured on the current kernel. But this is a general problem, and we would require a general solution. The solution cannot be to only support rule attributes that are supported by the oldest possible kernel. It's not clear how much of a problem there really is, or which general solution is required (if any).
2019-07-11 18:54:48 +02:00
nm_ip_routing_rule_get_suppress_prefixlength;
nm_ip_routing_rule_set_suppress_prefixlength;
libnm,cli,ifcfg-rh: add connection:wait-device-timeout property Initscripts already honor the DEVTIMEOUT variable (rh #1171917). Don't make this a property only supported by initscripts. Every useful property should also be supported by keyfile and it should be accessible via D-Bus. Also, I will soon drop NMSIfcfgConnection, so handling this would require extra code. It's easier when DEVTIMEOUT is a regular property of the connection profile. The property is not yet implemented. ifcfg-rh still uses the old implementation, and keyfile is not yet adjusted. Since both keyfile and ifcfg-rh will both be rewritten soon, this property will be implemented then.
2019-07-01 10:01:28 +02:00
nm_setting_connection_get_wait_device_timeout;
libnm: add nm_setting_ethtool_get_optnames() function It's rather limiting if we have no API to ask NMSettingEthtool which options are set. Note that currently NMSettingEthtool only supports offload features. In the future, it should also support other options like coalesce or ring options. Hence, this returns all option names, not only features. If a caller needs to know whether the name is an option name, he/she should call nm_ethtool_optname_is_feature().
2019-06-11 11:20:53 +02:00
nm_setting_ethtool_get_optnames;
libnm-core: add ovs-dpdk setting
2019-06-11 15:53:05 +02:00
nm_setting_ovs_dpdk_get_devargs;
nm_setting_ovs_dpdk_get_type;
nm_setting_ovs_dpdk_new;
wireguard: support configuring policy routing to avoid routing loops For WireGuard (like for all IP-tunnels and IP-based VPNs), the IP addresses of the peers must be reached outside the tunnel/VPN itself. For VPN connections, NetworkManager usually adds a direct /32 route to the external VPN gateway to the underlying device. For WireGuard that is not done, because injecting a route to another device is ugly and error prone. Worse: WireGuard with automatic roaming and multiple peers makes this more complicated. This is commonly a problem when setting the default-route via the VPN, but there are also other subtle setups where special care must be taken to prevent such routing loops. WireGuard's wg-quick provides a simple, automatic solution by adding two policy routing rules and relying on the WireGuard packets having a fwmark set (see [1]). Let's also do that. Add new properties "wireguard.ip4-auto-default-route" and "wireguard.ip6-auto-default-route" to enable/disable this. Note that the default value lets NetworkManager automatically choose whether to enable it (depending on whether there are any peers that have a default route). This means, common scenarios should now work well without additional configuration. Note that this is also a change in behavior and upon package upgrade NetworkManager may start adding policy routes (if there are peers that have a default-route). This is a change in behavior, as the user already clearly had this setup working and configured some working solution already. The new automatism picks the rule priority automatically and adds the default-route to the routing table that has the same number as the fwmark. If any of this is unsuitable, then the user is free to disable this automatism. Note that since 1.18.0 NetworkManager supports policy routing (*). That means, what this automatism does can be also achieved via explicit configuration of the profile, which gives the user more flexibility to adjust all parameters explicitly). (*) but only since 1.20.0 NetworkManager supports the "suppress_prefixlength" rule attribute, which makes it impossible to configure exactly this rule-based solution with 1.18.0 NetworkManager. [1] https://www.wireguard.com/netns/#improved-rule-based-routing
2019-04-30 17:48:46 +02:00
nm_setting_wireguard_get_ip4_auto_default_route;
nm_setting_wireguard_get_ip6_auto_default_route;
core,libnm: add AddConnection2() D-Bus API to block autoconnect from the start It should be possible to add a profile with autoconnect blocked form the start. Update2() has a %NM_SETTINGS_UPDATE2_FLAG_BLOCK_AUTOCONNECT flag to block autoconnect, and so we need something similar when adding a connection. As the existing AddConnection() and AddConnectionUnsaved() API is not extensible, add AddConnection2() that has flags and room for additional arguments. Then add and implement the new flag %NM_SETTINGS_ADD_CONNECTION2_FLAG_BLOCK_AUTOCONNECT for AddConnection2(). Note that libnm's nm_client_add_connection2() API can completely replace the existing nm_client_add_connection_async() call. In particular, it will automatically prefer to call the D-Bus methods AddConnection() and AddConnectionUnsaved(), in order to work with server versions older than 1.20. The purpose of this is that when upgrading the package, the running NetworkManager might still be older than the installed libnm. Anyway, so since nm_client_add_connection2_finish() also has a result output, the caller needs to decide whether he cares about that result. Hence it has an argument ignore_out_result, which allows to fallback to the old API. One might argue that a caller who doesn't care about the output results while still wanting to be backward compatible, should itself choose to call nm_client_add_connection_async() or nm_client_add_connection2(). But instead, it's more convenient if the new function can fully replace the old one, so that the caller does not need to switch which start/finish method to call. https://bugzilla.redhat.com/show_bug.cgi?id=1677068
2019-07-09 15:22:01 +02:00
nm_settings_add_connection2_flags_get_type;
libnm/modem: add device id getter
2019-05-06 17:45:30 +02:00
} libnm_1_18_0;
setting-gsm: add auto-config property This will make NetworkManager look up APN, username, and password in the Mobile Broadband Provider database. It is mutually exclusive with the apn, username and password properties. If that is the case, the connection will be normalized to auto-config=false. This makes it convenient for the user to turn off the automatism by just setting the apn.
2019-09-09 20:22:19 +02:00
libnm: adjust symbol versioning after backporting 802-1x.optional to 1.20.6 NM 1.22 is not released yet and 1.20.6 will happen before 1.22.0, so we can introduce the new API with version libnm_1_20_6 in both releases without having duplicate symbols on 1.22.
2019-11-06 13:36:32 +01:00
libnm_1_20_6 {
global:
nm_setting_802_1x_get_optional;
} libnm_1_20_0;
setting-gsm: add auto-config property This will make NetworkManager look up APN, username, and password in the Mobile Broadband Provider database. It is mutually exclusive with the apn, username and password properties. If that is the case, the connection will be normalized to auto-config=false. This makes it convenient for the user to turn off the automatism by just setting the apn.
2019-09-09 20:22:19 +02:00
libnm_1_22_0 {
global:
libnm: fix leaking internal GMainContext for synchronously initialized NMClient NMClient makes asynchronous D-Bus calls via g_dbus_connection_call(). This references the current GMainContext to later invoke the asynchronous callback. Even when we cancel the asynchronous call, the callback will still be invoked (later) to complete the request. In particular this means when we destroy (unref) an NMClient, there are quite possibly pending requests in the GMainContext. Although they are cancelled, they keep the GMainContext alive. With synchronous initialization, we have an internal GMainContext. When we destroy the NMClient, we cannot just unhook the integrated source, instead, we need to keep it integrated in the caller's main context, as long as there are pending requests. Add a mechanism to track those pending requests and fix the leak for the internal GMainContext. Also expose the same mechanism to the user via a new API called nm_client_get_context_busy_watcher(). This allows the user to know when it can stop iterating the main context and when all resources are reclaimed. For example the following will lead to a crash: for i in range(1,2000): nmc = NM.Client.new(None) This creates a number of NMClient instances and destroys them again. Note that here the GMainContext is never iterated, because synchronous initialization does not iterate the caller's context. So, while we correctly unref and dispose the created NMClient instances, there are pending requests left in the inner GMainContext. These pile up and soon the program will crash because it runs out of file descriptors. We can have a similar problem with asynchronous initialization, when we create a new GMainContext per client, and don't iterate it after we are done with the client. Note that this patch does not avoid the problem in general. The problem cannot be avoided, the user must iterate the main contex at some point. Otherwise resources (memory and file descriptors) will be leaked. Fixes: ce0e898fb476 ('libnm: refactor caching of D-Bus objects in NMClient') https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/347
2019-11-26 00:23:41 +01:00
nm_client_get_context_busy_watcher;
libnm: add NM_CLIENT_DBUS_CONNECTION property The used GDBusConnection should be configurable when creating the NMClient instance. Automatically choosing one of the g_bus_get() singletons is fine by default, but it's an unnecessary limitation.
2019-10-12 14:59:23 +02:00
nm_client_get_dbus_connection;
libnm: add NM_CLIENT_DBUS_NAME_OWNER property It's not yet implemented. But obviously it's interesting to get the name owner to which the NMClient is currently connected. Note only that: the name-owner property really says whether NM is currently running or not.
2019-10-15 16:08:36 +02:00
nm_client_get_dbus_name_owner;
libnm: add nm_client_get_main_context() function The NMClient is associated with a certain context. Add a getter function to give the context. The context is really not internal API of NMClient, that is because the user must iterate this context and be aware of it.
2019-11-26 13:31:11 +01:00
nm_client_get_main_context;
libnm: refactor caching of D-Bus objects in NMClient No longer use GDBusObjectMangaerClient and gdbus-codegen generated classes for the NMClient cache. Instead, use GDBusConnection directly and a custom implementation (NMLDBusObject) for caching D-Bus' ObjectManager data. CHANGES ------- - This is a complete rework. I think the previous implementation was difficult to understand. There were unfixed bugs and nobody understood the code well enough to fix them. Maybe somebody out there understood the code, but I certainly did not. At least nobody provided patches to fix those issues. I do believe that this implementation is more straightforward and easier to understand. It removes a lot of layers of code. Whether this claim of simplicity is true, each reader must decide for himself/herself. Note that it is still fairly complex. - There was a lingering performance issue with large number of D-Bus objects. The patch tries hard that the implementation scales well. Of course, when we cache N objects that have N-to-M references to other, we still are fundamentally O(N*M) for runtime and memory consumption (with M being the number of references between objects). But each part should behave efficiently and well. - Play well with GMainContext. libnm code (NMClient) is generally not thread safe. However, it should work to use multiple instances in parallel, as long as each access to a NMClient is through the caller's GMainContext. This follows glib's style and effectively allows to use NMClient in a multi threaded scenario. This implies to stick to a main context upon construction and ensure that callbacks are only invoked when iterating that context. Also, NMClient itself shall never iterate the caller's context. This also means, libnm must never use g_idle_add() or g_timeout_add(), as those enqueue sources in the g_main_context_default() context. - Get ordering of messages right. All events are consistently enqueued in a GMainContext and processed strictly in order. For example, previously "nm-object.c" tried to combine signals and emit them on an idle handler. That is wrong, signals must be emitted in the right order and when they happen. Note that when using GInitable's synchronous initialization to initialize the NMClient instance, NMClient internally still operates fully asynchronously. In that case NMClient has an internal main context. - NMClient takes over most of the functionality. When using D-Bus' ObjectManager interface, one needs to handle basically the entire state of the D-Bus interface. That cannot be separated well into distinct parts, and even if you try, you just end up having closely related code in different source files. Spreading related code does not make it easier to understand, on the contrary. That means, NMClient is inherently complex as it contains most of the logic. I think that is not avoidable, but it's not as bad as it sounds. - NMClient processes D-Bus messages and state changes in separate steps. First NMClient unpacks the message (e.g. _dbus_handle_properties_changed()) and keeps track of the changed data. Then we update the GObject instances (_dbus_handle_obj_changed_dbus()) without emitting any signals yet. Finally, we emit all signals and notifications that were collected (_dbus_handle_changes_commit()). Note that for example during the initial GetManagedObjects() reply, NMClient receive a large amount of state at once. But we first apply all the changes to our GObject instances before emitting any signals. The result is that signals are always emitted in a moment when the cache is consistent. The unavoidable downside is that when you receive a property changed signal, possibly many other properties changed already and more signals are about to be emitted. - NMDeviceWifi no longer modifies the content of the cache from client side during poke_wireless_devices_with_rf_status(). The content of the cache should be determined by D-Bus alone and follow what NetworkManager service exposes. Local modifications should be avoided. - This aims to bring no API/ABI change, though it does of course bring various subtle changes in behavior. Those should be all for the better, but the goal is not to break any existing clients. This does change internal (albeit externally visible) API, like dropping NM_OBJECT_DBUS_OBJECT_MANAGER property and NMObject no longer implementing GInitableIface and GAsyncInitableIface. - Some uses of gdbus-codegen classes remain in NMVpnPluginOld, NMVpnServicePlugin and NMSecretAgentOld. These are independent of NMClient/NMObject and should be reworked separately. - While we no longer use generated classes from gdbus-codegen, we don't need more glue code than before. Also before we constructed NMPropertiesInfo and a had large amount of code to propagate properties from NMDBus* to NMObject. That got completely reworked, but did not fundamentally change. You still need about the same effort to create the NMLDBusMetaIface. Not using generated bindings did not make anything worse (which tells about the usefulness of generated code, at least in the way it was used). - NMLDBusMetaIface and other meta data is static and immutable. This avoids copying them around. Also, macros like NML_DBUS_META_PROPERTY_INIT_U() have compile time checks to ensure the property types matches. It's pretty hard to misuse them because it won't compile. - The meta data now explicitly encodes the expected D-Bus types and makes sure never to accept wrong data. That would only matter when the server (accidentally or intentionally) exposes unexpected types on D-Bus. I don't think that was previously ensured in all cases. For example, demarshal_generic() only cared about the GObject property type, it didn't know the expected D-Bus type. - Previously GDBusObjectManager would sometimes emit warnings (g_log()). Those probably indicated real bugs. In any case, it prevented us from running CI with G_DEBUG=fatal-warnings, because there would be just too many unrelated crashes. Now we log debug messages that can be enabled with "LIBNM_CLIENT_DEBUG=trace". Some of these messages can also be turned into g_warning()/g_critical() by setting LIBNM_CLIENT_DEBUG=warning,error. Together with G_DEBUG=fatal-warnings, this turns them into assertions. Note that such "assertion failures" might also happen because of a server bug (or change). Thus these are not common assertions that indicate a bug in libnm and are thus not armed unless explicitly requested. In our CI we should now always run with LIBNM_CLIENT_DEBUG=warning,error and G_DEBUG=fatal-warnings and to catch bugs. Note that currently NetworkManager has bugs in this regard, so enabling this will result in assertion failures. That should be fixed first. - Note that this changes the order in which we emit "notify:devices" and "device-added" signals. I think it makes the most sense to emit first "device-removed", then "notify:devices", and finally "device-added" signals. This changes behavior for commit 52ae28f6e5bf ('libnm: queue added/removed signals and suppress uninitialized notifications'), but I don't think that users should actually rely on the order. Still, the new order makes the most sense to me. - In NetworkManager, profiles can be invisible to the user by setting "connection.permissions". Such profiles would be hidden by NMClient's nm_client_get_connections() and their "connection-added"/"connection-removed" signals. Note that NMActiveConnection's nm_active_connection_get_connection() and NMDevice's nm_device_get_available_connections() still exposes such hidden NMRemoteConnection instances. This behavior was preserved. NUMBERS ------- I compared 3 versions of libnm. [1] 962297f9085d, current tip of nm-1-20 branch [2] 4fad8c7c642e, current master, immediate parent of this patch [3] this patch All tests were done on Fedora 31, x86_64, gcc 9.2.1-1.fc31. The libraries were build with $ ./contrib/fedora/rpm/build_clean.sh -g -w test -W debug Note that RPM build already stripped the library. --- N1) File size of libnm.so.0.1.0 in bytes. There currently seems to be a issue on Fedora 31 generating wrong ELF notes. Usually, libnm is smaller but in these tests it had large (and bogus) ELF notes. Anyway, the point is to show the relative sizes, so it doesn't matter). [1] 4075552 (102.7%) [2] 3969624 (100.0%) [3] 3705208 ( 93.3%) --- N2) `size /usr/lib64/libnm.so.0.1.0`: text data bss dec hex filename [1] 1314569 (102.0%) 69980 ( 94.8%) 10632 ( 80.4%) 1395181 (101.4%) 1549ed /usr/lib64/libnm.so.0.1.0 [2] 1288410 (100.0%) 73796 (100.0%) 13224 (100.0%) 1375430 (100.0%) 14fcc6 /usr/lib64/libnm.so.0.1.0 [3] 1229066 ( 95.4%) 65248 ( 88.4%) 13400 (101.3%) 1307714 ( 95.1%) 13f442 /usr/lib64/libnm.so.0.1.0 --- N3) Performance test with test-client.py. With checkout of [2], run ``` prepare_checkout() { rm -rf /tmp/nm-test && \ git checkout -B test 4fad8c7c642e && \ git clean -fdx && \ ./autogen.sh --prefix=/tmp/nm-test && \ make -j 5 install && \ make -j 5 check-local-clients-tests-test-client } prepare_test() { NM_TEST_REGENERATE=1 NM_TEST_CLIENT_BUILDDIR="/data/src/NetworkManager" NM_TEST_CLIENT_NMCLI_PATH=/usr/bin/nmcli python3 ./clients/tests/test-client.py -v } do_test() { for i in {1..10}; do NM_TEST_CLIENT_BUILDDIR="/data/src/NetworkManager" NM_TEST_CLIENT_NMCLI_PATH=/usr/bin/nmcli python3 ./clients/tests/test-client.py -v || return -1 done echo "done!" } prepare_checkout prepare_test time do_test ``` [1] real 2m14.497s (101.3%) user 5m26.651s (100.3%) sys 1m40.453s (101.4%) [2] real 2m12.800s (100.0%) user 5m25.619s (100.0%) sys 1m39.065s (100.0%) [3] real 1m54.915s ( 86.5%) user 4m18.585s ( 79.4%) sys 1m32.066s ( 92.9%) --- N4) Performance. Run NetworkManager from build [2] and setup a large number of profiles (551 profiles and 515 devices, mostly unrealized). This setup is already at the edge of what NetworkManager currently can handle. Of course, that is a different issue. Here we just check how long plain `nmcli` takes on the system. ``` do_cleanup() { for UUID in $(nmcli -g NAME,UUID connection show | sed -n 's/^xx-c-.*:\([^:]\+\)$/\1/p'); do nmcli connection delete uuid "$UUID" done for DEVICE in $(nmcli -g DEVICE device status | grep '^xx-i-'); do nmcli device delete "$DEVICE" done } do_setup() { do_cleanup for i in {1..30}; do nmcli connection add type bond autoconnect no con-name xx-c-bond-$i ifname xx-i-bond-$i ipv4.method disabled ipv6.method ignore for j in $(seq $i 30); do nmcli connection add type vlan autoconnect no con-name xx-c-vlan-$i-$j vlan.id $j ifname xx-i-vlan-$i-$j vlan.parent xx-i-bond-$i ipv4.method disabled ipv6.method ignore done done systemctl restart NetworkManager.service sleep 5 } do_test() { perf stat -r 50 -B nmcli 1>/dev/null } do_test ``` [1] Performance counter stats for 'nmcli' (50 runs): 456.33 msec task-clock:u # 1.093 CPUs utilized ( +- 0.44% ) 0 context-switches:u # 0.000 K/sec 0 cpu-migrations:u # 0.000 K/sec 5,900 page-faults:u # 0.013 M/sec ( +- 0.02% ) 1,408,675,453 cycles:u # 3.087 GHz ( +- 0.48% ) 1,594,741,060 instructions:u # 1.13 insn per cycle ( +- 0.02% ) 368,744,018 branches:u # 808.061 M/sec ( +- 0.02% ) 4,566,058 branch-misses:u # 1.24% of all branches ( +- 0.76% ) 0.41761 +- 0.00282 seconds time elapsed ( +- 0.68% ) [2] Performance counter stats for 'nmcli' (50 runs): 477.99 msec task-clock:u # 1.088 CPUs utilized ( +- 0.36% ) 0 context-switches:u # 0.000 K/sec 0 cpu-migrations:u # 0.000 K/sec 5,948 page-faults:u # 0.012 M/sec ( +- 0.03% ) 1,471,133,482 cycles:u # 3.078 GHz ( +- 0.36% ) 1,655,275,369 instructions:u # 1.13 insn per cycle ( +- 0.02% ) 382,595,152 branches:u # 800.433 M/sec ( +- 0.02% ) 4,746,070 branch-misses:u # 1.24% of all branches ( +- 0.49% ) 0.43923 +- 0.00242 seconds time elapsed ( +- 0.55% ) [3] Performance counter stats for 'nmcli' (50 runs): 352.36 msec task-clock:u # 1.027 CPUs utilized ( +- 0.32% ) 0 context-switches:u # 0.000 K/sec 0 cpu-migrations:u # 0.000 K/sec 4,790 page-faults:u # 0.014 M/sec ( +- 0.26% ) 1,092,341,186 cycles:u # 3.100 GHz ( +- 0.26% ) 1,209,045,283 instructions:u # 1.11 insn per cycle ( +- 0.02% ) 281,708,462 branches:u # 799.499 M/sec ( +- 0.01% ) 3,101,031 branch-misses:u # 1.10% of all branches ( +- 0.61% ) 0.34296 +- 0.00120 seconds time elapsed ( +- 0.35% ) --- N5) same setup as N4), but run `PAGER= /bin/time -v nmcli`: [1] Command being timed: "nmcli" User time (seconds): 0.42 System time (seconds): 0.04 Percent of CPU this job got: 107% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.43 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 34456 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 6128 Voluntary context switches: 1298 Involuntary context switches: 1106 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 [2] Command being timed: "nmcli" User time (seconds): 0.44 System time (seconds): 0.04 Percent of CPU this job got: 108% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.44 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 34452 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 6169 Voluntary context switches: 1849 Involuntary context switches: 142 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 [3] Command being timed: "nmcli" User time (seconds): 0.32 System time (seconds): 0.02 Percent of CPU this job got: 102% Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.34 Average shared text size (kbytes): 0 Average unshared data size (kbytes): 0 Average stack size (kbytes): 0 Average total size (kbytes): 0 Maximum resident set size (kbytes): 29196 Average resident set size (kbytes): 0 Major (requiring I/O) page faults: 0 Minor (reclaiming a frame) page faults: 5059 Voluntary context switches: 919 Involuntary context switches: 685 Swaps: 0 File system inputs: 0 File system outputs: 0 Socket messages sent: 0 Socket messages received: 0 Signals delivered: 0 Page size (bytes): 4096 Exit status: 0 --- N6) same setup as N4), but run `nmcli monitor` and look at `ps aux` for the RSS size. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND [1] me 1492900 21.0 0.2 461348 33248 pts/10 Sl+ 15:02 0:00 nmcli monitor [2] me 1490721 5.0 0.2 461496 33548 pts/10 Sl+ 15:00 0:00 nmcli monitor [3] me 1495801 16.5 0.1 459476 28692 pts/10 Sl+ 15:04 0:00 nmcli monitor
2019-10-30 11:42:58 +01:00
nm_client_get_metered;
libnm: add nm_client_reload() Introduce libnm API to reload NM configuration through the Reload() D-Bus method.
2019-09-05 15:19:33 +02:00
nm_client_reload;
nm_client_reload_finish;
libnm: export interface flags Add libnm support for the new InterfaceFlags property of NMDevice.
2019-10-10 10:04:06 +02:00
nm_device_get_interface_flags;
core: export interface flags of devices Add a new read-only "InterfaceFlags" property to the Device interface to export via D-Bus kernel flags and possibly other NM specific flags. At the moment IFF_UP and IFF_LOWERUP are implemented.
2019-10-10 09:23:22 +02:00
nm_device_interface_flags_get_type;
libnm: add ipvx.dhcp-hostname-flags properties When using the dhclient DHCP backend users can tweak the behavior in the dhclient configuration file. One of the options that was reported as useful in the past was the FQDN flags [1] [2]. Add native support for FQDN flags to NM by introducing new ipv{4,6}.dhcp-hostname-flags properties. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1684595 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1255507
2019-07-09 11:26:02 +02:00
nm_dhcp_hostname_flags_get_type;
libnm: add nm_ip_address_cmp_full() function Not being able to compare two NMIPAddress instances is a major limitation. Add nm_ip_address_cmp_full(). The choice here for adding a "cmp()" function instead of a "equals()" function is that cmp is more useful. We only want to add one of the two, so choose the more powerful one. Yes, usually its also not the variant we want or the variant that is convenient to use, such is life. Compare this to: - nm_ip_route_equal_full(), which is an equal() method and not a cmp(). - nm_ip_route_equal_full() which has a guint flags argument, instead of a typedef for an enum, with a proper generated GType.
2019-11-26 11:24:40 +01:00
nm_ip_address_cmp_flags_get_type;
nm_ip_address_cmp_full;
libnm: export reload flags Flags to the manager Reload() method are stable API but not exposed in a public header. Export them.
2019-09-05 14:54:22 +02:00
nm_manager_reload_flags_get_type;
setting-gsm: add auto-config property This will make NetworkManager look up APN, username, and password in the Mobile Broadband Provider database. It is mutually exclusive with the apn, username and password properties. If that is the case, the connection will be normalized to auto-config=false. This makes it convenient for the user to turn off the automatism by just setting the apn.
2019-09-09 20:22:19 +02:00
nm_setting_gsm_get_auto_config;
libnm: add ipvx.dhcp-hostname-flags properties When using the dhclient DHCP backend users can tweak the behavior in the dhclient configuration file. One of the options that was reported as useful in the past was the FQDN flags [1] [2]. Add native support for FQDN flags to NM by introducing new ipv{4,6}.dhcp-hostname-flags properties. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1684595 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1255507
2019-07-09 11:26:02 +02:00
nm_setting_ip_config_get_dhcp_hostname_flags;
setting-gsm: add auto-config property This will make NetworkManager look up APN, username, and password in the Mobile Broadband Provider database. It is mutually exclusive with the apn, username and password properties. If that is the case, the connection will be normalized to auto-config=false. This makes it convenient for the user to turn off the automatism by just setting the apn.
2019-09-09 20:22:19 +02:00
} libnm_1_20_0;
libnm: add NMClient:instance-flags property Add a flags property to control behavior of NMClient. Possible future use cases: - currently it would always automatically fetch permissions. Often that is not used and the user could opt out of it. - currently, using sync init creates an internal GMainContext. This has an overhead and may be undesirable. We could implement another "sync" initialization that would merely iterate the callers mainloop until the initialization completes. A flag would allow to opt in. - currently, NMClient always fetches all connection settings automatically. Via a flag the user could opt out of that. Instead NMClient could provide an API so the user can request settings as they are needed.
2019-12-05 18:17:43 +01:00
libnm: move nm_client_get_capabilities() to separate linker version nm_client_get_capabilities() was backported to 1.22.2. Add to to the appropriate linker version. Officially (and according to docs) nm_client_get_capabilities() still appears first in libnm 1.24.0. However, as it got backported to 1.22.2, it needs to be part of a different symbol version on 1.22. Instead of adding the symbol twice (once for libnm_1_24_0 and libnm_1_22_2), move it only to the libnm_1_22_2 symbol version, also on master.
2019-12-24 14:43:47 +01:00
libnm_1_22_2 {
libnm: add NMClient:instance-flags property Add a flags property to control behavior of NMClient. Possible future use cases: - currently it would always automatically fetch permissions. Often that is not used and the user could opt out of it. - currently, using sync init creates an internal GMainContext. This has an overhead and may be undesirable. We could implement another "sync" initialization that would merely iterate the callers mainloop until the initialization completes. A flag would allow to opt in. - currently, NMClient always fetches all connection settings automatically. Via a flag the user could opt out of that. Instead NMClient could provide an API so the user can request settings as they are needed.
2019-12-05 18:17:43 +01:00
global:
libnm: add nm_client_get_capabilities() to expose server Capabilities I hesitated to add this to libnm, because it's hardly used. However, we already fetch the property during GetManagedObjects(), we we should make it accessible, instead of requiring the user to make another D-Bus call.
2019-12-20 18:10:55 +01:00
nm_client_get_capabilities;
libnm: move nm_client_get_capabilities() to separate linker version nm_client_get_capabilities() was backported to 1.22.2. Add to to the appropriate linker version. Officially (and according to docs) nm_client_get_capabilities() still appears first in libnm 1.24.0. However, as it got backported to 1.22.2, it needs to be part of a different symbol version on 1.22. Instead of adding the symbol twice (once for libnm_1_24_0 and libnm_1_22_2), move it only to the libnm_1_22_2 symbol version, also on master.
2019-12-24 14:43:47 +01:00
} libnm_1_22_0;
libnm: move nm_setting_ip6_config_get_ra_timeout() to "libnm_1_22_8" symbol version nm_setting_ip6_config_get_ra_timeout() was backported to nm-1-22 branch, and will be released as 1.22.8. As such, on the stable branch the symbol will be placed in a separate symbol version ("libnm_1_22_8"). To support the upgrade path from 1.22.8+ to 1.23+, we want this symbol also present on master. At that point, we don't need to duplicate the symbol. Just add the same linker symbol version also to master.
2020-02-17 15:16:23 +01:00
libnm_1_22_8 {
global:
nm_setting_ip6_config_get_ra_timeout;
} libnm_1_22_2;
libnm: move nm_client_get_capabilities() to separate linker version nm_client_get_capabilities() was backported to 1.22.2. Add to to the appropriate linker version. Officially (and according to docs) nm_client_get_capabilities() still appears first in libnm 1.24.0. However, as it got backported to 1.22.2, it needs to be part of a different symbol version on 1.22. Instead of adding the symbol twice (once for libnm_1_24_0 and libnm_1_22_2), move it only to the libnm_1_22_2 symbol version, also on master.
2019-12-24 14:43:47 +01:00
libnm_1_24_0 {
global:
libnm: add nm_client_dbus_call() API Add an API for calling D-Bus methods arbitrary objects of NetworkManager's API. Of course, this is basically just a call to g_dbus_connection_call(), using the current name owner, nm_client_get_dbus_connection() and nm_client_get_main_context(). All of this could also be achieved without this new API. However, nm_client_dbus_call() also gracefully handles if the current name owner is %NULL. It's a valid concern whether such API is useful, as the users already have all pieces to do it themself. I think it is.
2020-03-13 17:30:23 +01:00
nm_client_dbus_call;
nm_client_dbus_call_finish;
libnm: add nm_client_dbus_set_property() API Similar to nm_client_dbus_call(), but useful for setting a D-Bus property on NetworkManager's D-Bus interface. Note that we currently have various synchronous API for setting D-Bus properties (like nm_client_networking_set_enabled()). Synchronous API does not play well with the content of NMClient's cache, and was thus deprecated. However, until now no async variant exists. Instead of adding multiple async operations, I think it should be sufficient to only add one nm_client_dbus_set_property() property. It's still reasonably convenient to use for setting a property.
2020-03-13 18:11:56 +01:00
nm_client_dbus_set_property;
nm_client_dbus_set_property_finish;
libnm: add NMClient:instance-flags property Add a flags property to control behavior of NMClient. Possible future use cases: - currently it would always automatically fetch permissions. Often that is not used and the user could opt out of it. - currently, using sync init creates an internal GMainContext. This has an overhead and may be undesirable. We could implement another "sync" initialization that would merely iterate the callers mainloop until the initialization completes. A flag would allow to opt in. - currently, NMClient always fetches all connection settings automatically. Via a flag the user could opt out of that. Instead NMClient could provide an API so the user can request settings as they are needed.
2019-12-05 18:17:43 +01:00
nm_client_get_instance_flags;
client: add nm_client_get_object_by_path() and nm_object_get_client() API When iterating the GMainContext of the NMClient instance, D-Bus events get processed. That means, every time you iterate the context (or "return to the main loop"), the content of the cache might change completely. It makes sense to keep a reference to an NMObject instance, do something, and afterwards check whether the instance can still be found in the cache. Add an API for that. nm_object_get_client() allows to know whether the object is still cached. Likewise, while NMClient abstracts D-Bus, it should still provide a way to look up an NMObject by D-Bus path. Add nm_client_get_object_by_path() for that. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/384
2020-01-04 07:58:58 +01:00
nm_client_get_object_by_path;
libnm: allow to enable/disable fetching of permissions in NMClient Currently, NMClient by default always fetches the permissions ("GetPermissions()") and refreshes them on "CheckPermissions" signal. Fetching permissions is relatively expensive, while they are not used most of the time. Allow the user to opt out of this. For that, have a NMClientInstanceFlags to enable/disable automatic fetching. Also add a "permissions-state" property that allows the user to understand whether the cached permissions are up to date or not. This is a bit an awkward API for handling this. E.g. you cannot explicitly request permissions, you can just enable/disable fetching permissions. And then you can watch the permission-state to know whether you are ready. It's done this way because it fits the previous model and extends the API with a (relative) small amount of new functions and properties.
2019-12-05 15:53:51 +01:00
nm_client_get_permissions_state;
libnm: add NMClient:instance-flags property Add a flags property to control behavior of NMClient. Possible future use cases: - currently it would always automatically fetch permissions. Often that is not used and the user could opt out of it. - currently, using sync init creates an internal GMainContext. This has an overhead and may be undesirable. We could implement another "sync" initialization that would merely iterate the callers mainloop until the initialization completes. A flag would allow to opt in. - currently, NMClient always fetches all connection settings automatically. Via a flag the user could opt out of that. Instead NMClient could provide an API so the user can request settings as they are needed.
2019-12-05 18:17:43 +01:00
nm_client_instance_flags_get_type;
core,libnm: add VRF support Add VRF support to the daemon. When the device we are activating is a VRF or a VRF's slave, put routes in the table specified by the VRF connection. Also, introduce a VRF device type in libnm.
2019-12-05 10:36:54 +01:00
nm_device_vrf_get_table;
nm_device_vrf_get_type;
client: add nm_client_get_object_by_path() and nm_object_get_client() API When iterating the GMainContext of the NMClient instance, D-Bus events get processed. That means, every time you iterate the context (or "return to the main loop"), the content of the cache might change completely. It makes sense to keep a reference to an NMObject instance, do something, and afterwards check whether the instance can still be found in the cache. Add an API for that. nm_object_get_client() allows to know whether the object is still cached. Likewise, while NMClient abstracts D-Bus, it should still provide a way to look up an NMObject by D-Bus path. Add nm_client_get_object_by_path() for that. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/384
2020-01-04 07:58:58 +01:00
nm_object_get_client;
libnm/secret-agent: rework NMSecretAgentOld Note that the name "NMSecretAgentOld" comes from when libnm was forked from libnm-glib. There was a plan to rework the secret agent API and replace it by a better one. That didn't happen (yet), instead our one and only agent implementation is still lacking. Don't add a new API, instead try to improve the existing one, without breaking existing users. Just get over the fact that the name "NMSecretAgentOld" is ugly. Also note how nm-applet uses NMSecretAgentOld. It subtypes a class AppletAgent. The constructor applet_agent_new() is calling the synchronous g_initable_init() initialization with auto-register enabled. As it was, g_initable_init() would call nm_secret_agent_old_register(), and if the "Register" call failed, initialization failed for good. There are even unit tests that test this behavior. This is bad behavior. It means, when you start nm-applet without NetworkManager running, it will fail to create the AppletAgent instance. It would hence be the responsibility of the applet to recover from this situation (e.g. by retrying after timeout or watching the D-Bus name owner). Of course, nm-applet doesn't do that and won't recover from such a failure. NMSecretAgentOld must try hard not to fail and recover automatically. The user of the API is not interested in implementing the registration, unregistration and retry handling. Instead, it should just work best effort and transparently to the user of the API. Differences: - no longer use gdbus-codegen generate bindings. Use GDBusConnection directly instead. These generated proxies complicate the code by introducing an additional, stateful layer. - properly handle GMainContext and synchronous initialization by using an internal GMainContext. With this NMSecretAgentOld can be used in a multi threaded context with separate GMainContext. This does not mean that the object itself became thread safe, but that the GMainContext gives the means to coordinate multi-threaded access. - there are no more blocking calls except g_initiable_init() which iterates an internal GMainContext until initialization completes. - obtaining the Unix user ID with "GetConnectionUnixUser" to authenticate the server is now done asynchronously and only once per name-owner. - NMSecretAgentOld will now register/export the Agent D-Bus object already during initialization and stay registered as long as the instance is alive. This is because usually registering a D-Bus object would not fail, unless the D-Bus path is already taken. Such an error would mean that another agent is registered for the same GDBusConnection, that likely would be a bug in the caller. Hence, such an issue is truly non-recoverable and should be reported early to the user. There is a change in behavior compared to before, where previously the D-Bus object would only be registered while the instance is enabled. This makes a difference if the user intended to keep the NMSecretAgentOld instance around in an unregistered state. Note that nm_secret_agent_old_destroy() was added to really unregister the D-Bus object. A destroyed instance can no longer be registered. - the API no longer fully exposes the current registration state. The user either enables or disables the agent. Then, in the background NMSecretAgentOld will register, and serve requests as they come. It will also always automatically re-register and it can de-facto no longer fail. That is, there might be a failure to register, or the NetworkManager peer might not be authenticated (non-root) or there might be some other error, or NetworkManager might not be running. But such errors are not exposed to the user. The instance is just not able to provide the secrets in those cases, but it may recover if the problem can be resolved. - In particular, it makes no sense that nm_secret_agent_old_register*() fails, returns an error, or waits until registration is complete. This API is now only to enable/disable the agent. It is idempotent and won't fail (there is a catch, see next point). In particular, nm_secret_agent_old_unregister*() cannot fail anymore. - However, with the previous point there is a problem/race. When you create a NMSecretAgentOld instance and immediately afterwards activate a profile, then you want to be sure that the registration is complete first. Otherwise, NetworkManager might fail the activation because no secret agent registered yet. A partial solution for this is that g_initiable_init()/g_async_initable_init_async() will block until registration is complete (or with or without success). That means, if NetworkManager is running, initializing the NMSecretAgentOld will wait until registration is complete (or failed). However, that does not solve the race if NetworkManager was not running when creating the instance. To solve that race, the user may call nm_secret_agent_old_register_async() and wait for the command to finish before starting activating. While async registration no longer fails (in the sense of leaving the agent permanently disconnected), it will try to ensure that we are successfully registered and ready to serve requests. By using this API correctly, a race can be avoided and the user can know that the instance is now ready to serve request.
2019-12-24 13:26:50 +01:00
nm_secret_agent_old_destroy;
nm_secret_agent_old_enable;
nm_secret_agent_old_get_context_busy_watcher;
libnm/secret-agent: add dbus-connection and main-context properties to NMSecretAgentOld The NMSecretAgentOld is build very much around a GDBusConnection, and GDBusConnection is build around GMainContext. That means, a NMSecretAgentOld instance is strongly related to these two. That is because NMSecretAgentOld will register to signals on D-Bus, using GDBusConnection. Hence, that GDBusConnection instance and the calling GMainContext becomes central to the NMSecretAgentOld instance. Also, the GMainContext is the way to synchronize access to the NMSecretAgentOld. Used properly, this allows using the API in multi threaded context. Expose these two in the public API. Since NMSecretAgentOld is part of libnm and supposed to provide a flexible API, this is just useful to have. Also, allow to provide a GDBusConnection as construct-only property. This way, the instance can be used independent of g_bus_get() and the user has full control. There is no setter for the GMainContext, because it just takes the g_main_context_get_thread_default() instance at the time of construction.
2019-12-17 13:19:49 +01:00
nm_secret_agent_old_get_dbus_connection;
libnm/secret-agent: rework NMSecretAgentOld Note that the name "NMSecretAgentOld" comes from when libnm was forked from libnm-glib. There was a plan to rework the secret agent API and replace it by a better one. That didn't happen (yet), instead our one and only agent implementation is still lacking. Don't add a new API, instead try to improve the existing one, without breaking existing users. Just get over the fact that the name "NMSecretAgentOld" is ugly. Also note how nm-applet uses NMSecretAgentOld. It subtypes a class AppletAgent. The constructor applet_agent_new() is calling the synchronous g_initable_init() initialization with auto-register enabled. As it was, g_initable_init() would call nm_secret_agent_old_register(), and if the "Register" call failed, initialization failed for good. There are even unit tests that test this behavior. This is bad behavior. It means, when you start nm-applet without NetworkManager running, it will fail to create the AppletAgent instance. It would hence be the responsibility of the applet to recover from this situation (e.g. by retrying after timeout or watching the D-Bus name owner). Of course, nm-applet doesn't do that and won't recover from such a failure. NMSecretAgentOld must try hard not to fail and recover automatically. The user of the API is not interested in implementing the registration, unregistration and retry handling. Instead, it should just work best effort and transparently to the user of the API. Differences: - no longer use gdbus-codegen generate bindings. Use GDBusConnection directly instead. These generated proxies complicate the code by introducing an additional, stateful layer. - properly handle GMainContext and synchronous initialization by using an internal GMainContext. With this NMSecretAgentOld can be used in a multi threaded context with separate GMainContext. This does not mean that the object itself became thread safe, but that the GMainContext gives the means to coordinate multi-threaded access. - there are no more blocking calls except g_initiable_init() which iterates an internal GMainContext until initialization completes. - obtaining the Unix user ID with "GetConnectionUnixUser" to authenticate the server is now done asynchronously and only once per name-owner. - NMSecretAgentOld will now register/export the Agent D-Bus object already during initialization and stay registered as long as the instance is alive. This is because usually registering a D-Bus object would not fail, unless the D-Bus path is already taken. Such an error would mean that another agent is registered for the same GDBusConnection, that likely would be a bug in the caller. Hence, such an issue is truly non-recoverable and should be reported early to the user. There is a change in behavior compared to before, where previously the D-Bus object would only be registered while the instance is enabled. This makes a difference if the user intended to keep the NMSecretAgentOld instance around in an unregistered state. Note that nm_secret_agent_old_destroy() was added to really unregister the D-Bus object. A destroyed instance can no longer be registered. - the API no longer fully exposes the current registration state. The user either enables or disables the agent. Then, in the background NMSecretAgentOld will register, and serve requests as they come. It will also always automatically re-register and it can de-facto no longer fail. That is, there might be a failure to register, or the NetworkManager peer might not be authenticated (non-root) or there might be some other error, or NetworkManager might not be running. But such errors are not exposed to the user. The instance is just not able to provide the secrets in those cases, but it may recover if the problem can be resolved. - In particular, it makes no sense that nm_secret_agent_old_register*() fails, returns an error, or waits until registration is complete. This API is now only to enable/disable the agent. It is idempotent and won't fail (there is a catch, see next point). In particular, nm_secret_agent_old_unregister*() cannot fail anymore. - However, with the previous point there is a problem/race. When you create a NMSecretAgentOld instance and immediately afterwards activate a profile, then you want to be sure that the registration is complete first. Otherwise, NetworkManager might fail the activation because no secret agent registered yet. A partial solution for this is that g_initiable_init()/g_async_initable_init_async() will block until registration is complete (or with or without success). That means, if NetworkManager is running, initializing the NMSecretAgentOld will wait until registration is complete (or failed). However, that does not solve the race if NetworkManager was not running when creating the instance. To solve that race, the user may call nm_secret_agent_old_register_async() and wait for the command to finish before starting activating. While async registration no longer fails (in the sense of leaving the agent permanently disconnected), it will try to ensure that we are successfully registered and ready to serve requests. By using this API correctly, a race can be avoided and the user can know that the instance is now ready to serve request.
2019-12-24 13:26:50 +01:00
nm_secret_agent_old_get_dbus_name_owner;
libnm/secret-agent: add dbus-connection and main-context properties to NMSecretAgentOld The NMSecretAgentOld is build very much around a GDBusConnection, and GDBusConnection is build around GMainContext. That means, a NMSecretAgentOld instance is strongly related to these two. That is because NMSecretAgentOld will register to signals on D-Bus, using GDBusConnection. Hence, that GDBusConnection instance and the calling GMainContext becomes central to the NMSecretAgentOld instance. Also, the GMainContext is the way to synchronize access to the NMSecretAgentOld. Used properly, this allows using the API in multi threaded context. Expose these two in the public API. Since NMSecretAgentOld is part of libnm and supposed to provide a flexible API, this is just useful to have. Also, allow to provide a GDBusConnection as construct-only property. This way, the instance can be used independent of g_bus_get() and the user has full control. There is no setter for the GMainContext, because it just takes the g_main_context_get_thread_default() instance at the time of construction.
2019-12-17 13:19:49 +01:00
nm_secret_agent_old_get_main_context;
Add domain_match mode for wifi certificate domain comparison https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/308 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/437
2020-03-23 18:22:21 +01:00
nm_setting_802_1x_get_domain_match;
nm_setting_802_1x_get_phase2_domain_match;
nm-setting-bond: add API to libnm to get the normalized bond option value Add 'nm_setting_bond_get_option_normalized()', the purpose of this API is to retrieve a bond option normalized value which is the option that NetworkManager will actually apply to the bond when activating the connection, this takes into account default values for some options that NM assumes. For example, if you create a connection: $ nmcli c add type bond con-name nm-bond ifname bond0 bond.options mode=0 Calling 'nm_setting_bond_get_option_normalized(s_bond, "miimon")' would return "100" as even if not specified NetworkManager enables miimon for bond connections. Another example: $ nmcli c add type bond con-name nm-bond ifname bond0 bond.options mode=0,arp_interval=100 Calling 'nm_setting_bond_get_option_normalized(s_bond, "miimon")' would return NULL in this case because NetworkManager disables miimon if 'arp_interval' is set explicitly but 'miimon' is not.
2020-03-03 11:36:16 +01:00
nm_setting_bond_get_option_normalized;
nm-setting-bridge: add 'group-address' bridge option Also add related unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-23 19:29:24 +01:00
nm_setting_bridge_get_group_address;
nm-setting-bridge: add 'multicast-querier' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-30 13:50:35 +02:00
nm_setting_bridge_get_multicast_querier;
nm-setting-bridge: add 'multicast-query-use-ifaddr' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-27 17:18:06 +01:00
nm_setting_bridge_get_multicast_query_use_ifaddr;
nm-setting-bridge: add 'multicast-router' bridge option Also add related unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-26 18:38:04 +01:00
nm_setting_bridge_get_multicast_router;
nm-setting-bridge: add 'vlan-protocol' bridge option Also add related unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-26 12:02:20 +01:00
nm_setting_bridge_get_vlan_protocol;
nm-setting-bridge: add 'vlan-stats-enabled' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-03-26 16:23:50 +01:00
nm_setting_bridge_get_vlan_stats_enabled;
libnm-core,cli: add VRF setting Add new VRF setting and connection types to libnm-core and support them in nmcli.
2019-12-05 10:13:34 +01:00
nm_setting_vrf_get_table;
nm_setting_vrf_get_type;
nm_setting_vrf_new;
libnm: move nm_setting_ip6_config_get_ra_timeout() to "libnm_1_22_8" symbol version nm_setting_ip6_config_get_ra_timeout() was backported to nm-1-22 branch, and will be released as 1.22.8. As such, on the stable branch the symbol will be placed in a separate symbol version ("libnm_1_22_8"). To support the upgrade path from 1.22.8+ to 1.23+, we want this symbol also present on master. At that point, we don't need to duplicate the symbol. Just add the same linker symbol version also to master.
2020-02-17 15:16:23 +01:00
} libnm_1_22_8;
libnm: fix symbol versioning for nm_setting_connection_get_mud_url()
2020-04-24 09:17:59 +02:00
libnm_1_26_0 {
global:
ethtool: add coalesce settings This is the initial support for coalesce settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-07 16:58:32 +02:00
nm_ethtool_optname_is_coalesce;
ethtool: add ring settings This is the initial support for ring settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-12 17:27:45 +02:00
nm_ethtool_optname_is_ring;
nm-setting-bridge: add 'multicast-hash-max' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-10 15:03:39 +02:00
nm_setting_bridge_get_multicast_hash_max;
nm-setting-bridge: add 'multicast-last-member-count' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_last_member_count;
nm-setting-bridge: add 'multicast-last-member-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_last_member_interval;
nm-setting-bridge: add 'multicast-membership-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_membership_interval;
nm-setting-bridge: add 'multicast-querier-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_querier_interval;
nm-setting-bridge: add 'multicast-query-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_query_interval;
nm-setting-bridge: add 'multicast-query-response-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_query_response_interval;
nm-setting-bridge: add 'multicast-startup-query-count' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_startup_query_count;
nm-setting-bridge: add 'multicast-startup-query-interval' bridge option https://bugzilla.redhat.com/show_bug.cgi?id=1755768
2020-04-21 17:35:51 +02:00
nm_setting_bridge_get_multicast_startup_query_interval;
libnm: fix symbol versioning for nm_setting_connection_get_mud_url()
2020-04-24 09:17:59 +02:00
nm_setting_connection_get_mud_url;
ethtool: add coalesce settings This is the initial support for coalesce settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-07 16:58:32 +02:00
nm_setting_ethtool_clear_coalesce;
nm_setting_ethtool_clear_coalesce_all;
ethtool: add ring settings This is the initial support for ring settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-12 17:27:45 +02:00
nm_setting_ethtool_clear_ring;
nm_setting_ethtool_clear_ring_all;
ethtool: add coalesce settings This is the initial support for coalesce settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-07 16:58:32 +02:00
nm_setting_ethtool_get_coalesce;
ethtool: add ring settings This is the initial support for ring settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-12 17:27:45 +02:00
nm_setting_ethtool_get_ring;
ethtool: add coalesce settings This is the initial support for coalesce settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-07 16:58:32 +02:00
nm_setting_ethtool_set_coalesce;
ethtool: add ring settings This is the initial support for ring settings and only allows getting/setting, nothing is yet implemented in nm-device. Also add unit test. https://bugzilla.redhat.com/show_bug.cgi?id=1614700
2020-05-12 17:27:45 +02:00
nm_setting_ethtool_set_ring;
settings: add match for driver Add a new "driver" match option to nm-settings. It allows to disable a network connection configuration if a pattern is found or is not found in the device driver name.
2020-04-21 17:39:12 +02:00
nm_setting_match_add_driver;
libnm: sort entires in libnm.ver
2020-05-06 12:16:32 +02:00
nm_setting_match_add_kernel_command_line;
settings: add match for driver Add a new "driver" match option to nm-settings. It allows to disable a network connection configuration if a pattern is found or is not found in the device driver name.
2020-04-21 17:39:12 +02:00
nm_setting_match_clear_drivers;
libnm: sort entires in libnm.ver
2020-05-06 12:16:32 +02:00
nm_setting_match_clear_kernel_command_lines;
settings: add match for driver Add a new "driver" match option to nm-settings. It allows to disable a network connection configuration if a pattern is found or is not found in the device driver name.
2020-04-21 17:39:12 +02:00
nm_setting_match_get_driver;
nm_setting_match_get_drivers;
libnm: sort entires in libnm.ver
2020-05-06 12:16:32 +02:00
nm_setting_match_get_kernel_command_line;
nm_setting_match_get_kernel_command_lines;
settings: add match for driver Add a new "driver" match option to nm-settings. It allows to disable a network connection configuration if a pattern is found or is not found in the device driver name.
2020-04-21 17:39:12 +02:00
nm_setting_match_get_num_drivers;
libnm: sort entires in libnm.ver
2020-05-06 12:16:32 +02:00
nm_setting_match_get_num_kernel_command_lines;
settings: add match for driver Add a new "driver" match option to nm-settings. It allows to disable a network connection configuration if a pattern is found or is not found in the device driver name.
2020-04-21 17:39:12 +02:00
nm_setting_match_remove_driver;
nm_setting_match_remove_driver_by_value;
libnm: sort entires in libnm.ver
2020-05-06 12:16:32 +02:00
nm_setting_match_remove_kernel_command_line;
nm_setting_match_remove_kernel_command_line_by_value;
libnm: add API for setting gendata options to NMSetting (nm_setting_option_get()) NMSettingEthtool is implemented using "gendata", meaning a hash of GVariant. This is different from most other settings that have properties implemented as GObject properties. There are two reasons for this approach: - The setting is transferred via D-Bus as "a{sv}" dictionary. By unpacking the dictionary into GObject properties, the setting cannot handle unknown properties. To be forward compatible (and due to sloppy programming), unknown dictionary keys are silently ignored when parsing a NMSetting. That is error prone and also prevents settings to be treated loss-less. Instead, we should at first accept all values from the dictionary. Only in a second step, nm_connection_verify() rejects invalid settings with an error reason. This way, the user can create a NMSetting, but in a separate step handle if the setting doesn't verify. "gendata" solves this by tracking the full GVariant dictionary. This is still not entirely lossless, because multiple keys are combined. This is for example interesting if an libnm client fetches a connection from a newer NetworkManager version. Now the user can modify the properties that she knows about, while leaving all unknown properties (from newer versions) in place. - the approach aims to reduce the necessary boiler plate to create GObject properties. Adding a new property should require less new code. This approach was always be intended to be suitable for all settings, not only NMSettingEthtool. We should not once again try to add API like nm_setting_ethtool_set_feature(), nm_setting_ethtool_set_coalesce(), etc. Note that the option name already fully encodes whether it is a feature, a coalesce option, or whatever. We should not have "nm_setting_set_$SUB_GROUP (setting, $ONE_NAME_FROM_GROUP)" API, but simply "nm_setting_option_set (setting, $OPTION)" accessors. Also, when parsing a NMSettingEthtool from a GVariant, then a feature option can be any kind of variant. Only nm_setting_verify() rejects variants of the wrong type. As such, nm_setting_option_set*() also doesn't validate whether the variant type matches the option. Of course, if you set a value of wrong type, verify() will reject the setting. Add new general purpose API for this and expose it for NMSetting.
2020-05-14 09:16:32 +02:00
nm_setting_option_get;
libnm: add nm_setting_option_get_names() More general purpose API for generic options of settings.
2020-05-14 09:16:33 +02:00
nm_setting_option_get_all_names;
libnm: add nm_setting_option_set(), nm_setting_option_get_boolean(), nm_setting_option_set_boolean() More general purpose API for generic options of settings.
2020-05-14 09:16:32 +02:00
nm_setting_option_get_boolean;
libnm: add nm_setting_option_get_uint32(), nm_setting_option_set_uint32() More general purpose API for generic options of settings.
2020-05-20 16:31:30 +02:00
nm_setting_option_get_uint32;
libnm: add nm_setting_option_set(), nm_setting_option_get_boolean(), nm_setting_option_set_boolean() More general purpose API for generic options of settings.
2020-05-14 09:16:32 +02:00
nm_setting_option_set;
nm_setting_option_set_boolean;
libnm: add nm_setting_option_get_uint32(), nm_setting_option_set_uint32() More general purpose API for generic options of settings.
2020-05-20 16:31:30 +02:00
nm_setting_option_set_uint32;
libnm: fix symbol versioning for nm_setting_connection_get_mud_url()
2020-04-24 09:17:59 +02:00
} libnm_1_24_0;
Reference in a new issue Copy permalink