Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Matthias Kurz <m.kurz@irregular.at>
To: iwd@lists.linux.dev
Subject: [PATCH 2/2] doc: document externally managed profiles
Date: Tue, 28 Apr 2026 13:47:57 +0200	[thread overview]
Message-ID: <20260428114809.75413-3-m.kurz@irregular.at> (raw)
In-Reply-To: <20260428114809.75413-1-m.kurz@irregular.at>

Document [Settings].ExternallyManaged in iwd.network. The setting
marks profiles that IWD may read but must not update during normal
network operation, while explicit removal remains allowed.
---
 src/iwd.network.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/iwd.network.rst b/src/iwd.network.rst
index 892c6eb8..2b5c3f0e 100644
--- a/src/iwd.network.rst
+++ b/src/iwd.network.rst
@@ -174,6 +174,14 @@ The group ``[Settings]`` contains general settings.
        Properly configured Access Points will typically update this setting
        appropriately via Transition Disable indications.  User customization
        of this value is thus typically not required.
+   * - ExternallyManaged
+     - Values: true, **false**
+
+       If enabled, the profile contents are managed by an external
+       application.  IWD will read the profile but will not update it as a
+       side effect of network operation, for example to persist connection
+       metadata or security material learned at runtime.  Explicit profile
+       removal through the KnownNetwork Forget method is still allowed.
    * - UseDefaultEccGroup
      - Values: true, false
 
-- 
2.54.0


      parent reply	other threads:[~2026-04-28 11:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 11:47 [PATCH 0/2] network: add externally managed profiles Matthias Kurz
2026-04-28 11:47 ` [PATCH 1/2] " Matthias Kurz
2026-04-28 11:47 ` Matthias Kurz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260428114809.75413-3-m.kurz@irregular.at \
    --to=m.kurz@irregular.at \
    --cc=iwd@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox