Bug 437453

Summary: VPN protocol cannot be changed away from “pulse”
Product: [Applications] systemsettings Reporter: Philipp A. <flying-sheep>
Component: kcm_networkmanagementAssignee: Jan Grulich <jgrulich>
Status: RESOLVED FIXED    
Severity: normal CC: jgrulich, nate, rakuco
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Philipp A. 2021-05-21 10:54:36 UTC 
When creating a new VPN connection and selecting any protocol it gets saved in /etc/NetworkManager/system-connections/<name>.nmconnection as “protocol=pulse”.

The same applies to editing a connection: The dialog opens with “Pulse Connect Secure” visible in the dropdown, no matter what the (manually edited) config file says. Changing anything and saving the config (no matter if you select the protocol you want first or not) resets the config file to contain “protocol=pulse”


STEPS TO REPRODUCE
1. Create a new VPN (openconnect) connection
2. Select any protocol other than “Pulse Connect Secure”
3. Save it

OBSERVED RESULT
- The saved protocol in the config file is always “pulse”
- As is the one it actually tries to use when connecting
- As is the one selected in the select box in the edit dialog, no matter what is actually in the configuration file

EXPECTED RESULT
The protocol I selected is saved and used

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Comment 1 Raphael Kubo da Costa 2021-10-17 13:35:31 UTC 
Is this still an issue? I tried to reproduce this with plasma-nm 5.21.5 and only ran into an issue (already fixed) where choosing the "PAN Global Protect" protocol would end up choosing Pulse instead.

Other than that, creating a new VPN connection with e.g. the "Cisco AnyConnect" protocol sets it in the nmconnection file, and switching the protocol to something like "Juniper Network Connect" in the UI also worked. Reopening the settings continued to show the protocol I'd selected, and so did nmcli.
Comment 2 Philipp A. 2022-07-14 07:56:29 UTC 
Seems fixed, yes!