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.html | 40 ++++++++++++++++++++++++++++++++++++--- 1 file changed, 37 insertions(+), 3 deletions(-) (limited to 'docs/api/html/NetworkManager.html') diff --git a/docs/api/html/NetworkManager.html b/docs/api/html/NetworkManager.html index 678e9f1c..4f2bcb04 100644 --- a/docs/api/html/NetworkManager.html +++ b/docs/api/html/NetworkManager.html @@ -177,7 +177,8 @@ - + +

NM_UNMANAGED

If set to "1" or "true", the device is @@ -186,7 +187,40 @@ nmcli device set "$DEVICE" managed yes or "device*.managed=1" in NetworkManager.conf.

- + + +

ID_NET_MANAGED_BY

+

+ If NM_UNMANAGED is set, this has no effect. Otherwise, + if the attribute is set to anything but + "org.freedesktop.NetworkManager", the device is unmanaged. +

+ + +

NM_AUTO_DEFAULT_LINK_LOCAL_ONLY

+

+ If set to "1" or "true", the + automatically generated connections "Wired connection N" will only + enable link local addressing for IPv4 and IPv6. This can be useful + on thunderbolt devices or host-to-host USB devices. +

+ + +

ID_NET_AUTO_LINK_LOCAL_ONLY

+

+ Honored and treated the same as if NM_AUTO_DEFAULT_LINK_LOCAL_ONLY + were set. +

+ + +

ID_NET_DHCP_BROADCAST

+

+ If set to "1" or "true", use + broadcast requests for DHCPv4 offers. This can make sense of devices + that can't handle unicast messages until being configured. +

+ +
@@ -344,7 +378,7 @@ nmcli(1), nmcli-examples(7), nm-online(1), - nm-settings(5), + nm-settings-nmcli(5), nm-applet(1), nm-connection-editor(1), udev(7) -- cgit 1.3.0-6-gf8a5