summary refs log tree commit diff
path: root/docs/internal/device.md
diff options
context:
space:
mode:
authorMichael Biebl <biebl@debian.org>2024-09-01 22:38:35 +0200
committerMichael Biebl <biebl@debian.org>2024-09-01 22:38:35 +0200
commitf9bfd1158b8d08d6a5ed3bb7cc1ba7a6455e5201 (patch)
tree10267dcf5b842b7c638a79bd6851549cd849b81d /docs/internal/device.md
parent681dfc70ef98f6ed0c05bcb0fbff00e3fc0799ea (diff)
New upstream version 1.49.90 upstream/1.49.90
Diffstat (limited to 'docs/internal/device.md')
-rw-r--r--docs/internal/device.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/internal/device.md b/docs/internal/device.md
index 0042fdc5..f1c31579 100644
--- a/docs/internal/device.md
+++ b/docs/internal/device.md
@@ -304,8 +304,8 @@ Note that the unmanaged flags are tracked via two variables
 practice a tri-state variable with possible values TRUE (unmanaged),
 FALSE (managed) and UNSET.
 
-External devices and sys-iface-state
-------------------------------------
+External devices and managed-type
+---------------------------------
 
 Even if a device is managed, that doesn't mean that NetworkManager is
 actively configuring it. When a device is created externally (for
@@ -314,9 +314,9 @@ creates a in-memory connection representing the configuration
 parameters on the interface such as IP addresses, routes, DNS, etc.;
 the connection appears as active but NetworkManager doesn't actually
 touch the interface. The external status is tracked in the
-`sys-iface-state` member, which can have the following values:
+`managed-type` member, which can have the following values:
 
  - EXTERNAL: the interface is not touched by NM.
  - ASSUME: this value is deprecated; it used to mean that NM should manage the device without fully reconfiguring it. Now, the interface is either managed on external.
- - MANAGED: the interface is fully managed.
+ - FULL: the interface is fully managed.
  - REMOVED: the link was removed externally.