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

171 lines
4.8 KiB
Text
Raw Normal View History

Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
{
global:
libnm_glib_get_network_state;
libnm_glib_init;
libnm_glib_register_callback;
libnm_glib_shutdown;
libnm_glib_unregister_callback;
nm_access_point_get_flags;
nm_access_point_get_frequency;
nm_access_point_get_hw_address;
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_access_point_new;
nm_active_connection_get_connection;
nm_active_connection_get_default;
core: add 'default6' property for ActiveConnection objects Since IPv4 and IPv6 have different routing one device can have the active IPv4 connection and a completely different one can have the active IPv6 one.
2010-04-15 15:18:08 -07:00
nm_active_connection_get_default6;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_active_connection_get_devices;
nm_active_connection_get_specific_object;
nm_active_connection_get_state;
nm_active_connection_get_type;
nm_active_connection_new;
nm_cdma_device_get_type;
nm_cdma_device_new;
nm_client_activate_connection;
nm_client_deactivate_connection;
nm_client_get_active_connections;
nm_client_get_device_by_path;
nm_client_get_devices;
nm_client_get_manager_running;
core: add permissions framework for various operations (rh #585182) (bgo #619323)
2010-05-28 18:23:00 -07:00
nm_client_get_permission_result;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_client_get_state;
nm_client_get_type;
core: add networking enable/disable knob distinct from sleep/wake (rh #589108) (bgo #346615) Since forever we've used sleep/wake as the way to implement Networking Enabled. When the state file was introduced to make the networking and wifi states persistent, we ran into a bug where a failed suspend (like if the machine ran out of power while suspended) would result in networking being disabled on reboot since suspend/resume used the same knob as enable/disable. This patch adds a distinct call for enable/disable networking which changes the state file, while sleep/wake no longer change the state file.
2010-05-22 08:55:30 -07:00
nm_client_networking_get_enabled;
nm_client_networking_set_enabled;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_client_new;
nm_client_sleep;
nm_client_wireless_get_enabled;
nm_client_wireless_hardware_get_enabled;
nm_client_wireless_set_enabled;
libnm-glib: add WWAN enable/disable support
2009-12-23 00:22:47 -08:00
nm_client_wwan_get_enabled;
nm_client_wwan_hardware_get_enabled;
nm_client_wwan_set_enabled;
wimax: Implement RFKILL handling Implement and export over DBus WiMAX enable/disable and hardware state query.
2009-12-29 11:27:10 +02:00
nm_client_wimax_get_enabled;
nm_client_wimax_hardware_get_enabled;
nm_client_wimax_set_enabled;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_dbus_settings_get_connection_by_path;
nm_dbus_settings_get_type;
nm_dbus_settings_new;
nm_dbus_settings_system_add_connection;
2008-11-14 Dan Williams <dcbw@redhat.com> * libnm-glib/libnm_glib.ver libnm-glib/nm-dbus-settings-system.c libnm-glib/nm-dbus-settings-system.h - Add libnm-glib bits for CanModify git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4289 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-11-14 19:54:10 +00:00
nm_dbus_settings_system_get_can_modify;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_dbus_settings_system_get_type;
nm_dbus_settings_system_get_unmanaged_devices;
nm_dbus_settings_system_new;
libnm-glib: add nm_device_disconnect function to glib API
2009-09-18 01:55:31 +02:00
nm_device_disconnect;
bluetooth: fixes and addition of NMDeviceBt to libnm-glib
2009-07-10 10:45:24 -04:00
nm_device_bt_new;
nm_device_bt_get_capabilities;
nm_device_bt_get_hw_address;
nm_device_bt_get_name;
nm_device_bt_get_type;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_device_ethernet_get_carrier;
nm_device_ethernet_get_hw_address;
core: MAC address spoofing/cloning (rh #447827) (bgo #553771) This commit implements MAC cloning feature in NetworkManager. To support that, 'PermHwAddress' property is added into *.Device.Wired and *.Device.Wireless interfaces. The permanent MAC address is obtained when creating the device, and is used for 'locking' connections to the device. If a cloned MAC is specified in connection to be activated, the MAC is set to the interface in stage1. While disconecting, the permanent MAC is set back to the interface.
2010-06-22 14:21:25 +02:00
nm_device_ethernet_get_permanent_hw_address;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_device_ethernet_get_speed;
nm_device_ethernet_get_type;
nm_device_ethernet_new;
nm_device_get_capabilities;
nm_device_get_dhcp4_config;
nm_device_get_driver;
core/libnm-glib: implement better missing firmware support (rh #594578) Track missing firmware and ensure the device can't be used when firmware is missing. Add a property for missing firmware so that clients can do something intelligent with this information.
2010-05-25 10:52:25 -07:00
nm_device_get_firmware_missing;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_device_get_iface;
nm_device_get_ip4_config;
libnm-glib: add NMIP6Config object that proxies device's IP6 config
2009-08-20 11:30:52 -05:00
nm_device_get_ip6_config;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_device_get_managed;
nm_device_get_product;
nm_device_get_state;
nm_device_get_type;
nm_device_get_udi;
nm_device_get_vendor;
nm_device_new;
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;
core: MAC address spoofing/cloning (rh #447827) (bgo #553771) This commit implements MAC cloning feature in NetworkManager. To support that, 'PermHwAddress' property is added into *.Device.Wired and *.Device.Wireless interfaces. The permanent MAC address is obtained when creating the device, and is used for 'locking' connections to the device. If a cloned MAC is specified in connection to be activated, the MAC is set to the interface in stage1. While disconecting, the permanent MAC is set back to the interface.
2010-06-22 14:21:25 +02:00
nm_device_wifi_get_permanent_hw_address;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_device_wifi_get_mode;
nm_device_wifi_get_type;
nm_device_wifi_new;
nm_dhcp4_config_get_one_option;
nm_dhcp4_config_get_options;
nm_dhcp4_config_get_type;
nm_dhcp4_config_new;
libnm-glib: fix export of NMDHCP6Config symbols Found by Giovanni Campagna <gcampagna@src.gnome.org>
2010-12-15 17:52:55 -06:00
nm_dhcp6_config_get_one_option;
nm_dhcp6_config_get_options;
nm_dhcp6_config_get_type;
nm_dhcp6_config_new;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_gsm_device_get_type;
nm_gsm_device_new;
nm_ip4_config_get_addresses;
nm_ip4_config_get_domains;
nm_ip4_config_get_hostname;
nm_ip4_config_get_nameservers;
Re-add WINS support to the IPv4 config Don't do anything with WINS servers (dispatcher scripts installed with samba could certainly update samba's idea of WINS servers), but at least provide them so that the VPNs that can get upstream WINS servers can at least make other stuff aware of them.
2008-12-19 17:01:06 -05:00
nm_ip4_config_get_wins_servers;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_ip4_config_get_routes;
nm_ip4_config_get_type;
nm_ip4_config_new;
libnm-glib: add NMIP6Config object that proxies device's IP6 config
2009-08-20 11:30:52 -05:00
nm_ip6_address_array_get_type;
nm_ip6_address_object_array_get_type;
nm_ip6_config_get_addresses;
nm_ip6_config_get_domains;
nm_ip6_config_get_nameservers;
nm_ip6_config_get_routes;
nm_ip6_config_get_type;
nm_ip6_config_new;
nm_ip6_route_object_array_get_type;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_object_array_get_type;
nm_object_get_connection;
nm_object_get_path;
nm_object_get_type;
remove nm-settings-connection-interface NMSettingsConnectionInterface was created to allow the daemon and NM clients to have common code that handled both system and user connections. It's no longer needed now that user settings services are gone. This concludes the flattening of libnm-glib.
2010-08-05 18:25:15 -04:00
nm_remote_connection_delete;
nm_remote_connection_get_secrets;
nm_remote_connection_commit_changes;
libnm-glib: implement new settings interfaces The old NMExportedConnection was used for both client and server-side classes, which was a mistake and made the code very complicated to follow. Additionally, all PolicyKit operations were synchronous, and PK operations can block for a long time (ie for user input) before returning, so they need to be async. But NMExportedConnection and NMSysconfigConnection didn't allow for async PK ops at all. Use this opportunity to clean up the mess and create GInterfaces that both server and client objects implement, so that the connection editor and applet can operate on generic objects like they did before (using the interfaces) but can perform specific operations (like async PK verification of callers) depending on whether they are local or remote or whatever.
2009-07-23 09:20:52 -04:00
nm_remote_connection_get_type;
nm_remote_connection_new;
libnm-glib: remove NMSettingsInterface NMSettingsInterface was created to allow code to operate on a settings service without caring about what kind of settings service it was. Now that we have just one settings service, this is no longer needed. More work needs to be done in order to handle errors and permission settings in an appropriate manner.
2010-08-03 13:23:30 -04:00
nm_remote_settings_add_connection;
nm_remote_settings_get_connection_by_path;
nm_remote_settings_list_connections;
nm_remote_settings_get_permissions;
nm_remote_settings_save_hostname;
libnm-glib: implement new settings interfaces The old NMExportedConnection was used for both client and server-side classes, which was a mistake and made the code very complicated to follow. Additionally, all PolicyKit operations were synchronous, and PK operations can block for a long time (ie for user input) before returning, so they need to be async. But NMExportedConnection and NMSysconfigConnection didn't allow for async PK ops at all. Use this opportunity to clean up the mess and create GInterfaces that both server and client objects implement, so that the connection editor and applet can operate on generic objects like they did before (using the interfaces) but can perform specific operations (like async PK verification of callers) depending on whether they are local or remote or whatever.
2009-07-23 09:20:52 -04:00
nm_remote_settings_get_type;
nm_remote_settings_new;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
nm_serial_device_get_bytes_received;
nm_serial_device_get_bytes_sent;
nm_serial_device_get_type;
nm_settings_error_quark;
nm_settings_get_type;
nm_settings_list_connections;
nm_settings_signal_new_connection;
nm_ssid_get_type;
nm_string_array_get_type;
nm_uint_array_get_type;
nm_vpn_connection_get_banner;
nm_vpn_connection_get_type;
nm_vpn_connection_get_vpn_state;
nm_vpn_connection_new;
wimax: add Center Frequency, RSSI, CINR, TX Power, and BSID properties Useful diagnostic/support info when device is connected.
2011-01-06 15:18:19 -06:00
nm_device_wimax_get_bsid;
nm_device_wimax_get_center_frequency;
nm_device_wimax_get_cinr;
wimax: make WiMAX mostly work Heavily modify Inaky's Intel WiMAX SDK glue (originally from connman) to be more generic and more thread-safe, and suitable for use with NetworkManager instead of rolling our own client code. Rewrite the NMDeviceWimax code to mostly work. Still to be done: actual connection logic, DHCP handling, spawning wimaxd if it's not started yet
2011-01-03 23:55:38 -06:00
nm_device_wimax_get_hw_address;
nm_device_wimax_get_active_nsp;
nm_device_wimax_get_nsp_by_path;
nm_device_wimax_get_nsps;
wimax: add Center Frequency, RSSI, CINR, TX Power, and BSID properties Useful diagnostic/support info when device is connected.
2011-01-06 15:18:19 -06:00
nm_device_wimax_get_rssi;
nm_device_wimax_get_tx_power;
wimax: make WiMAX mostly work Heavily modify Inaky's Intel WiMAX SDK glue (originally from connman) to be more generic and more thread-safe, and suitable for use with NetworkManager instead of rolling our own client code. Rewrite the NMDeviceWimax code to mostly work. Still to be done: actual connection logic, DHCP handling, spawning wimaxd if it's not started yet
2011-01-03 23:55:38 -06:00
nm_device_wimax_get_type;
nm_device_wimax_new;
wimax: Implement WiMAX support
2009-12-14 13:51:50 +02:00
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_new;
Add the actual version scripts git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3995 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-22 11:32:31 +00:00
local:
*;
};
Reference in a new issue Copy permalink