From fccd6e70bea7c6ec0176d8f08917cd4b74b34ee1 Mon Sep 17 00:00:00 2001 From: Chuck Date: Sat, 2 May 2026 11:20:27 -0400 Subject: [PATCH] =?UTF-8?q?fix(wifi):=20remove=20PMF=20setting=20from=20op?= =?UTF-8?q?en=20AP=20profile=20=E2=80=94=20breaks=20nmcli=20connection=20a?= =?UTF-8?q?dd=20on=20Trixie=20NM=201.52+?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 802-11-wireless-security.pmf is only valid within a security section that also includes key-mgmt. Adding it to an open-network profile causes NM 1.52+ to reject the connection add with 'key-mgmt: property is missing'. PMF has no meaning for open APs (it only applies to WPA2/WPA3), so the setting is simply removed rather than worked around. Found by testing on devpi (Trixie, NM 1.52.1). Co-Authored-By: Claude Sonnet 4.6 --- src/wifi_manager.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/wifi_manager.py b/src/wifi_manager.py index 6521d6df..286b67e7 100644 --- a/src/wifi_manager.py +++ b/src/wifi_manager.py @@ -2007,10 +2007,10 @@ class WiFiManager: # No 802-11-wireless-security section → open network ] - # On Trixie disable PMF which can prevent older clients from connecting - if self._is_trixie: - cmd += ["802-11-wireless-security.pmf", "disable"] - logger.info("Trixie detected: disabling PMF for better client compatibility") + # PMF (Protected Management Frames) is only meaningful for WPA2/WPA3. + # An open AP has no security section, so adding 802-11-wireless-security.pmf + # would cause NM to require key-mgmt too, breaking the connection add on + # Trixie NM 1.52+. Leave PMF untouched — open APs have no frame protection. result = subprocess.run(cmd, capture_output=True, text=True, timeout=30)