Hi, Please create a bug report with this information at bugzilla.opensuse.org, you will be able to have a much more efficient conversation with the relevant people there then you will here. Thanks Simon On 4/27/21 3:31 AM, Juan Erbes wrote:
For more than a year I have made the setup of a VPN service with the Yast VPN module.
But now I found the service doesn't work right.
The Yast VPN module don't gives the option to place the user for the connection.
In my Android phone with the Strongswan app, I place the name of the vpn server like "ipsec.name1.name2.net", the user and the password for the service AND IT WORKS!
But with Tumbleed is not so easy.
They are 2 ways tosetup the VPN:
1- Via the Yast VPN module
2- Via Network Manager Strongswan
The configuration Via Network Manager Strongswan is not enabled, then not possible.
I have installed:
NetworkManager-strongswan - NetworkManager VPN support for strongSwan
plasma-nm5-strongswan - strongSwan support for plasma-nm5
strongswan - IPsec-based VPN solution
strongswan-hmac - HMAC files for FIPS-140-2 integrity in strongSwan
strongswan-ipsec - IPsec-based VPN solution
strongswan-libs0 - strongSwan core libraries and basic plugins
strongswan-mysql - MySQL plugin for strongSwan
strongswan-nm - NetworkManager plugin for strongSwan
strongswan-sqlite - SQLite plugin for strongSwan
I have reinstalled all the related packages, but no changes!
The status result of the Yast VPN module is:
● strongswan.service - strongSwan IPsec IKEv1/IKEv2 daemon using swanctl
Loaded: loaded (/usr/lib/systemd/system/strongswan.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2021-04-26 14:35:54 -03; 22min ago
Process: 1426 ExecStartPost=/usr/sbin/swanctl --load-all --noprompt (code=exited, status=0/SUCCESS)
Main PID: 1140 (charon-systemd)
Status: "charon-systemd running, strongSwan 5.9.0, Linux 5.11.15-1-default, x86_64"
Tasks: 17 (limit: 4915)
CPU: 147ms
CGroup: /system.slice/strongswan.service
└─1140 /usr/sbin/charon-systemd
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/private' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/rsa' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/ecdsa' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/bliss' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/pkcs8' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: opening directory '/etc/swanctl/pkcs12' failed: No such file or directory
abr 26 14:35:54 linux-9yja swanctl[1426]: no authorities found, 0 unloaded
abr 26 14:35:54 linux-9yja swanctl[1426]: no pools found, 0 unloaded
abr 26 14:35:54 linux-9yja swanctl[1426]: no connections found, 0 unloaded
abr 26 14:35:54 linux-9yja systemd[1]: Started strongSwan IPsec IKEv1/IKEv2 daemon using swanctl.
Regards, Juan
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B