From 0984f0194709db2d85651615b0551054876dbcc5 Mon Sep 17 00:00:00 2001 From: Golubev Alexander Date: Sat, 27 Jul 2013 10:34:20 +0400 Subject: move all tdehw stuff into separate subdir --- .../dbus-introspection/CMakeLists.txt | 90 ++++ .../dbus-introspection/nm-access-point.xml | 92 ++++ .../dbus-introspection/nm-active-connection.xml | 76 +++ .../dbus-introspection/nm-agent-manager.xml | 38 ++ .../dbus-introspection/nm-device-adsl.xml | 21 + .../dbus-introspection/nm-device-bond.xml | 27 + .../dbus-introspection/nm-device-bt.xml | 48 ++ .../dbus-introspection/nm-device-ethernet.xml | 39 ++ .../dbus-introspection/nm-device-infiniband.xml | 27 + .../dbus-introspection/nm-device-modem.xml | 64 +++ .../dbus-introspection/nm-device-olpc-mesh.xml | 34 ++ .../dbus-introspection/nm-device-vlan.xml | 33 ++ .../dbus-introspection/nm-device-wifi.xml | 124 +++++ .../dbus-introspection/nm-device-wimax.xml | 103 ++++ .../dbus-introspection/nm-device.xml | 577 +++++++++++++++++++++ .../dbus-introspection/nm-dhcp4-config.xml | 20 + .../dbus-introspection/nm-dhcp6-config.xml | 20 + .../dbus-introspection/nm-ip4-config.xml | 29 ++ .../dbus-introspection/nm-ip6-config.xml | 19 + .../dbus-introspection/nm-manager.xml | 390 ++++++++++++++ .../dbus-introspection/nm-ppp-manager.xml | 22 + .../dbus-introspection/nm-secret-agent.xml | 177 +++++++ .../dbus-introspection/nm-settings-connection.xml | 93 ++++ .../dbus-introspection/nm-settings.xml | 102 ++++ .../dbus-introspection/nm-vpn-connection.xml | 146 ++++++ .../dbus-introspection/nm-vpn-plugin.xml | 199 +++++++ .../dbus-introspection/nm-wimax-nsp.xml | 44 ++ 27 files changed, 2654 insertions(+) create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/CMakeLists.txt create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-access-point.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-active-connection.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-agent-manager.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-adsl.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bond.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bt.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-ethernet.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-infiniband.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-modem.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-olpc-mesh.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-vlan.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wifi.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wimax.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp4-config.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp6-config.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip4-config.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip6-config.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-manager.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ppp-manager.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-secret-agent.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings-connection.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-connection.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-plugin.xml create mode 100644 tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-wimax-nsp.xml (limited to 'tdecore/tdehw/networkbackends/network-manager/dbus-introspection') diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/CMakeLists.txt b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/CMakeLists.txt new file mode 100644 index 000000000..144d56569 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/CMakeLists.txt @@ -0,0 +1,90 @@ +################################################# +# +# (C) 2010 Serghei Amelian +# serghei (DOT) amelian (AT) gmail.com +# +# Improvements and feedback are welcome +# +# This file is released under GPL >= 2 +# +################################################# + +include_directories( + ${CMAKE_CURRENT_BINARY_DIR} + ${TQT_INCLUDE_DIRS} + ${DBUS_TQT_INCLUDE_DIRS} +) + + +##### tdenm_dbus (static) ######################### + +set( INTROSPECTIONPATH ${CMAKE_CURRENT_SOURCE_DIR} ) + +# options: +# p - generate proxy files +# i - generate interface files +# n - generate node files + +function( add_dbus_xml option basename classname namespace xmlfile ) + if( classname ) + set( classname -c ${classname} ) + endif( ) + add_custom_command( OUTPUT ${basename}.cpp ${basename}.h + COMMAND ${DBUSXML2QT3_EXECUTABLE} -${option} ${basename} ${classname} -N ${namespace} ${INTROSPECTIONPATH}/${xmlfile} 2>/dev/null + DEPENDS ${INTROSPECTIONPATH}/${xmlfile} ) +endfunction( ) + +add_dbus_xml( p networkmanagerproxy NetworkManagerProxy DBus nm-manager.xml ) +add_dbus_xml( p networkmanagerpppproxy NetworkManagerPPPProxy DBus nm-ppp-manager.xml ) +add_dbus_xml( p deviceproxy DeviceProxy DBus nm-device.xml ) +add_dbus_xml( p wifiproxy WiFiDeviceProxy DBus nm-device-wifi.xml ) +add_dbus_xml( p wimaxproxy WiMaxDeviceProxy DBus nm-device-wimax.xml ) +add_dbus_xml( p olpcmeshproxy OlpcMeshDeviceProxy DBus nm-device-olpc-mesh.xml ) +add_dbus_xml( p bluetoothproxy BluetoothDeviceProxy DBus nm-device-bt.xml ) +add_dbus_xml( p ethernetproxy EthernetDeviceProxy DBus nm-device-ethernet.xml ) +add_dbus_xml( p infinibandproxy InfinibandDeviceProxy DBus nm-device-infiniband.xml ) +add_dbus_xml( p modemproxy ModemDeviceProxy DBus nm-device-modem.xml ) +add_dbus_xml( p accesspointproxy AccessPointProxy DBus nm-access-point.xml ) +add_dbus_xml( p activeconnectionproxy ActiveConnectionProxy DBus nm-active-connection.xml ) +add_dbus_xml( p vpnconnectionproxy VPNConnectionProxy DBus nm-vpn-connection.xml ) +add_dbus_xml( p vpnpluginproxy VPNPluginProxy DBus nm-vpn-plugin.xml ) +add_dbus_xml( p networkmanagersettings SettingsInterface DBus nm-settings.xml ) +add_dbus_xml( p connectionsettings ConnectionSettingsInterface DBus nm-settings-connection.xml ) + + +# generate moc files + +set( MOCHEADERS accesspointproxy.h deviceproxy.h networkmanagerproxy.h networkmanagerpppproxy.h bluetoothproxy.h olpcmeshproxy.h ethernetproxy.h + infinibandproxy.h wifiproxy.h wimaxproxy.h activeconnectionproxy.h vpnconnectionproxy.h vpnpluginproxy.h modemproxy.h + networkmanagersettings.h connectionsettings.h ) + +foreach( _header_file ${MOCHEADERS} ) + get_filename_component( _basename "${_header_file}" NAME_WE ) + set( _moc_file ${_basename}.moc ) + list( APPEND _moc_files ${_moc_file} ) + add_custom_command( OUTPUT ${_moc_file} + COMMAND ${TMOC_EXECUTABLE} ${_header_file} -o ${_moc_file} + DEPENDS ${_header_file} ) +endforeach( ) + +add_custom_command( OUTPUT mocfiles.cpp + COMMAND cat ${_moc_files} > mocfiles.cpp + DEPENDS ${_moc_files} ) + +# tde_automoc( accesspointproxy.h deviceproxy.h networkmanagerproxy.h +# networkmanagerpppproxy.h bluetoothproxy.h olpcmeshproxy.h +# ethernetproxy.h infinibandproxy.h wifiproxy.h wimaxproxy.h +# activeconnectionproxy.h vpnconnectionproxy.h vpnpluginproxy.h +# modemproxy.h networkmanagersettings.h connectionsettings.h ) + +# build the library + +tde_add_library( tdenm_dbus STATIC_PIC + SOURCES + networkmanagerproxy.cpp networkmanagerpppproxy.cpp + deviceproxy.cpp bluetoothproxy.cpp olpcmeshproxy.cpp ethernetproxy.cpp + infinibandproxy.cpp wifiproxy.cpp wimaxproxy.cpp accesspointproxy.cpp + networkmanagersettings.cpp connectionsettings.cpp + mocfiles.cpp activeconnectionproxy.cpp vpnconnectionproxy.cpp + vpnpluginproxy.cpp modemproxy.cpp +) diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-access-point.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-access-point.xml new file mode 100644 index 000000000..21f238ffa --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-access-point.xml @@ -0,0 +1,92 @@ + + + + + + Flags describing the capabilities of the access point. + + + Flags describing the access point's capabilities according to WPA (Wifi Protected Access). + + + Flags describing the access point's capabilities according to the RSN (Robust Secure Network) protocol. + + + The Service Set Identifier identifying the access point. + + + The radio channel frequency in use by the access point, in MHz. + + + The hardware address (BSSID) of the access point. + + + + Describes the operating mode of the access point. + + + The maximum bitrate this access point is capable of, in kilobits/second (Kb/s). + + + The current signal quality of the access point, in percent. + + + + + + A dictionary mapping property names to variant boxed values + + + + + + Flags describing the general capabilities of the access point. + + + Null capability - says nothing about the access point. + + + Access point supports privacy measures. + + + + + Flags describing the security capabilities of the access point. + + + Null flag. + + + Access point supports pairwise 40-bit WEP encryption. + + + Access point supports pairwise 104-bit WEP encryption. + + + Access point supports pairwise TKIP encryption. + + + Access point supports pairwise CCMP encryption. + + + Access point supports a group 40-bit WEP cipher. + + + Access point supports a group 104-bit WEP cipher. + + + Access point supports a group TKIP cipher. + + + Access point supports a group CCMP cipher. + + + Access point supports PSK key management. + + + Access point supports 802.1x key management. + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-active-connection.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-active-connection.xml new file mode 100644 index 000000000..ef01ab160 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-active-connection.xml @@ -0,0 +1,76 @@ + + + + + + Objects that implement the Connection.Active interface represent an attempt + to connect to a network using the details provided by a Connection object. + The Connection.Active object tracks the life-cycle of the connection + attempt and if successful indicates whether the connected network is the + "default" or preferred network for access. + + + + The path of the connection. + + + A specific object associated with the active connection. + + + + The UUID of the connection, provided as a convenience so that clients + do not have to retrieve all connection details. + + + + Array of object paths representing devices which are part of this active connection. + + + The state of this active connection. + + + Whether this active connection is the default IPv4 connection, i.e. whether it currently owns the default IPv4 route. + + + Whether this active connection is the default IPv6 connection, i.e. whether it currently owns the default IPv6 route. + + + Whether this active connection is also a VPN connection. + + + The path to the master device if the connection is a slave. + + + + + + A dictionary mapping property names to variant boxed values + + + + + + + + The active connection is in an unknown state. + + + + + The connection is activating. + + + + + The connection is activated. + + + + + The connection is being torn down and cleaned up. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-agent-manager.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-agent-manager.xml new file mode 100644 index 000000000..e26caacf4 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-agent-manager.xml @@ -0,0 +1,38 @@ + + + + + + + + Called by secret Agents to register their ability to provide and save + network secrets. + + + + + + Identifies this agent; only one agent in each user session may use the + same identifier. Identifier formatting follows the same rules as + D-Bus bus names with the exception that the ':' character is not + allowed. The valid set of characters is "[A-Z][a-z][0-9]_-." and the + identifier is limited in length to 255 characters with a minimum + of 3 characters. An example valid identifier is 'org.gnome.nm-applet' + (without quotes). + + + + + + + Called by secret Agents to notify NetworkManager that they will no + longer handle requests for network secrets. Agents are automatically + unregistered when they disconnect from D-Bus. + + + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-adsl.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-adsl.xml new file mode 100644 index 000000000..ec50d1104 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-adsl.xml @@ -0,0 +1,21 @@ + + + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + + Indicates whether the physical carrier is found. + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bond.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bond.xml new file mode 100644 index 000000000..9d200ef8f --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bond.xml @@ -0,0 +1,27 @@ + + + + + + + + Hardware address of the device. + + + + + + Indicates whether the physical carrier is found (e.g. whether a cable is plugged in or not). + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bt.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bt.xml new file mode 100644 index 000000000..cc4a9b544 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-bt.xml @@ -0,0 +1,48 @@ + + + + + + + + Bluetooth hardware address of the device. + + + + + + Bluetooth name of the device. + + + + + + Bluetooth capabilities of the device (either DUN or NAP). + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + + Flags describing the capabilities of a Bluetooth device. + + + The device has no recognized capabilities. + + + The device supports Bluetooth Dial-Up Networking. + + + The device supports Bluetooth Personal Area Networking. + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-ethernet.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-ethernet.xml new file mode 100644 index 000000000..000caf752 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-ethernet.xml @@ -0,0 +1,39 @@ + + + + + + + + Active hardware address of the device. + + + + + + Permanent hardware address of the device. + + + + + + Design speed of the device, in megabits/second (Mb/s). + + + + + + Indicates whether the physical carrier is found (e.g. whether a cable is plugged in or not). + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-infiniband.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-infiniband.xml new file mode 100644 index 000000000..097714c69 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-infiniband.xml @@ -0,0 +1,27 @@ + + + + + + + + Hardware address of the device. + + + + + + Indicates whether the physical carrier is found (e.g. whether a cable is plugged in or not). + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-modem.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-modem.xml new file mode 100644 index 000000000..0ca101fd7 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-modem.xml @@ -0,0 +1,64 @@ + + + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + + The generic family of access technologies the modem supports. Not all + capabilities are available at the same time however; some modems require + a firmware reload or other reinitialization to switch between eg CDMA/EVDO + and GSM/UMTS. + + + + + + The generic family of access technologies the modem currently supports + without a firmware reload or reinitialization. + + + + + + Flags describing one or more of the general access technology families + that a modem device supports. + + + Modem has no capabilties. + + + + Modem supports the analog wired telephone network (ie 56k dialup) and + does not have wireless/cellular capabilities. + + + + + Modem supports at least one of CDMA 1xRTT, EVDO revision 0, EVDO + revision A, or EVDO revision B. + + + + + Modem supports at least one of GSM, GPRS, EDGE, UMTS, HSDPA, HSUPA, or + HSPA+ packet switched data capability. + + + + + Modem has at LTE data capability. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-olpc-mesh.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-olpc-mesh.xml new file mode 100644 index 000000000..c30ecfc60 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-olpc-mesh.xml @@ -0,0 +1,34 @@ + + + + + + + The hardware address of the device. + + + + + + The object path of the companion device. + + + + + + The currently active channel. + + + + + + + A dictionary containing the FIXME: check changed parameters. + + + + Emitted when the wireless device's properties changed. + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-vlan.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-vlan.xml new file mode 100644 index 000000000..54b7bbe48 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-vlan.xml @@ -0,0 +1,33 @@ + + + + + + + + Hardware address of the device. + + + + + + Indicates whether the physical carrier is found (e.g. whether a cable is plugged in or not). + + + + + + The VLAN ID of this VLAN interface. + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wifi.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wifi.xml new file mode 100644 index 000000000..531fc8930 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wifi.xml @@ -0,0 +1,124 @@ + + + + + + + + + List of access point object paths + + + + Get the list of access points visible to this device. + + + + + + + + + Options of scan + + + + Request the device to scan + + + + + + The active hardware address of the device. + + + + + + The permanent hardware address of the device. + + + + + + The operating mode of the wireless device. + + + + + + The bit rate currently used by the wireless device, in kilobits/second (Kb/s). + + + + + Object path of the access point currently used by the wireless device. + + + + + The capabilities of the wireless device. + + + + + + + A dictionary containing the FIXME: check changed parameters. + + + + Emitted when the wireless device's properties changed. + + + + + + + The object path of the newly found access point. + + + + Emitted when a new access point is found by the device. + + + + + + + The object path of the access point that has disappeared. + + + + Emitted when an access point disappears from view of the device. + + + + + + Flags describing the capabilities of a wireless device. + + + Null capability - syntactic sugar for no capabilities supported. Do not AND this with other capabilities! + + + The device supports the 40-bit WEP cipher. + + + The device supports the 104-bit WEP cipher. + + + The device supports the TKIP cipher. + + + The device supports the CCMP cipher. + + + The device supports the WPA encryption/authentication protocol. + + + The device supports the RSN encryption/authentication protocol. + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wimax.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wimax.xml new file mode 100644 index 000000000..6e414087f --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device-wimax.xml @@ -0,0 +1,103 @@ + + + + + + + + + List of NSP object paths + + + + Get the list of NSPs visible to this device. + + + + + + Hardware address of the device. + + + + + + Center frequency (in KHz) of the radio channel the device is using to + communicate with the network when connected. Has no meaning when the + device is not connected. + + + + + + RSSI of the current radio link in dBm. This value indicates how strong + the raw received RF signal from the base station is, but does not + indicate the overall quality of the radio link. Has no meaning when the + device is not connected. + + + + + + CINR (Carrier to Interference + Noise Ratio) of the current radio link + in dB. CINR is a more accurate measure of radio link quality. Has no + meaning when the device is not connected. + + + + + + Average power of the last burst transmitted by the device, in units of + 0.5 dBm. i.e. a TxPower of -11 represents an actual device TX power of + -5.5 dBm. Has no meaning when the device is not connected. + + + + + + The ID of the serving base station as received from the network. Has + no meaning when the device is not connected. + + + + + + Object path of the NSP currently used by the WiMax device. + + + + + + + A dictionary mapping property names to variant boxed values. + + + + Emitted when the WiMax device's properties changed. + + + + + + + The object path of the newly found NSP. + + + + Emitted when a new NSP is found by the device. + + + + + + + The object path of the NSP that has disappeared. + + + + Emitted when an NSP disappears from view of the device. + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device.xml new file mode 100644 index 000000000..5b2c98b3c --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-device.xml @@ -0,0 +1,577 @@ + + + + + + + Operating-system specific transient device hardware identifier. This + is an opaque string representing the underlying hardware for the device, + and shouldn't be used to keep track of individual devices. For some + device types (Bluetooth, Modems) it is an identifier used by the + hardware service (ie bluez or ModemManager) to refer to that device, + and client programs use it get additional information from those + services which NM does not provide. The Udi is not guaranteed to be + consistent across reboots or hotplugs of the hardware. If you're looking + for a way to uniquely track each device in your application, use the + object path. If you're looking for a way to track a specific piece of + hardware across reboot or hotplug, use a MAC address or USB serial + number. + + + + + The name of the device's control (and often data) interface. + + + + + The name of the device's data interface when available. This property + may not refer to the actual data interface until the device has + successfully established a data connection, indicated by the device's + State becoming ACTIVATED. + + + + + The driver handling the device. + + + + + The version of the driver handling the device. + + + + + The firmware version for the device. + + + + + Flags describing the capabilities of the device. + + + + + The IPv4 address bound to the device. FIXME: what about devices with >1 IP address? + + + + + The current state of the device. + + + + + The current state and reason for changing to that state. + + + + + Object path of an ActiveConnection object that "owns" this device during + activation. The ActiveConnection object tracks the life-cycle of a + connection to a specific network and implements the + org.freedesktop.NetworkManager.Connection.Active D-Bus interface. + + + + + Object path of the Ip4Config object describing the configuration of the device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state. + + + + + Object path of the Dhcp4Config object describing the DHCP options returned by the DHCP server. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state. + + + + + Object path of the Ip6Config object describing the configuration of the device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state. + + + + + Object path of the Dhcp6Config object describing the DHCP options + returned by the DHCP server. Only valid when the device is in the + NM_DEVICE_STATE_ACTIVATED state. + + + + + Whether or not this device is managed by NetworkManager. + + + + + If TRUE, indicates the device is allowed to autoconnect. If FALSE, + manual intervention is required before the device will automatically + connect to a known network, such as activating a connection using the + device, or setting this property to TRUE. + + + + + If TRUE, indicates the device is likely missing firmware necessary for + its operation. + + + + + The general type of the network device; ie Ethernet, WiFi, etc. + + + + + An array of object paths of every configured connection that is currently 'available' through this device. + + + + + + + + Disconnects a device and prevents the device from automatically activating further connections without user intervention. + + + + + + + The new state of the device. + + + + + The previous state of the device. + + + + + A reason for the state transition. + + + + + + + + The device is in an unknown state. + + + + + The device is recognized but not managed by NetworkManager. + + + + + The device cannot be used (carrier off, rfkill, etc). + + + + + The device is not connected. + + + + + The device is preparing to connect. + + + + + The device is being configured. + + + + + The device is awaiting secrets necessary to continue connection. + + + + + The IP settings of the device are being requested and configured. + + + + + The device's IP connectivity ability is being determined. + + + + + The device is waiting for secondary connections to be activated. + + + + + The device is active. + + + + + The device's network connection is being torn down. + + + + + The device is in a failure state following an attempt to activate it. + + + + + + + + The device type is unknown. + + + + + The device is wired Ethernet device. + + + + + The device is an 802.11 WiFi device. + + + + Unused + + + Unused + + + + The device is Bluetooth device that provides PAN or DUN capabilities. + + + + + The device is an OLPC mesh networking device. + + + + + The device is an 802.16e Mobile WiMAX device. + + + + + The device is a modem supporting one or more of analog telephone, + CDMA/EVDO, GSM/UMTS/HSPA, or LTE standards to access a cellular or + wireline data network. + + + + + The device is an IP-capable InfiniBand interface. + + + + + The device is a bond master interface. + + + + + The device is a VLAN interface. + + + + + The device is an ADSL device supporting PPPoE and PPPoATM protocols. + + + + + + + Null capability. + + + The device is supported by NetworkManager. + + + The device supports carrier detection. + + + + + + + The reason for the device state change is unknown. + + + + + The state change is normal. + + + + + The device is now managed. + + + + + The device is no longer managed. + + + + + The device could not be readied for configuration. + + + + + IP configuration could not be reserved (no available address, timeout, etc). + + + + + The IP configuration is no longer valid. + + + + + Secrets were required, but not provided. + + + + + The 802.1X supplicant disconnected from the access point or authentication server. + + + + + Configuration of the 802.1X supplicant failed. + + + + + The 802.1X supplicant quit or failed unexpectedly. + + + + + The 802.1X supplicant took too long to authenticate. + + + + + The PPP service failed to start within the allowed time. + + + + + The PPP service disconnected unexpectedly. + + + + + The PPP service quit or failed unexpectedly. + + + + + The DHCP service failed to start within the allowed time. + + + + + The DHCP service reported an unexpected error. + + + + + The DHCP service quit or failed unexpectedly. + + + + + The shared connection service failed to start. + + + + + The shared connection service quit or failed unexpectedly. + + + + + The AutoIP service failed to start. + + + + + The AutoIP service reported an unexpected error. + + + + + The AutoIP service quit or failed unexpectedly. + + + + + Dialing failed because the line was busy. + + + + + Dialing failed because there was no dial tone. + + + + + Dialing failed because there was carrier. + + + + + Dialing timed out. + + + + + Dialing failed. + + + + + Modem initialization failed. + + + + + Failed to select the specified GSM APN. + + + + + Not searching for networks. + + + + + Network registration was denied. + + + + + Network registration timed out. + + + + + Failed to register with the requested GSM network. + + + + + PIN check failed. + + + + + Necessary firmware for the device may be missing. + + + + + The device was removed. + + + + + NetworkManager went to sleep. + + + + + The device's active connection was removed or disappeared. + + + + + A user or client requested the disconnection. + + + + + The device's carrier/link changed. + + + + + The device's existing connection was assumed. + + + + + The 802.1x supplicant is now available. + + + + + The modem could not be found. + + + + + The Bluetooth connection timed out or failed. + + + + + GSM Modem's SIM Card not inserted. + + + + + GSM Modem's SIM Pin required. + + + + + GSM Modem's SIM Puk required. + + + + + GSM Modem's SIM wrong + + + + + InfiniBand device does not support connected mode. + + + + + A dependency of the connection failed. + + + + + Problem with the RFC 2684 Ethernet over ADSL bridge. + + + + + + + + The device state. + + + + + The reason for originally changing to the device state. + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp4-config.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp4-config.xml new file mode 100644 index 000000000..c0821ada9 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp4-config.xml @@ -0,0 +1,20 @@ + + + + + + Options and configuration returned by the IPv4 DHCP server. + + + Configuration options returned by a DHCP server, if any. + + + + + + A dictionary mapping property names to variant boxed values + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp6-config.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp6-config.xml new file mode 100644 index 000000000..93b0f1c8f --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-dhcp6-config.xml @@ -0,0 +1,20 @@ + + + + + + Options and configuration returned by the IPv6 DHCP server. + + + Configuration options returned by a DHCP server, if any. + + + + + + A dictionary mapping property names to variant boxed values + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip4-config.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip4-config.xml new file mode 100644 index 000000000..70d3e1ce4 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip4-config.xml @@ -0,0 +1,29 @@ + + + + + + Array of tuples of IPv4 address/prefix/gateway. All 3 + elements of each tuple are in network byte order. Essentially: + [(addr, prefix, gateway), (addr, prefix, gateway), ...] + + + + The nameservers in use. + + + The Windows Internet Name Service servers associated with the connection. Each address is in network byte order. + + + A list of domains this address belongs to. + + + Tuples of IPv4 route/prefix/next-hop/metric. All 4 elements + of each tuple are in network byte order. 'route' and 'next hop' are IPv4 + addresses, while prefix and metric are simple unsigned integers. Essentially: + [(route, prefix, next-hop, metric), (route, prefix, next-hop, metric), ...] + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip6-config.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip6-config.xml new file mode 100644 index 000000000..604781857 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ip6-config.xml @@ -0,0 +1,19 @@ + + + + + + Tuples of IPv6 address/prefix/gateway. + + + The nameservers in use. + + + A list of domains this address belongs to. + + + Tuples of IPv6 route/prefix/next-hop/metric. + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-manager.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-manager.xml new file mode 100644 index 000000000..f5fd7abcf --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-manager.xml @@ -0,0 +1,390 @@ + + + + + + + Get the list of network devices. + + + + + List of object paths of network devices known to the system. + + + + + + + Return the object path of the network device referenced by its IP + interface name. Note that some devices (usually modems) only have an + IP interface name when they are connected. + + + + + Interface name of the device to find. + + + + + Object path of the network device. + + + + + + + + + Activate a connection using the supplied device. + + + + The connection to activate the devices with. + + + + + The object path of device to be activated for physical connections. This parameter is ignored for VPN connections, because the specific_object (if provided) specifies the device to use. + + + + + The path of a connection-type-specific object this activation should use. + This parameter is currently ignored for wired and mobile broadband connections, + and the value of "/" should be used (ie, no specific object). For WiFi + connections, pass the object path of a specific AP from the card's scan + list, or "/" to pick and AP automatically. For VPN connections, pass + the object path of an ActiveConnection object that should serve as the + "base" connection (to which the VPN connections lifetime will be tied), + or pass "/" and NM will automatically use the current default device. + + + + + The path of the active connection object representing this active connection. + + + + + + + Another connection is already activating or the same connection is already active. FIXME: check if the error name is correct. FIXME: split into 2 errors? + + + The connection is invalid for this device. + + + + + + + + + Adds a new connection using the given details (if any) as a template + (automatically filling in missing settings with the capabilities of the + given device and specific object), then activate the new connection. + Cannot be used for VPN connections at this time. + + + + Connection settings and properties; if incomplete missing settings will + be automatically completed using the given device and specific object. + + + + + The object path of device to be activated using the given connection. + + + + + The path of a connection-type-specific object this activation should use. + This parameter is currently ignored for wired and mobile broadband connections, + and the value of "/" should be used (ie, no specific object). For WiFi + connections, pass the object path of a specific AP from the card's scan + list, which will be used to complete the details of the newly added + connection. + + + + + Object path of the new connection that was just added. + + + + + The path of the active connection object representing this active connection. + + + + + + + The connection is invalid for this device. + + + + + + + Deactivate an active connection. + + + + + + The currently active connection to deactivate. + + + + + + + + + Control the NetworkManager daemon's sleep state. When asleep, all + interfaces that it manages are deactivated. When awake, devices are + available to be activated. This command should not be called directly + by users or clients; it is intended for system suspend/resume tracking. + + + + Indicates whether the NetworkManager daemon should sleep or wake. + + + + + + + + + Control whether overall networking is enabled or disabled. When + disabled, all interfaces that NM manages are deactivated. When enabled, + all managed interfaces are re-enabled and available to be activated. + This command should be used by clients that provide to users the ability + to enable/disable all networking. + + + + If FALSE, indicates that all networking should be disabled. If TRUE, + indicates that NetworkManager should begin managing network devices. + + + + + + + + + Returns the permissions a caller has for various authenticated operations + that NetworkManager provides, like Enable/Disable networking, changing + WiFi, WWAN, and WiMAX state, etc. + + + + Dictionary of available permissions and results. Each permission + is represented by a name (ie "org.freedesktop.NetworkManager.Foobar") + and each result is one of the following values: "yes" (the permission + is available), "auth" (the permission is available after a successful + authentication), or "no" (the permission is denied). Clients may use + these values in the UI to indicate the ability to perform certain + operations. + + + + + + + Emitted when system authorization details change, indicating that + clients may wish to recheck permissions with GetPermissions. + + + + + + + Set logging verbosity and which operations are logged. + + + + One of [ERR, WARN, INFO, DEBUG]. + + + + + A combination of logging domains separated by commas (','), or "NONE" + to disable logging. Each domain enables logging for operations + related to that domain. Available domains are: [NONE, HW, RFKILL, + ETHER, WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, + DNS, VPN, SHARING, SUPPLICANT, USER_SET, SYS_SET, SUSPEND, CORE, + DEVICE, OLPC]. If an empty string is given, the log level is changed + but the current set of log domains remains unchanged. + + + + + + + The overall networking state as determined by the NetworkManager daemon, + based on the state of network devices under it's management. + + + + + + + + Indicates if overall networking is currently enabled or not. See the + Enable() method. + + + + + + Indicates if wireless is currently enabled or not. + + + + + + Indicates if the wireless hardware is currently enabled, i.e. the state of the RF kill switch. + + + + + + Indicates if mobile broadband devices are currently enabled or not. + + + + + + Indicates if the mobile broadband hardware is currently enabled, i.e. the state of the RF kill switch. + + + + + + Indicates if WiMAX devices are currently enabled or not. + + + + + + Indicates if the WiMAX hardware is currently enabled, i.e. the state of the RF kill switch. + + + + + + List of active connection object paths. + + + + + + NetworkManager version. + + + + + + The overall state of the NetworkManager daemon. + + + + + + NetworkManager's state changed. + + + + The new state of NetworkManager. + + + + + + + NetworkManager's properties changed. + + + + The changed properties. + + + + + + + A device was added to the system + + + + The object path of the newly added device. + + + + + + + A device was removed from the system, and is no longer available. + + + + The object path of the device that was just removed. + + + + + + + Describes the overall state of the daemon. + + + + Networking state is unknown. + + + + + Networking is inactive and all devices are disabled. + + + + + There is no active network connection. + + + + + Network connections are being cleaned up. + + + + + A network device is connecting to a network and there is no other + available network connection. + + + + + A network device is connected, but there is only link-local connectivity. + + + + + A network device is connected, but there is only site-local connectivity. + + + + + A network device is connected, with global network connectivity. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ppp-manager.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ppp-manager.xml new file mode 100644 index 000000000..9e2dfdb1c --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-ppp-manager.xml @@ -0,0 +1,22 @@ + + + + + + + + + + + + + + + + + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-secret-agent.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-secret-agent.xml new file mode 100644 index 000000000..81a1321b1 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-secret-agent.xml @@ -0,0 +1,177 @@ + + + + + + + Private D-Bus interface used by secret agents that store and provide + secrets to NetworkManager. If an agent provides secrets to + NetworkManager as part of connection creation, and the some of those + secrets are "agent owned" the agent should store those secrets + itself and should not expect its SaveSecrets() method to be called. + SaveSecrets() will be called eg if some program other than the + agent itself (like a connection editor) changes the secrets out of + band. + + + + + Retrieve and return stored secrets, if any, or request new + secrets from the agent's user. + + + + + + Nested settings maps containing the connection for which + secrets are being requested. This may contain system-owned + secrets if the agent has successfully authenticated to + modify system network settings and the GetSecrets request + flags allow user interaction. + + + + + Object path of the connection for which secrets are being + requested. + + + + + Setting name for which secrets are being requested. + + + + + Array of strings of key names in the requested setting for + which NetworkManager thinks a secrets may be required, + and/or well-known identifiers and data that may be useful + to the client in processing the secrets request. The Agent + should return any secrets it has, or that it thinks are + required, regardless of what hints NetworkManager sends + in this request. + + + + + Flags which modify the behavior of the secrets request. + If true, new secrets are assumed to be invalid or incorrect, + and the agent should ask the user for new secrets. If false, + existing secrets should be retrieved from storage and + returned without interrupting the user. + + + + + + Nested settings maps containing secrets. Each setting MUST + contain at least the 'name' field, containing the name of + the setting, and one or more secrets. + + + + + + + Flags modifying the behavior of GetSecrets request. + + + + No special behavior; by default no user interaction is allowed and + requests for secrets are fulfilled from persistent storage, or + if no secrets are available an error is returned. + + + + + Allows the request to interact with the user, possibly prompting + via UI for secrets if any are required, or if none are found in + persistent storage. + + + + + Explicitly prompt for new secrets from the user. This flag + signals that NetworkManager thinks any existing secrets are + invalid or wrong. This flag implies that interaction is allowed. + + + + + Set if the request was initiated by user-requested action via the + D-Bus interface, as opposed to automatically initiated by + NetworkManager in response to (for example) scan results or + carrier changes. + + + + + + + Cancel a pending GetSecrets request for secrets of the given + connection. Any matching request should be canceled. + + + + + + Object path of the connection for which, if secrets are being + requested, the request should be canceled. + + + + + Setting name for which secrets for this connection were + originally being requested. + + + + + + + Save given secrets to backing storage. + + + + + + Nested settings maps containing the entire connection + (including secrets), for which the agent should save the + secrets to backing storage. This method will not be called + when the agent itself is the process creating or updating + a connection; in that case the agent is assumed to have + already saved those secrets since it had them already. + + + + + Object path of the connection for which the agent should + save secrets to backing storage. + + + + + + + Delete secrets from backing storage. + + + + + + Nested settings maps containing the connection properties + (sans secrets), for which the agent should delete the + secrets from backing storage. + + + + + Object path of the connection for which the agent should + delete secrets from backing storage. + + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings-connection.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings-connection.xml new file mode 100644 index 000000000..9089b009a --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings-connection.xml @@ -0,0 +1,93 @@ + + + + + + + Represents a single network connection configuration. + + + + + Update the connection with new settings and properties, replacing + all previous settings and properties. Secrets may be part of the + update request, and will be either stored in persistent storage or + given to a Secret Agent for storage, depending on the request. + + + + + + New connection settings, properties, and (optionally) secrets. + + + + + + + Delete the connection. + + + + + + + + Get the settings maps describing this network configuration. + This will never include any secrets required for connection + to the network, as those are often protected. Secrets must + be requested separately using the GetSecrets() call. + + + + + + The nested settings maps describing this object. + + + + + + + Get the secrets belonging to this network configuration. Only + secrets from persistent storage or a Secret Agent running in + the requestor's session will be returned. The user will never + be prompted for secrets as a result of this request. + + + + + + Name of the setting to return secrets for. If empty, all + all secrets will be returned. + + + + + + Nested settings maps containing secrets. + + + + + + + Emitted when any settings or permissions change. When handling + this signal, clients should re-read the connection using the + GetSettings method to get the changes and to ensure the client + still has permission to access the connection. + + + + + + Emitted when this connection is no longer available. This + happens when the connection is deleted or if it is no longer + accessable by any of the system's logged-in users. After + receipt of this signal, the object no longer exists. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings.xml new file mode 100644 index 000000000..301cde76d --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-settings.xml @@ -0,0 +1,102 @@ + + + + + + The Settings interface allows clients to view and administrate the connections stored and used by NetworkManager. + + + + + List the connections stored by this Settings object. + + + + + List of connections. + + + + + + + Retrieve the object path of a connection, given that connection's UUID. + + + + + The UUID to find the connection object path for. + + + + + The connection's object path. + + + + + + + Add new connection. + + + + + + Connection settings and properties. + + + + + Object path of the new connection that was just added. + + + + + + + Save the hostname to persistent configuration. + + + + + + The hostname to save to persistent configuration. If blank, the persistent hostname is cleared. + + + + + + + The machine hostname stored in persistent configuration. + + + + + + If true, adding and modifying connections is supported. + + + + + + + A dictionary mapping property names to variant boxed values + + + + + + + Emitted when a new connection has been added. + + + + Object path of the new connection. + + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-connection.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-connection.xml new file mode 100644 index 000000000..65b917854 --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-connection.xml @@ -0,0 +1,146 @@ + + + + + + Represents an active connection to a Virtual Private Network. + + + + + + A dictionary mapping property names to variant boxed values + + + + + + The VPN-specific state of the connection. + + + The banner string of the VPN connection. + + + + + Emitted when the state of the VPN connection has changed. + + + + The new state of the VPN connection. + + + + + Reason code describing the change to the new state. + + + + + + + + The state of the VPN connection is unknown. + + + + + The VPN connection is preparing to connect. + + + + + The VPN connection needs authorization credentials. + + + + + The VPN connection is being established. FIXME: Should be CONNECTING or CONNECTED. + + + + + The VPN connection is getting an IP address. FIXME: Should be an -ING + + + + + The VPN connection is active. + + + + + The VPN connection failed. + + + + + The VPN connection is disconnected. + + + + + + + The reason for the VPN connection state change is unknown. + + + + + No reason was given for the VPN connection state change. + + + + + The VPN connection changed state because the user disconnected it. + + + + + The VPN connection changed state because the device it was using was disconnected. + + + + + The service providing the VPN connection was stopped. + + + + + The IP config of the VPN connection was invalid. + + + + + The connection attempt to the VPN service timed out. + + + + + A timeout occurred while starting the service providing the VPN connection. + + + + + Starting the service starting the service providing the VPN connection failed. + + + + + Necessary secrets for the VPN connection were not provided. + + + + + Authentication to the VPN server failed. + + + + + The connection was deleted from settings. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-plugin.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-plugin.xml new file mode 100644 index 000000000..5fb11622a --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-vpn-plugin.xml @@ -0,0 +1,199 @@ + + + + + + This interface is provided by plugins providing VPN services to the NetworkManager daemon. + + + + Tells the plugin to connect. + + + + + Describes the connection to be established. + + + + + + + + + + + + + + Asks the plugin whether the provided connection will require secrets to connect successfully. + + + + + Describes the connection that may need secrets. + + + + + The setting name within the provided connection that requires secrets, if any. + + + + + + + + + + Disconnect the plugin. + + + + + + + + + + + Set generic connection details on the connection. + + + + + Generic configuration details for the connection. + + + + + + + Set IPv4 details on the connection. + + + + + Ip4Config details for the connection. You must call + SetConfig() before calling this. + + + + + + + Set IPv6 details on the connection. + + + + + Ip6Config details for the connection. You must call + SetConfig() before calling this. + + + + + + + Indicate a failure to the plugin. + + + + + The reason for the failure. + + + + + + + The state of the plugin. + + + + + + Emitted when the plugin state changes. + + + + The new state of the plugin. + + + + + + + The plugin obtained generic configuration information. + + + + The configuration information. + + + + + + + The plugin obtained an IPv4 configuration. + + + + The IPv4 configuration. + + + + + + + The plugin obtained an IPv6 configuration. + + + + The IPv6 configuration. + + + + + + + Emitted when the plugin receives a login banner from the VPN service. + + + + The login banner string. + + + + + + + Emitted when a failure in the VPN plugin occurs. + + + + Reason code for the failure. + + + + + + + + Login failed. + + + + + Connect failed. + + + + + Invalid IP configuration returned from the VPN plugin. + + + + + + diff --git a/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-wimax-nsp.xml b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-wimax-nsp.xml new file mode 100644 index 000000000..55ac4abcf --- /dev/null +++ b/tdecore/tdehw/networkbackends/network-manager/dbus-introspection/nm-wimax-nsp.xml @@ -0,0 +1,44 @@ + + + + + + + The name of the NSP. + + + The current signal quality of the NSP, in percent. + + + The network type of the NSP. + + + + + + A dictionary mapping property names to variant boxed values. + + + + + + + Network type of the NSP. + + + Unknown network. + + + Home network. + + + Partner network. + + + Roaming partner network. + + + + + + -- cgit v1.2.1