fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-22 16:10:08 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/callouts/tests/dispatcher-down

23 lines
470 B
Text
Raw Normal View History

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
[main]
action=down
core: fix dispatcher handling of empty VPN interface (bgo #649773) We pass a VPN IP iface of "" through D-Bus (since dbus doesn't do NULL) and the dispatcher code wasn't ignoring that as it should have been.
2011-05-10 11:33:43 -05:00
expected-iface=wlan0
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
uuid=3fd2a33a-d81b-423f-ae99-e6baba742311
id=Random Connection
[device]
state=30
ip-interface=wlan0
type=2
interface=wlan0
path=/org/freedesktop/NetworkManager/Devices/0
[env]
dispatcher/test: fix tests after adding PATH environment variable These tests were broken by commit 45ed459ae32976a120f607046021b48bf728c1d6. Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-04-22 12:19:29 +02:00
PATH=
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
CONNECTION_UUID=3fd2a33a-d81b-423f-ae99-e6baba742311
dispatcher: expose connection D-Bus path src/nm-dispatcher.c was passing the connection's D-Bus path to the dispatcher, which was then ignoring it. Meanwhile, test-dispatcher-envp was passing a fake D-Bus path with the wrong name (which didn't actually matter since nm_dispatcher_utils_construct_envp() ignored it anyway). Fix it so that the path gets exposed as CONNECTION_DBUS_PATH, and adjust the tests for that.
2014-12-18 09:06:56 -05:00
CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Connections/5
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
CONNECTION_ID=Random Connection
dispatcher: remove "old" from the test names There's no reason the dispatcher test files should have "old" in their names, since they're testing the current dispatcher interface.
2014-12-18 08:35:58 -05:00
CONNECTION_FILENAME=/callouts/tests/dispatcher-down
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
DEVICE_IFACE=wlan0
DEVICE_IP_IFACE=wlan0
Reference in a new issue Copy permalink