2005-12-06 23:37:09 +00:00
|
|
|
/* NetworkManager -- Network link manager
|
|
|
|
|
*
|
|
|
|
|
* Dan Williams <dcbw@redhat.com>
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
2008-06-26 18:31:52 +00:00
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
|
* 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
2005-12-06 23:37:09 +00:00
|
|
|
*
|
|
|
|
|
* (C) Copyright 2004 Red Hat, Inc.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef NETWORK_MANAGER_VPN_H
|
|
|
|
|
#define NETWORK_MANAGER_VPN_H
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* dbus services details
|
|
|
|
|
*/
|
2007-09-12 16:23:53 +00:00
|
|
|
#define NM_DBUS_PATH_VPN "/org/freedesktop/NetworkManager/VPN/Manager"
|
|
|
|
|
#define NM_DBUS_INTERFACE_VPN "org.freedesktop.NetworkManager.VPN.Manager"
|
2005-12-06 23:37:09 +00:00
|
|
|
|
2007-09-12 16:23:53 +00:00
|
|
|
#define NM_DBUS_PATH_VPN_CONNECTION "/org/freedesktop/NetworkManager/VPN/Connection"
|
|
|
|
|
#define NM_DBUS_INTERFACE_VPN_CONNECTION "org.freedesktop.NetworkManager.VPN.Connection"
|
|
|
|
|
|
|
|
|
|
#define NM_VPN_DBUS_PLUGIN_PATH "/org/freedesktop/NetworkManager/VPN/Plugin"
|
|
|
|
|
#define NM_VPN_DBUS_PLUGIN_INTERFACE "org.freedesktop.NetworkManager.VPN.Plugin"
|
2005-12-06 23:37:09 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* VPN Errors
|
|
|
|
|
*/
|
|
|
|
|
#define NM_DBUS_NO_ACTIVE_VPN_CONNECTION "org.freedesktop.NetworkManager.VPNConnections.NoActiveVPNConnection"
|
|
|
|
|
#define NM_DBUS_NO_VPN_CONNECTIONS "org.freedesktop.NetworkManager.VPNConnections.NoVPNConnections"
|
|
|
|
|
#define NM_DBUS_INVALID_VPN_CONNECTION "org.freedesktop.NetworkManager.VPNConnections.InvalidVPNConnection"
|
|
|
|
|
|
|
|
|
|
#define NM_DBUS_VPN_STARTING_IN_PROGRESS "StartingInProgress"
|
|
|
|
|
#define NM_DBUS_VPN_ALREADY_STARTED "AlreadyStarted"
|
|
|
|
|
#define NM_DBUS_VPN_STOPPING_IN_PROGRESS "StoppingInProgress"
|
|
|
|
|
#define NM_DBUS_VPN_ALREADY_STOPPED "AlreadyStopped"
|
|
|
|
|
#define NM_DBUS_VPN_WRONG_STATE "WrongState"
|
|
|
|
|
#define NM_DBUS_VPN_BAD_ARGUMENTS "BadArguments"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* VPN daemon signals
|
|
|
|
|
*/
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_LOGIN_BANNER "LoginBanner"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_LOGIN_FAILED "LoginFailed"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_LAUNCH_FAILED "LaunchFailed"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_CONNECT_FAILED "ConnectFailed"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_VPN_CONFIG_BAD "VPNConfigBad"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_IP_CONFIG_BAD "IPConfigBad"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_STATE_CHANGE "StateChange"
|
|
|
|
|
#define NM_DBUS_VPN_SIGNAL_IP4_CONFIG "IP4Config"
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* VPN daemon states
|
|
|
|
|
*/
|
2007-08-14 14:09:57 +00:00
|
|
|
typedef enum NMVPNServiceState
|
2005-12-06 23:37:09 +00:00
|
|
|
{
|
2007-08-14 14:09:57 +00:00
|
|
|
NM_VPN_SERVICE_STATE_UNKNOWN = 0,
|
|
|
|
|
NM_VPN_SERVICE_STATE_INIT,
|
|
|
|
|
NM_VPN_SERVICE_STATE_SHUTDOWN,
|
|
|
|
|
NM_VPN_SERVICE_STATE_STARTING,
|
|
|
|
|
NM_VPN_SERVICE_STATE_STARTED,
|
|
|
|
|
NM_VPN_SERVICE_STATE_STOPPING,
|
|
|
|
|
NM_VPN_SERVICE_STATE_STOPPED
|
|
|
|
|
} NMVPNServiceState;
|
2005-12-06 23:37:09 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
2007-08-14 14:09:57 +00:00
|
|
|
* VPN connection states
|
2005-12-06 23:37:09 +00:00
|
|
|
*/
|
2007-08-14 14:09:57 +00:00
|
|
|
typedef enum NMVPNConnectionState
|
2005-12-06 23:37:09 +00:00
|
|
|
{
|
2007-08-14 14:09:57 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_UNKNOWN = 0,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_PREPARE,
|
2007-09-27 02:28:54 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_NEED_AUTH,
|
2007-08-14 14:09:57 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_CONNECT,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_IP_CONFIG_GET,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_ACTIVATED,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_FAILED,
|
2008-05-13 16:57:01 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_DISCONNECTED
|
2007-08-14 14:09:57 +00:00
|
|
|
} NMVPNConnectionState;
|
2005-12-06 23:37:09 +00:00
|
|
|
|
2007-10-01 17:57:36 +00:00
|
|
|
typedef enum NMVPNConnectionStateReason
|
|
|
|
|
{
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_UNKNOWN = 0,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_NONE,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_USER_DISCONNECTED,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_SERVICE_STOPPED,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_IP_CONFIG_INVALID,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_CONNECT_TIMEOUT,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_TIMEOUT,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_SERVICE_START_FAILED,
|
2008-09-22 15:29:00 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_REASON_NO_SECRETS,
|
2008-10-11 19:57:45 +00:00
|
|
|
NM_VPN_CONNECTION_STATE_REASON_LOGIN_FAILED,
|
|
|
|
|
NM_VPN_CONNECTION_STATE_REASON_CONNECTION_REMOVED
|
2007-10-01 17:57:36 +00:00
|
|
|
} NMVPNConnectionStateReason;
|
2005-12-06 23:37:09 +00:00
|
|
|
|
2008-09-22 15:29:00 +00:00
|
|
|
typedef enum {
|
|
|
|
|
NM_VPN_PLUGIN_FAILURE_LOGIN_FAILED,
|
|
|
|
|
NM_VPN_PLUGIN_FAILURE_CONNECT_FAILED,
|
|
|
|
|
NM_VPN_PLUGIN_FAILURE_BAD_IP_CONFIG
|
|
|
|
|
} NMVPNPluginFailure;
|
|
|
|
|
|
2008-10-11 14:26:41 +00:00
|
|
|
|
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
|
|
|
/*** Generic config ***/
|
|
|
|
|
|
|
|
|
|
/* string: VPN interface name (tun0, tap0, etc) */
|
|
|
|
|
#define NM_VPN_PLUGIN_CONFIG_TUNDEV "tundev"
|
|
|
|
|
|
|
|
|
|
/* string: Login message */
|
|
|
|
|
#define NM_VPN_PLUGIN_CONFIG_BANNER "banner"
|
|
|
|
|
|
2012-05-23 12:04:17 -04:00
|
|
|
/* uint32 / array of uint8: IP address of the public external VPN gateway (network byte order) */
|
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
|
|
|
#define NM_VPN_PLUGIN_CONFIG_EXT_GATEWAY "gateway"
|
|
|
|
|
|
|
|
|
|
/* uint32: Maximum Transfer Unit that the VPN interface should use */
|
|
|
|
|
#define NM_VPN_PLUGIN_CONFIG_MTU "mtu"
|
|
|
|
|
|
|
|
|
|
/* boolean: Has IP4 configuration? */
|
|
|
|
|
#define NM_VPN_PLUGIN_CONFIG_HAS_IP4 "has-ip4"
|
|
|
|
|
|
|
|
|
|
/* boolean: Has IP6 configuration? */
|
|
|
|
|
#define NM_VPN_PLUGIN_CONFIG_HAS_IP6 "has-ip6"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*** Ip4Config ***/
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* uint32: IP address of the internal gateway of the subnet the VPN interface is
|
2009-08-13 17:01:06 -05:00
|
|
|
* on, if the VPN uses subnet configuration (network byte order)
|
2009-08-13 16:56:44 -05:00
|
|
|
*/
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_INT_GATEWAY "internal-gateway"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
2009-08-13 17:01:06 -05:00
|
|
|
/* uint32: internal IP address of the local VPN interface (network byte order) */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_ADDRESS "address"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* uint32: IP address of the other side of Point-to-Point connection if the VPN
|
|
|
|
|
* uses Point-to-Point configuration. (network byte order)
|
|
|
|
|
*/
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_PTP "ptp"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* uint32: IP prefix of the VPN interface; 1 - 32 inclusive */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_PREFIX "prefix"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* array of uint32: IP addresses of DNS servers for the VPN (network byte order) */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_DNS "dns"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* array of uint32: IP addresses of NBNS/WINS servers for the VPN (network byte order) */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_NBNS "nbns"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* uint32: Message Segment Size that the VPN interface should use */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_MSS "mss"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
|
|
|
|
/* string: DNS domain name */
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_DOMAIN "domain"
|
2009-08-13 16:56:44 -05:00
|
|
|
|
2012-03-15 14:56:26 -07:00
|
|
|
/* array of strings: DNS domain names */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_DOMAINS "domains"
|
|
|
|
|
|
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
|
|
|
/* [ip4 routes]: custom routes the client should apply, in the format used
|
|
|
|
|
* by nm_utils_ip4_routes_to/from_gvalue
|
2009-08-13 16:56:44 -05:00
|
|
|
*/
|
2008-10-11 14:26:41 +00:00
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_ROUTES "routes"
|
|
|
|
|
|
2010-08-12 23:52:17 -05:00
|
|
|
/* boolean: prevent this VPN connection from ever getting the default route */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_NEVER_DEFAULT "never-default"
|
|
|
|
|
|
2008-10-11 14:26:41 +00:00
|
|
|
/* Deprecated */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_GATEWAY NM_VPN_PLUGIN_IP4_CONFIG_EXT_GATEWAY
|
|
|
|
|
|
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
|
|
|
/* Legacy IP4 items; these are included in the IP4 config by older plugins,
|
|
|
|
|
* but in the generic config by newer plugins.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_BANNER NM_VPN_PLUGIN_CONFIG_BANNER
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_EXT_GATEWAY NM_VPN_PLUGIN_CONFIG_EXT_GATEWAY
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_MTU NM_VPN_PLUGIN_CONFIG_MTU
|
|
|
|
|
#define NM_VPN_PLUGIN_IP4_CONFIG_TUNDEV NM_VPN_PLUGIN_CONFIG_TUNDEV
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*** Ip6Config ***/
|
|
|
|
|
|
|
|
|
|
/* array of uint8: IP address of the internal gateway of the subnet the VPN interface is
|
|
|
|
|
* on, if the VPN uses subnet configuration (network byte order)
|
|
|
|
|
*/
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_INT_GATEWAY "internal-gateway"
|
|
|
|
|
|
|
|
|
|
/* array of uint8: internal IP address of the local VPN interface (network byte order) */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_ADDRESS "address"
|
|
|
|
|
|
|
|
|
|
/* array of uint8: IP address of the other side of Point-to-Point connection if the VPN
|
|
|
|
|
* uses Point-to-Point configuration. (network byte order)
|
|
|
|
|
*/
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_PTP "ptp"
|
|
|
|
|
|
|
|
|
|
/* uint32: prefix length of the VPN interface; 1 - 128 inclusive */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_PREFIX "prefix"
|
|
|
|
|
|
|
|
|
|
/* array of array of uint8: IP addresses of DNS servers for the VPN (network byte order) */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_DNS "dns"
|
|
|
|
|
|
|
|
|
|
/* uint32: Message Segment Size that the VPN interface should use */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_MSS "mss"
|
|
|
|
|
|
|
|
|
|
/* string: DNS domain name */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_DOMAIN "domain"
|
|
|
|
|
|
|
|
|
|
/* array of strings: DNS domain names */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_DOMAINS "domains"
|
|
|
|
|
|
|
|
|
|
/* [ip6 routes]: custom routes the client should apply, in the format used
|
|
|
|
|
* by nm_utils_ip6_routes_to/from_gvalue
|
|
|
|
|
*/
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_ROUTES "routes"
|
|
|
|
|
|
|
|
|
|
/* boolean: prevent this VPN connection from ever getting the default route */
|
|
|
|
|
#define NM_VPN_PLUGIN_IP6_CONFIG_NEVER_DEFAULT "never-default"
|
2007-09-12 16:23:53 +00:00
|
|
|
|
2005-12-06 23:37:09 +00:00
|
|
|
#endif /* NETWORK_MANAGER_VPN_H */
|
