SUMMARY After recent KDE update ability to connect to PAN GP from NM applet in Plasma is lost. Command line openconnect app works flawlessly. NetworkManager-openconnect and plasma-nm5-openconnect packages are installed. STEPS TO REPRODUCE 1. Open Network Connections configuration of NM applet. 2. Press "+" for adding new connection and choose "PAN Global Protect", press "Create". "New connection (vpn)" window appears. 3. Type in vpn gate address, press "Save", close "Connections" window. 4. Go to tray, press NM applet's icon, choose newly created vpn connection and poress "Connect". Login screen appears. 5. Enter creds, press login button - no connection appears with 404 error in log. 6. Go back to NM applet in tray, choose vpn connection, right click on it and press "Configure". See that "Pulse Secure" is being chosen in protocol field instead of "PAN Global Protect". OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Confirming. I had my PAN GP configured and working fine for several months. Today, after changing the gateway for an experiment, I couldn't get it to work with either the new or old gateway. Turns out saving the configuration changed the protocol from PAN GP to Pulse and it was impossible to change it back to PAN GP from the UI, it kept being changed to Pulse when saving the config. Workaround: stop NetworkManager service and manually edit the connection file, in the section [vpn] replace line "protocol=pulse" with "protocol=gp", start the NetworkManager service back. As long a plasma-nm is only used to connect/disconnect from VPN everithing is fine. Linux: 5.11.2 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 NetworkNamager version: 1.28.0 openconnect version: 8.10
(In reply to Andrei Slavoiu from comment #1) > Confirming. I had my PAN GP configured and working fine for several months. > Today, after changing the gateway for an experiment, I couldn't get it to > work with either the new or old gateway. Turns out saving the configuration > changed the protocol from PAN GP to Pulse and it was impossible to change it > back to PAN GP from the UI, it kept being changed to Pulse when saving the > config. > > Workaround: stop NetworkManager service and manually edit the connection > file, in the section [vpn] replace line "protocol=pulse" with "protocol=gp", > start the NetworkManager service back. As long a plasma-nm is only used to > connect/disconnect from VPN everithing is fine. > > Linux: 5.11.2 > KDE Plasma Version: 5.21.2 > KDE Frameworks Version: 5.79.0 > Qt Version: 5.15.2 > NetworkNamager version: 1.28.0 > openconnect version: 8.10 Great catch, Andrei! In turn I confirm that your workaround works - editing "/etc/NetworkManager/system-connections/[connection-name].nmconnection" makes it work as it should. Dear developers, please fix it.
Hello, I can confirm the same bug under Kubuntu 21.04, fresh install. After applying the Andrei workaround I can confirm that now under network manager applet protocol is gp but if I try to connect using the applet, dialog box does not offer any option to set the username and password so I cannot use the applet to connect to the global protect vpn. Can I put username and password in "/etc/NetworkManager/system-connections/[connection-name].nmconnection" at least? how? Thanks!
(In reply to Daniel Morales Salas from comment #3) > Hello, I can confirm the same bug under Kubuntu 21.04, fresh install. After > applying the Andrei workaround I can confirm that now under network manager > applet protocol is gp but if I try to connect using the applet, dialog box > does not offer any option to set the username and password so I cannot use > the applet to connect to the global protect vpn. Can I put username and > password in > "/etc/NetworkManager/system-connections/[connection-name].nmconnection" at > least? how? > > Thanks! I don't have this. After specifying gp as protocol in .nmconnection file it works as it should asking creds and so on. Did you change anything else in .nmconnection file in addition to "protocol" line?
Anyone knows how to raise bug priority or escalate it? New Plasma software versions are coming but this trifling bug is still hanging not resolved and drags on from version to version.
Bulk transfer as requested in T17796