1 <?xml version="1.0" encoding="UTF-8" ?>
3 <node name="/org/freedesktop/NetworkManager" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
4 <interface name="org.freedesktop.NetworkManager">
5 <annotation name="org.gtk.GDBus.C.Name" value="Manager"/>
7 <method name="GetDevices">
9 Get the list of realized network devices.
11 <arg name="devices" type="ao" direction="out">
13 List of object paths of network devices known to the system. This
14 list does not include device placeholders (see GetAllDevices()).
19 <method name="GetAllDevices">
21 Get the list of all network devices.
23 <annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_manager_get_all_devices"/>
24 <arg name="devices" type="ao" direction="out">
26 List of object paths of network devices and device placeholders
27 (eg, devices that do not yet exist but which can be automatically
28 created by NetworkManager if one of their AvailableConnections
34 <method name="GetDeviceByIpIface">
36 Return the object path of the network device referenced by its IP
37 interface name. Note that some devices (usually modems) only have an
38 IP interface name when they are connected.
40 <arg name="iface" type="s" direction="in">
42 Interface name of the device to find.
45 <arg name="device" type="o" direction="out">
47 Object path of the network device.
52 <method name="ActivateConnection">
54 Activate a connection using the supplied device.
56 <arg name="connection" type="o" direction="in">
58 The connection to activate. If "/" is given, a valid device path must
59 be given, and NetworkManager picks the best connection to activate for
60 the given device. VPN connections must always pass a valid connection
64 <arg name="device" type="o" direction="in">
66 The object path of device to be activated for physical connections.
67 This parameter is ignored for VPN connections, because the
68 specific_object (if provided) specifies the device to use.
71 <arg name="specific_object" type="o" direction="in">
73 The path of a connection-type-specific object this activation should use.
74 This parameter is currently ignored for wired and mobile broadband connections,
75 and the value of "/" should be used (ie, no specific object). For WiFi
76 connections, pass the object path of a specific AP from the card's scan
77 list, or "/" to pick an AP automatically. For VPN connections, pass
78 the object path of an ActiveConnection object that should serve as the
79 "base" connection (to which the VPN connections lifetime will be tied),
80 or pass "/" and NM will automatically use the current default device.
83 <arg name="active_connection" type="o" direction="out">
85 The path of the active connection object representing this active connection.
90 <method name="AddAndActivateConnection">
92 Adds a new connection using the given details (if any) as a template
93 (automatically filling in missing settings with the capabilities of the
94 given device and specific object), then activate the new connection.
95 Cannot be used for VPN connections at this time.
97 <arg name="connection" type="a{sa{sv}}" direction="in">
99 Connection settings and properties; if incomplete missing settings will
100 be automatically completed using the given device and specific object.
103 <arg name="device" type="o" direction="in">
105 The object path of device to be activated using the given connection.
108 <arg name="specific_object" type="o" direction="in">
110 The path of a connection-type-specific object this activation should use.
111 This parameter is currently ignored for wired and mobile broadband connections,
112 and the value of "/" should be used (ie, no specific object). For WiFi
113 connections, pass the object path of a specific AP from the card's scan
114 list, which will be used to complete the details of the newly added
118 <arg name="path" type="o" direction="out">
120 Object path of the new connection that was just added.
123 <arg name="active_connection" type="o" direction="out">
125 The path of the active connection object representing this active connection.
130 <method name="DeactivateConnection">
132 Deactivate an active connection.
134 <arg name="active_connection" type="o" direction="in">
136 The currently active connection to deactivate.
141 <method name="Sleep">
143 Control the NetworkManager daemon's sleep state. When asleep, all
144 interfaces that it manages are deactivated. When awake, devices are
145 available to be activated. This command should not be called directly
146 by users or clients; it is intended for system suspend/resume tracking.
148 <arg name="sleep" type="b" direction="in">
150 Indicates whether the NetworkManager daemon should sleep or wake.
155 <method name="Enable">
157 Control whether overall networking is enabled or disabled. When
158 disabled, all interfaces that NM manages are deactivated. When enabled,
159 all managed interfaces are re-enabled and available to be activated.
160 This command should be used by clients that provide to users the ability
161 to enable/disable all networking.
163 <arg name="enable" type="b" direction="in">
165 If FALSE, indicates that all networking should be disabled. If TRUE,
166 indicates that NetworkManager should begin managing network devices.
171 <method name="GetPermissions">
173 Returns the permissions a caller has for various authenticated operations
174 that NetworkManager provides, like Enable/Disable networking, changing
175 WiFi, WWAN, and WiMAX state, etc.
177 <arg name="permissions" type="a{ss}" direction="out">
179 Dictionary of available permissions and results. Each permission
180 is represented by a name (ie "org.freedesktop.NetworkManager.Foobar")
181 and each result is one of the following values: "yes" (the permission
182 is available), "auth" (the permission is available after a successful
183 authentication), or "no" (the permission is denied). Clients may use
184 these values in the UI to indicate the ability to perform certain
190 <signal name="CheckPermissions">
192 Emitted when system authorization details change, indicating that
193 clients may wish to recheck permissions with GetPermissions.
197 <method name="SetLogging">
199 Set logging verbosity and which operations are logged.
201 <arg name="level" type="s" direction="in">
203 One of [ERR, WARN, INFO, DEBUG, TRACE, OFF, KEEP].
204 This level is applied to the domains as specified in the domains
205 argument. Except for the special level "KEEP", all unmentioned
206 domains are disabled entirely. "KEEP" is special and allows
207 not to change the current setting except for the specified
208 domains. E.g. level=KEEP and domains=PLATFORM:DEBUG will only
209 touch the platform domain.
212 <arg name="domains" type="s" direction="in">
214 A combination of logging domains separated by commas (','), or "NONE"
215 to disable logging. Each domain enables logging for operations
216 related to that domain. Available domains are: [PLATFORM, RFKILL, ETHER,
217 WIFI, BT, MB, DHCP4, DHCP6, PPP, WIFI_SCAN, IP4, IP6, AUTOIP4, DNS,
218 VPN, SHARING, SUPPLICANT, AGENTS, SETTINGS, SUSPEND, CORE, DEVICE,
219 OLPC, WIMAX, INFINIBAND, FIREWALL, ADSL, BOND, VLAN, BRIDGE, DBUS_PROPS,
220 TEAM, CONCHECK, DCB, DISPATCH, AUDIT].
221 In addition to these domains, the following special domains can be used:
222 [NONE, ALL, DEFAULT, DHCP, IP]. You can also specify that some domains
223 should log at a different level from the default by appending a colon (':')
224 and a log level (eg, 'WIFI:DEBUG'). If an empty string is given, the
225 log level is changed but the current set of log domains remains
231 <method name="GetLogging">
233 Get current logging verbosity level and operations domains.
235 <arg name="level" type="s" direction="out">
237 One of [ERR, WARN, INFO, DEBUG, TRACE].
240 <arg name="domains" type="s" direction="out">
242 For available domains see SetLogging() call.
247 <method name="CheckConnectivity">
249 Re-check the network connectivity state.
251 <arg name="connectivity" type="u" tp:type="NM_CONNECTIVITY" direction="out">
253 The current connectivity state.
258 <method name="state">
260 The overall networking state as determined by the NetworkManager daemon,
261 based on the state of network devices under it's management.
263 <arg name="state" type="u" direction="out" tp:type="NM_STATE"/>
266 <property name="Devices" type="ao" access="read">
268 The list of realized network devices. Realized devices are those which
269 have backing resources (eg from the kernel or a management daemon like
270 ModemManager, teamd, etc).
274 <property name="AllDevices" type="ao" access="read">
276 The list of both realized and un-realized network devices. Un-realized
277 devices are software devices which do not yet have backing resources,
278 but for which backing resources can be created if the device is
283 <property name="NetworkingEnabled" type="b" access="read">
285 Indicates if overall networking is currently enabled or not. See the
290 <property name="WirelessEnabled" type="b" access="readwrite">
292 Indicates if wireless is currently enabled or not.
296 <property name="WirelessHardwareEnabled" type="b" access="read">
298 Indicates if the wireless hardware is currently enabled, i.e. the state of the RF kill switch.
302 <property name="WwanEnabled" type="b" access="readwrite">
304 Indicates if mobile broadband devices are currently enabled or not.
308 <property name="WwanHardwareEnabled" type="b" access="read">
310 Indicates if the mobile broadband hardware is currently enabled, i.e. the state of the RF kill switch.
314 <property name="WimaxEnabled" type="b" access="readwrite">
316 Indicates if WiMAX devices are currently enabled or not.
320 <property name="WimaxHardwareEnabled" type="b" access="read">
322 Indicates if the WiMAX hardware is currently enabled, i.e. the state of the RF kill switch.
326 <property name="ActiveConnections" type="ao" access="read">
328 List of active connection object paths.
332 <property name="PrimaryConnection" type="o" access="read">
334 The object path of the "primary" active connection being used
335 to access the network. In particular, if there is no VPN
336 active, or the VPN does not have the default route, then this
337 indicates the connection that has the default route. If there
338 is a VPN active with the default route, then this indicates
339 the connection that contains the route to the VPN endpoint.
343 <property name="PrimaryConnectionType" type="s" access="read">
345 The connection type of the "primary" active connection being
346 used to access the network. This is the same as the Type
347 property on the object indicated by PrimaryConnection.
351 <property name="Metered" type="u" access="read" tp:type="NM_METERED">
353 Indicates whether the connectivity is metered. This is equivalent
354 to the metered property of the device associated with the primary
359 <property name="ActivatingConnection" type="o" access="read">
361 The object path of an active connection that is currently
362 being activated and which is expected to become the new
363 PrimaryConnection when it finishes activating.
367 <property name="Startup" type="b" access="read">
369 Indicates whether NM is still starting up; this becomes FALSE
370 when NM has finished attempting to activate every connection
371 that it might be able to activate at startup.
375 <property name="Version" type="s" access="read">
377 NetworkManager version.
381 <property name="State" type="u" access="read" tp:type="NM_STATE">
383 The overall state of the NetworkManager daemon.
387 <signal name="StateChanged">
389 NetworkManager's state changed.
391 <arg name="state" type="u" tp:type="NM_STATE">
393 The new state of NetworkManager.
398 <property name="Connectivity" type="u" access="read" tp:type="NM_CONNECTIVITY">
400 The network connectivity state.
404 <property name="GlobalDnsConfiguration" type="a{sv}" access="readwrite">
406 Dictionary of global DNS settings where the key is one of
407 "searches", "options" and "domains". The values for the
408 "searches" and "options" keys are string arrays describing the
409 list of search domains and resolver options, respectively.
410 The value of the "domains" key is a second-level dictionary,
411 where each key is a domain name, and each key's value is a
412 third-level dictionary with the keys "servers" and
413 "options". "servers" is a string array of DNS servers,
414 "options" is a string array of domain-specific options.
418 <signal name="PropertiesChanged">
420 NetworkManager's properties changed.
422 <arg name="properties" type="a{sv}" tp:type="String_Variant_Map">
424 The changed properties.
429 <signal name="DeviceAdded">
431 A device was added to the system
433 <arg name="device_path" type="o">
435 The object path of the newly added device.
440 <signal name="DeviceRemoved">
442 A device was removed from the system, and is no longer available.
444 <arg name="device_path" type="o">
446 The object path of the device that was just removed.
451 <tp:enum name="NM_STATE" type="u">
453 Describes the overall state of the daemon.
455 <tp:enumvalue suffix="UNKNOWN" value="0">
457 Networking state is unknown.
460 <tp:enumvalue suffix="ASLEEP" value="10">
462 Networking is inactive and all devices are disabled.
465 <tp:enumvalue suffix="DISCONNECTED" value="20">
467 There is no active network connection.
470 <tp:enumvalue suffix="DISCONNECTING" value="30">
472 Network connections are being cleaned up.
475 <tp:enumvalue suffix="CONNECTING" value="40">
477 A network device is connecting to a network and there is no other
478 available network connection.
481 <tp:enumvalue suffix="CONNECTED_LOCAL" value="50">
483 A network device is connected, but there is only link-local connectivity.
486 <tp:enumvalue suffix="CONNECTED_SITE" value="60">
488 A network device is connected, but there is only site-local connectivity.
491 <tp:enumvalue suffix="CONNECTED_GLOBAL" value="70">
493 A network device is connected, with global network connectivity.
498 <tp:enum name="NM_CONNECTIVITY" type="u">
500 Describes the network-connectivity state.
502 <tp:enumvalue suffix="UNKNOWN" value="0">
504 Network connectivity is unknown.
507 <tp:enumvalue suffix="NONE" value="1">
509 The host is not connected to any network.
512 <tp:enumvalue suffix="PORTAL" value="2">
514 The host is behind a captive portal and cannot reach the
518 <tp:enumvalue suffix="LIMITED" value="3">
520 The host is connected to a network, but does not appear to
521 be able to reach the full Internet.
524 <tp:enumvalue suffix="FULL" value="4">
526 The host is connected to a network, and appears to be able
527 to reach the full Internet