From 70e18d99b8e3e77bb37e218d7ac582130156f8ef Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 25 Jan 2024 09:46:18 +0100 Subject: New upstream version 1.45.90 --- docs/api/html/NetworkManager-dispatcher.html | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) (limited to 'docs/api/html/NetworkManager-dispatcher.html') diff --git a/docs/api/html/NetworkManager-dispatcher.html b/docs/api/html/NetworkManager-dispatcher.html index 88ed3634..b8ef62c3 100644 --- a/docs/api/html/NetworkManager-dispatcher.html +++ b/docs/api/html/NetworkManager-dispatcher.html @@ -51,8 +51,9 @@ device an operation just happened on, and second the action. For device actions, the interface is the name of the kernel interface suitable for IP configuration. Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable. - For the hostname action the device name is always "none" - and for connectivity-change it is empty. + For the hostname action the device name is always + "none". For connectivity-change and + dns-change it is empty.

The actions are:

@@ -158,6 +159,16 @@ The connection was reapplied on the device.

+ + + +

dns-change

+ The DNS configuration has changed. This action is raised even if + NetworkManager is configured to not manage resolv.conf (for example, + via dns=none). In such case, the dispatch script can discover the + DNS configuration provided by currently active connections by + looking at file /run/NetworkManager/resolv.conf +

-- cgit 1.3.0-6-gf8a5