fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-21 15:40:06 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/dispatcher/nm-dispatcher-utils.h

29 lines
1.2 KiB
C
Raw Normal View History

all: SPDX header conversion $ find * -type f |xargs perl contrib/scripts/spdx.pl $ git rm contrib/scripts/spdx.pl
2019-09-10 11:19:01 +02:00
// SPDX-License-Identifier: GPL-2.0+
all: manually drop code comments with file description
2019-09-25 13:13:40 +02:00
/*
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
* Copyright (C) 2008 - 2011 Red Hat, Inc.
*/
all: fix up multiple-include-guard defines Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include guard, which meant that nm-test-utils.h could not tell which of them was being included (and so, eg, if you tried to include nm-ip4-config.h in a libnm test, it would fail to compile because nm-test-utils.h was referring to symbols in src/nm-ip4-config.h). Fix this by changing the include guards in the non-API-stable parts of the tree: - libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H - libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__ - src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__ And likewise for all other headers. The two non-"nm"-prefixed headers, libnm/NetworkManager.h and src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and __NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely consistent with the general scheme, do still mostly make sense in isolation.
2014-08-13 14:10:11 -04:00
#ifndef __NETWORKMANAGER_DISPATCHER_UTILS_H__
#define __NETWORKMANAGER_DISPATCHER_UTILS_H__
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
char **
nm_dispatcher_utils_construct_envp (const char *action,
dispatcher: port to GDBus Port nm-dispatcher to GDBus, mostly, using dbus-glib's GVariant utilities to translate the return value of nm_connection_to_dbus().
2014-09-03 12:27:33 -04:00
GVariant *connection_dict,
GVariant *connection_props,
GVariant *device_props,
callouts: Fixes in Dispatcher to release Proxy env variables Dispatcher Fixed to release env variables for proxy stuff. For VPNs proxy variables have prefix "VPN_" as usual.
2016-08-16 05:55:59 +05:30
GVariant *device_proxy_props,
dispatcher: port to GDBus Port nm-dispatcher to GDBus, mostly, using dbus-glib's GVariant utilities to translate the return value of nm_connection_to_dbus().
2014-09-03 12:27:33 -04:00
GVariant *device_ip4_props,
GVariant *device_ip6_props,
GVariant *device_dhcp4_props,
GVariant *device_dhcp6_props,
nm-dispatcher: Handle the 'connectivity-state' parameter for 'Action' Actually handle this new parameter in the nm-dispatcher process, setting the value of a new CONNECTIVITY_STATE environment variable accordingly. This patch also includes new tests to check the different cases. https://bugzilla.gnome.org/show_bug.cgi?id=768969
2016-07-20 16:24:41 +01:00
const char *connectivity_state,
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
const char *vpn_ip_iface,
callouts: Fixes in Dispatcher to release Proxy env variables Dispatcher Fixed to release env variables for proxy stuff. For VPNs proxy variables have prefix "VPN_" as usual.
2016-08-16 05:55:59 +05:30
GVariant *vpn_proxy_props,
dispatcher: port to GDBus Port nm-dispatcher to GDBus, mostly, using dbus-glib's GVariant utilities to translate the return value of nm_connection_to_dbus().
2014-09-03 12:27:33 -04:00
GVariant *vpn_ip4_props,
GVariant *vpn_ip6_props,
dispatcher: return error reason from nm_dispatcher_utils_construct_envp() Also, error out in handle_action() when nm_dispatcher_utils_construct_envp() indicates a failure.
2015-08-04 10:51:32 +02:00
char **out_iface,
const char **out_error_message);
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
all: fix up multiple-include-guard defines Previously, src/nm-ip4-config.h, libnm/nm-ip4-config.h, and libnm-glib/nm-ip4-config.h all used "NM_IP4_CONFIG_H" as an include guard, which meant that nm-test-utils.h could not tell which of them was being included (and so, eg, if you tried to include nm-ip4-config.h in a libnm test, it would fail to compile because nm-test-utils.h was referring to symbols in src/nm-ip4-config.h). Fix this by changing the include guards in the non-API-stable parts of the tree: - libnm-glib/nm-ip4-config.h remains NM_IP4_CONFIG_H - libnm/nm-ip4-config.h now uses __NM_IP4_CONFIG_H__ - src/nm-ip4-config.h now uses __NETWORKMANAGER_IP4_CONFIG_H__ And likewise for all other headers. The two non-"nm"-prefixed headers, libnm/NetworkManager.h and src/NetworkManagerUtils.h are now __NETWORKMANAGER_H__ and __NETWORKMANAGER_UTILS_H__ respectively, which, while not entirely consistent with the general scheme, do still mostly make sense in isolation.
2014-08-13 14:10:11 -04:00
#endif /* __NETWORKMANAGER_DISPATCHER_UTILS_H__ */
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
Reference in a new issue Copy permalink