← Back to branch summary

~ubuntu-branches/ubuntu/lucid/knetworkmanager/lucid

« back to all changes in this revision

Viewing changes to knetworkmanager-0.7/introspection/nm-device.xml

  • Committer: Bazaar Package Importer
  • Author(s): Jonathan Riddell
  • Date: 2008-09-26 12:40:26 UTC
  • mfrom: (1.2.7 upstream)
  • Revision ID: james.westby@ubuntu.com-20080926124026-t5fr920l4lf2l6hz
Tags: 1:0.7svn864988-0ubuntu1
https://launchpad.net/bugs/259278
New upstream snapshot, now works with current NM API, 
closes LP: #259278

Show diffs side-by-side

added added

removed removed

Lines of Context:
knetworkmanager-0.7/introspection/nm-device.xml
 
1
<?xml version="1.0" encoding="UTF-8" ?>
 
2
 
 
3
<node name="/" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
 
4
  <interface name="org.freedesktop.NetworkManager.Device">
 
5
    <property name="Udi" type="s" access="read">
 
6
      <tp:docstring>
 
7
        HAL UDI for the device.
 
8
      </tp:docstring>
 
9
    </property>
 
10
    <property name="Interface" type="s" access="read">
 
11
      <tp:docstring>
 
12
        The network interface offered by the device.
 
13
      </tp:docstring>
 
14
    </property>
 
15
    <property name="Driver" type="s" access="read">
 
16
      <tp:docstring>
 
17
        The driver handling the device.
 
18
      </tp:docstring>
 
19
    </property>
 
20
    <property name="Capabilities" type="u" access="read" tp:type="NM_DEVICE_CAP">
 
21
      <tp:docstring>
 
22
        Flags describing the capabilities of the device.
 
23
      </tp:docstring>
 
24
    </property>
 
25
    <property name="Ip4Address" type="i" access="read">
 
26
      <tp:docstring>
 
27
        The IPv4 address bound to the device. FIXME: what about devices with >1 IP address?
 
28
      </tp:docstring>
 
29
    </property>
 
30
    <property name="State" type="u" access="read" tp:type="NM_DEVICE_STATE">
 
31
      <tp:docstring>
 
32
        The current state of the device.
 
33
      </tp:docstring>
 
34
    </property>
 
35
    <property name="Ip4Config" type="o" access="read">
 
36
      <tp:docstring>
 
37
        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.
 
38
      </tp:docstring>
 
39
    </property>
 
40
    <property name="Managed" type="b" access="read">
 
41
      <tp:docstring>
 
42
        Whether or not this device is managed by NetworkManager.
 
43
      </tp:docstring>
 
44
    </property>
 
45
 
 
46
    <!-- Ugh, but I see no other way of getting the type on the caller
 
47
    based on dbus object path only -->
 
48
    <property name="DeviceType" type="u" access="read">
 
49
      <tp:docstring>
 
50
      </tp:docstring>
 
51
    </property>
 
52
 
 
53
 
 
54
    <signal name="StateChanged">
 
55
      <arg name="state" type="u" tp:type="NM_DEVICE_STATE">
 
56
        <tp:docstring>
 
57
          The new state of the device.
 
58
        </tp:docstring>
 
59
      </arg>
 
60
    </signal>
 
61
 
 
62
    <tp:enum name="NM_DEVICE_STATE" type="u">
 
63
      <tp:enumvalue suffix="UNKNOWN" value="0">
 
64
        <tp:docstring>
 
65
          The device is in an unknown state.
 
66
        </tp:docstring>
 
67
      </tp:enumvalue>
 
68
      <tp:enumvalue suffix="DOWN" value="1">
 
69
        <tp:docstring>
 
70
          The device is down.
 
71
        </tp:docstring>
 
72
      </tp:enumvalue>
 
73
      <tp:enumvalue suffix="DISCONNECTED" value="2">
 
74
        <tp:docstring>
 
75
          The device is not connected.
 
76
        </tp:docstring>
 
77
      </tp:enumvalue>
 
78
      <tp:enumvalue suffix="PREPARE" value="3">
 
79
        <tp:docstring>
 
80
          The device is preparing to connect.
 
81
        </tp:docstring>
 
82
      </tp:enumvalue>
 
83
      <tp:enumvalue suffix="CONFIG" value="4">
 
84
        <tp:docstring>
 
85
          The device is being configured.
 
86
        </tp:docstring>
 
87
      </tp:enumvalue>
 
88
      <tp:enumvalue suffix="NEED_AUTH" value="5">
 
89
        <tp:docstring>
 
90
          The device is awaiting authorization credentials.
 
91
        </tp:docstring>
 
92
      </tp:enumvalue>
 
93
      <tp:enumvalue suffix="IP_CONFIG" value="6">
 
94
        <tp:docstring>
 
95
          The IP address of the device is being configured.
 
96
        </tp:docstring>
 
97
      </tp:enumvalue>
 
98
      <tp:enumvalue suffix="ACTIVATED" value="7">
 
99
        <tp:docstring>
 
100
          The device is active.
 
101
        </tp:docstring>
 
102
      </tp:enumvalue>
 
103
      <tp:enumvalue suffix="FAILED" value="8">
 
104
        <tp:docstring>
 
105
          The device is in a failure state following an attempt to activate it.
 
106
        </tp:docstring>
 
107
      </tp:enumvalue>
 
108
      <tp:enumvalue suffix="CANCELLED" value="9">
 
109
        <tp:docstring>
 
110
          The previous activation attempt on this device was cancelled.
 
111
        </tp:docstring>
 
112
      </tp:enumvalue>
 
113
    </tp:enum>
 
114
    <tp:flags name="NM_DEVICE_CAP" value-prefix="NM_DEVICE_CAP" type="u">
 
115
      <tp:flag suffix="NONE" value="0x0">
 
116
        <tp:docstring>Null capability.</tp:docstring>
 
117
      </tp:flag>
 
118
      <tp:flag suffix="NM_SUPPORTED" value="0x1">
 
119
        <tp:docstring>The device is supported by NetworkManager.</tp:docstring>
 
120
      </tp:flag>
 
121
      <tp:flag suffix="CARRIER_DETECT" value="0x2">
 
122
        <tp:docstring>The device supports carrier detection.</tp:docstring>
 
123
      </tp:flag>
 
124
    </tp:flags>
 
125
  </interface>
 
126
</node>