From 67449130e9fdd71a38ca26539dddfa8c882b1977 Mon Sep 17 00:00:00 2001 From: Fiona Klute Date: Wed, 17 Jun 2026 16:35:27 +0200 Subject: [PATCH] docs/manual/migrating.adoc: document iwd network config change for 2026.08 With 8536a5d04a6a83d9ec4b4922b99c14a7c4a8ae92 the upstream default config is used, changing EnableNetworkConfiguration. Signed-off-by: Fiona Klute Signed-off-by: Marcus Hoffmann --- docs/manual/migrating.adoc | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/manual/migrating.adoc b/docs/manual/migrating.adoc index d8d86d8945..230754be76 100644 --- a/docs/manual/migrating.adoc +++ b/docs/manual/migrating.adoc @@ -247,3 +247,14 @@ In 2026.02, the network-manager package stopped selecting the gnutls package as a cryptography backend automatically. Manually enable the gnutls or libnss package if you require features that depend on a cryptography backend, such as certificate-based authentication. + +[[migrating-to-2026-08]] +=== Migration to 2026.08 + +In 2026.08, the iwd package stopped installing a custom ++/etc/iwd/main.conf+, and started using the upstream example +instead. With that the +EnableNetworkConfiguration+ setting changed +from +true+ to +false+, in line with upstream defaults. If you need ++EnableNetworkConfiguration=true+ to let +iwd+ handle network +configuration for active wifi connections, adjust +/etc/iwd/main.conf+ +in your build (see xref:rootfs-custom[] for options).