| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
There's no reason the dispatcher test files should have "old" in their
names, since they're testing the current dispatcher interface.
(cherry picked from commit 9cfd9d376fd5fd2fef097293e6f851044068c6d1)
|
| |
|
|
| |
(cherry picked from commit bd2deace7081dc1327e7bb6ab416d49da4ae79ce)
|
| |
|
|
|
|
| |
These tests were broken by commit 45ed459ae32976a120f607046021b48bf728c1d6.
Signed-off-by: Thomas Haller <thaller@redhat.com>
|
| |
|
|
|
| |
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.
|
|
|
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.
|
