2007-09-12 16:23:53 +00:00
|
|
|
<?xml version="1.0" encoding="UTF-8" ?>
|
|
|
|
|
|
2008-02-28 02:07:21 +00:00
|
|
|
<node name="/" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
|
2007-09-12 16:23:53 +00:00
|
|
|
<interface name="org.freedesktop.NetworkManager.VPN.Plugin">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
This interface is provided by plugins providing VPN services to the NetworkManager daemon.
|
|
|
|
|
</tp:docstring>
|
2013-06-18 09:32:53 -05:00
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
<method name="Connect">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
2013-06-18 09:32:53 -05:00
|
|
|
Tells the plugin to connect. Interactive secrets requests (eg, emitting
|
|
|
|
|
the SecretsRequired signal) are not allowed.
|
2008-02-28 02:07:21 +00:00
|
|
|
</tp:docstring>
|
2007-09-12 16:23:53 +00:00
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_connect"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
<arg name="connection" type="a{sa{sv}}" direction="in" tp:type="String_String_Variant_Map_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Describes the connection to be established.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<tp:possible-errors>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.StartingInProgress"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.AlreadyStarted"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.StoppingInProgress"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.BadArguments"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.LaunchFailed"/>
|
2013-06-18 09:32:53 -05:00
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.WrongState"/>
|
|
|
|
|
</tp:possible-errors>
|
|
|
|
|
</method>
|
|
|
|
|
|
|
|
|
|
<method name="ConnectInteractive">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Tells the plugin to connect, allowing interactive secrets requests (eg
|
|
|
|
|
the plugin is allowed to emit the SecretsRequired signal if the VPN
|
|
|
|
|
service indicates that it needs additional secrets during the connect
|
|
|
|
|
process).
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_connect_interactive"/>
|
|
|
|
|
<arg name="connection" type="a{sa{sv}}" direction="in" tp:type="String_String_Variant_Map_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Describes the connection to be established.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<arg name="details" type="a{sv}" direction="in" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Additional details about the Connect process.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<tp:possible-errors>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.StartingInProgress"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.AlreadyStarted"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.StoppingInProgress"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.BadArguments"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.LaunchFailed"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.WrongState"/>
|
2013-09-26 10:19:33 +02:00
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.InteractiveNotSupported"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
</tp:possible-errors>
|
2007-09-12 16:23:53 +00:00
|
|
|
</method>
|
|
|
|
|
|
2007-09-27 02:20:53 +00:00
|
|
|
<method name="NeedSecrets">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Asks the plugin whether the provided connection will require secrets to connect successfully.
|
|
|
|
|
</tp:docstring>
|
2007-09-27 02:20:53 +00:00
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_need_secrets"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
<arg name="settings" type="a{sa{sv}}" direction="in" tp:type="String_String_Variant_Map_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Describes the connection that may need secrets.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<arg name="setting_name" type="s" direction="out">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The setting name within the provided connection that requires secrets, if any.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<tp:possible-errors>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.ConnectionInvalid"/>
|
|
|
|
|
</tp:possible-errors>
|
2007-09-27 02:20:53 +00:00
|
|
|
</method>
|
|
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
<method name="Disconnect">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Disconnect the plugin.
|
|
|
|
|
</tp:docstring>
|
2007-09-12 16:23:53 +00:00
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_disconnect"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:possible-errors>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.StoppingInProgress"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.AlreadyStopped"/>
|
|
|
|
|
</tp:possible-errors>
|
2007-09-12 16:23:53 +00:00
|
|
|
</method>
|
|
|
|
|
|
vpn: support IPv6 over VPNs
Add new API to allow passing both IPv4 and IPv6 configuration
information from VPN plugins to the backend.
Now instead of a single Ip4Config, a plugin has Config, Ip4Config, and
Ip6Config. "Config" contains information which is neither IPv4 nor
IPv6 specific, and also indicates which of Ip4Config and Ip6Config are
present. Ip4Config now only contains the IPv4-specific bits of
configuration.
There is backward compatibility in both directions: if the daemon is
new and the VPN plugin is old, then NM will notice that the plugin
emitted the Ip4Config signal without having emitted the Config signal
first, and so will assume that it is IPv4-only, and that the generic
bits of configuration have been included with the Ip4Config. If the
daemon is old and the plugin is new, then NMVPNPlugin will copy the
values from the generic config into the IPv4 config as well. (In fact,
NMVPNPlugin *always* does this, because it's harmless, and it's easier
than actually checking the daemon version.)
Currently the VPN is still configured all-at-once, after both IPv4 and
IPv6 information has been received, but the APIs allow for the
possibility of configuring them one at a time in the future.
2012-05-04 15:50:07 -04:00
|
|
|
<method name="SetConfig">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Set generic connection details on the connection.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_set_config"/>
|
|
|
|
|
<arg name="config" type="a{sv}" direction="in" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Generic configuration details for the connection.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
</method>
|
|
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
<method name="SetIp4Config">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Set IPv4 details on the connection.
|
|
|
|
|
</tp:docstring>
|
2007-09-12 16:23:53 +00:00
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_set_ip4_config"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
<arg name="config" type="a{sv}" direction="in" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
vpn: support IPv6 over VPNs
Add new API to allow passing both IPv4 and IPv6 configuration
information from VPN plugins to the backend.
Now instead of a single Ip4Config, a plugin has Config, Ip4Config, and
Ip6Config. "Config" contains information which is neither IPv4 nor
IPv6 specific, and also indicates which of Ip4Config and Ip6Config are
present. Ip4Config now only contains the IPv4-specific bits of
configuration.
There is backward compatibility in both directions: if the daemon is
new and the VPN plugin is old, then NM will notice that the plugin
emitted the Ip4Config signal without having emitted the Config signal
first, and so will assume that it is IPv4-only, and that the generic
bits of configuration have been included with the Ip4Config. If the
daemon is old and the plugin is new, then NMVPNPlugin will copy the
values from the generic config into the IPv4 config as well. (In fact,
NMVPNPlugin *always* does this, because it's harmless, and it's easier
than actually checking the daemon version.)
Currently the VPN is still configured all-at-once, after both IPv4 and
IPv6 information has been received, but the APIs allow for the
possibility of configuring them one at a time in the future.
2012-05-04 15:50:07 -04:00
|
|
|
Ip4Config details for the connection. You must call
|
|
|
|
|
SetConfig() before calling this.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
</method>
|
|
|
|
|
|
|
|
|
|
<method name="SetIp6Config">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Set IPv6 details on the connection.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_set_ip6_config"/>
|
|
|
|
|
<arg name="config" type="a{sv}" direction="in" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Ip6Config details for the connection. You must call
|
|
|
|
|
SetConfig() before calling this.
|
2008-02-28 02:07:21 +00:00
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</method>
|
|
|
|
|
|
|
|
|
|
<method name="SetFailure">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Indicate a failure to the plugin.
|
|
|
|
|
</tp:docstring>
|
2007-09-12 16:23:53 +00:00
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_set_failure"/>
|
2008-02-28 02:07:21 +00:00
|
|
|
<arg name="reason" type="s" direction="in">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The reason for the failure.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</method>
|
|
|
|
|
|
2014-07-07 09:35:07 -04:00
|
|
|
<property name="State" type="u" access="read" tp:type="NM_VPN_SERVICE_STATE">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
The state of the plugin.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</property>
|
2007-09-12 16:23:53 +00:00
|
|
|
|
|
|
|
|
<signal name="StateChanged">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Emitted when the plugin state changes.
|
|
|
|
|
</tp:docstring>
|
2014-07-07 09:35:07 -04:00
|
|
|
<arg name="state" type="u" tp:type="NM_VPN_SERVICE_STATE">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
The new state of the plugin.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</signal>
|
|
|
|
|
|
2013-06-18 09:32:53 -05:00
|
|
|
<signal name="SecretsRequired">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Emitted during an ongoing ConnectInteractive() request when the plugin
|
|
|
|
|
has determined that new secrets are required. NetworkManager will then
|
|
|
|
|
call the NewSecrets() method with a connection hash including the new
|
|
|
|
|
secrets.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<arg name="message" type="s" direction="out">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Informational message, if any, about the request. For example, if
|
|
|
|
|
a second PIN is required, could indicate to the user to wait for
|
|
|
|
|
the token code to change until entering the next PIN.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<arg name="secrets" type="as" direction="out">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Array of strings of VPN secret names which the plugin thinks
|
|
|
|
|
secrets may be required for, or other VPN-specific data to be
|
|
|
|
|
processed by the VPN's front-end.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
</signal>
|
|
|
|
|
|
|
|
|
|
<method name="NewSecrets">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Called in response to a SecretsRequired signal to deliver updated secrets
|
|
|
|
|
or other information to the plugin.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_vpn_plugin_new_secrets"/>
|
|
|
|
|
<arg name="connection" type="a{sa{sv}}" direction="in" tp:type="String_String_Variant_Map_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Describes the connection including the new secrets.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
<tp:possible-errors>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.WrongState"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.BadArguments"/>
|
|
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.LaunchFailed"/>
|
2013-09-26 10:19:33 +02:00
|
|
|
<tp:error name="org.freedesktop.NetworkManager.VPN.Error.InteractiveNotSupported"/>
|
2013-06-18 09:32:53 -05:00
|
|
|
</tp:possible-errors>
|
|
|
|
|
</method>
|
|
|
|
|
|
vpn: support IPv6 over VPNs
Add new API to allow passing both IPv4 and IPv6 configuration
information from VPN plugins to the backend.
Now instead of a single Ip4Config, a plugin has Config, Ip4Config, and
Ip6Config. "Config" contains information which is neither IPv4 nor
IPv6 specific, and also indicates which of Ip4Config and Ip6Config are
present. Ip4Config now only contains the IPv4-specific bits of
configuration.
There is backward compatibility in both directions: if the daemon is
new and the VPN plugin is old, then NM will notice that the plugin
emitted the Ip4Config signal without having emitted the Config signal
first, and so will assume that it is IPv4-only, and that the generic
bits of configuration have been included with the Ip4Config. If the
daemon is old and the plugin is new, then NMVPNPlugin will copy the
values from the generic config into the IPv4 config as well. (In fact,
NMVPNPlugin *always* does this, because it's harmless, and it's easier
than actually checking the daemon version.)
Currently the VPN is still configured all-at-once, after both IPv4 and
IPv6 information has been received, but the APIs allow for the
possibility of configuring them one at a time in the future.
2012-05-04 15:50:07 -04:00
|
|
|
<signal name="Config">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin obtained generic configuration information.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<arg name="config" type="a{sv}" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The configuration information.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
</signal>
|
|
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
<signal name="Ip4Config">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin obtained an IPv4 configuration.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<arg name="ip4config" type="a{sv}" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The IPv4 configuration.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</signal>
|
|
|
|
|
|
vpn: support IPv6 over VPNs
Add new API to allow passing both IPv4 and IPv6 configuration
information from VPN plugins to the backend.
Now instead of a single Ip4Config, a plugin has Config, Ip4Config, and
Ip6Config. "Config" contains information which is neither IPv4 nor
IPv6 specific, and also indicates which of Ip4Config and Ip6Config are
present. Ip4Config now only contains the IPv4-specific bits of
configuration.
There is backward compatibility in both directions: if the daemon is
new and the VPN plugin is old, then NM will notice that the plugin
emitted the Ip4Config signal without having emitted the Config signal
first, and so will assume that it is IPv4-only, and that the generic
bits of configuration have been included with the Ip4Config. If the
daemon is old and the plugin is new, then NMVPNPlugin will copy the
values from the generic config into the IPv4 config as well. (In fact,
NMVPNPlugin *always* does this, because it's harmless, and it's easier
than actually checking the daemon version.)
Currently the VPN is still configured all-at-once, after both IPv4 and
IPv6 information has been received, but the APIs allow for the
possibility of configuring them one at a time in the future.
2012-05-04 15:50:07 -04:00
|
|
|
<signal name="Ip6Config">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin obtained an IPv6 configuration.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<arg name="ip6config" type="a{sv}" tp:type="String_Variant_Map">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The IPv6 configuration.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
|
|
|
|
</signal>
|
|
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
<signal name="LoginBanner">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Emitted when the plugin receives a login banner from the VPN service.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
<arg name="banner" type="s">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The login banner string.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</signal>
|
|
|
|
|
|
|
|
|
|
<signal name="Failure">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Emitted when a failure in the VPN plugin occurs.
|
|
|
|
|
</tp:docstring>
|
2008-09-22 15:29:00 +00:00
|
|
|
<arg name="reason" type="u" tp:type="NM_VPN_PLUGIN_FAILURE">
|
2008-02-28 02:07:21 +00:00
|
|
|
<tp:docstring>
|
|
|
|
|
Reason code for the failure.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</arg>
|
2007-09-12 16:23:53 +00:00
|
|
|
</signal>
|
2008-09-22 15:29:00 +00:00
|
|
|
|
2014-07-07 09:35:07 -04:00
|
|
|
<tp:enum name="NM_VPN_SERVICE_STATE" type="u">
|
|
|
|
|
<tp:enumvalue suffix="UNKNOWN" value="0">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The state of the VPN plugin is unknown.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="INIT" value="1">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The VPN plugin is initialized.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="SHUTDOWN" value="2">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
(Not used.)
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="STARTING" value="3">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin is attempting to connect to a VPN server.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="STARTED" value="4">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin has connected to a VPN server.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="STOPPING" value="5">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin is disconnecting from the VPN server.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="STOPPED" value="6">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
The plugin has disconnected from the VPN server.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
</tp:enum>
|
|
|
|
|
|
2008-09-22 15:29:00 +00:00
|
|
|
<tp:enum name="NM_VPN_PLUGIN_FAILURE" type="u">
|
|
|
|
|
<tp:enumvalue suffix="LOGIN_FAILED" value="0">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Login failed.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="CONNECT_FAILED" value="1">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Connect failed.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
<tp:enumvalue suffix="BAD_IP_CONFIG" value="2">
|
|
|
|
|
<tp:docstring>
|
|
|
|
|
Invalid IP configuration returned from the VPN plugin.
|
|
|
|
|
</tp:docstring>
|
|
|
|
|
</tp:enumvalue>
|
|
|
|
|
</tp:enum>
|
|
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
</interface>
|
|
|
|
|
</node>
|
