Right now it seems one can only change settings for a ssid/wifi-connection after connecting to it.
One can change settings on active connection and on Previously Used. But not on unused/never connected to.
The Randomize Mac function is a little redundant if you join all public ssid:s with your static mac before changing it.
DNS is also something one might like to change to static before joining the wifi-network.
(I know adding match-device=type:wifi wifi.cloned-mac-address=stable-ssid / random
in /etc/NetworkManager/conf.d/some-number-some-name.conf will make random mac default.
But regarding that, it would be nice to be able to change/see status of that (default randomize mac) from KDE networking menu as well. I feel it’s something you have to know about and then actively look for now, when a lot of people would turn that on right away seeing it in the settings not having thought about it or heard about it.
I’m fairly sure the standard setting is out of KDE’s reach, but distro-based(?), if not, I’d recommend hit that up as standard. Even stalker company #1 Alphabeth think it’s a little too stalky and have it as a default on android. )
It’s only a discussion about the KDE gui part, about making it bit more user friendly and function rich. (Brainstorming)
If I want the things I mentioned (plus TLS, good idea) I can run: > nmcli connection add con-name JohnsCafe connection.type 802-11-wireless wifi.ssid JohnsCafe connection.autoconnect yes connection.dns-over-tls 2 ipv4.dns 194.2 42.2.2#``dns.mullvad.net`` wifi.cloned-mac random wifi-sec.key-mgmt wpa-psk wifi-sec.psk 12345678 && nmcli device wifi connect JohnsCafe
I can even just run > nmcli connection add con-name JohnsCafe connection.type 802-11-wireless wifi.ssid JohnsCafe
so /etc/NetworkManager/system-connections/JohnsCafe.nmconnection gets created, that “tricks” KDE network manager to let me edit it there before connecting (like spoofing mac and adding non-TLS DNS).
I’m guessing KDE networking view is mostly a wrapper of nmcli and NetworkManager.
If that’s the case it sounds like it wouldn’t be a huge endeavor to be able to configure before connecting. At least some (where randomize mac is the most important imo).
System wide settings is also quite lackluster to say the least, there is none to make (again, talking about KDE gui here). Understandable though with the way NetworkManager handles config files. Which to relate to. But only relating to 1 file (or 1 per setting) KDE makes itself with relatively high priority, ignoring all other would go quite a long way I think. Even if it would show wrong if one over wrote it with an higher priority config file modifying the same setting.