-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing EAP Secrets in StrongMan GUI broke preconfigured secrets. #163
Comments
The problem is that both clients (swanctl and strongMan) basically assume they have exclusive access to the config. So strongMan sends a |
Oh boy. I'm not very good at programming.
strongMan/strongMan/helper_apps/vici/wrapper/wrapper.py
/root/scripts/clear_creds.sh
strongMan/load-creds.py
Working well. |
Hello
Debian 11.11. Strongswan 5.9.1. StrongMan from git
I have preconfigured Strongswan with static config files like:
/etc/swanctl/ikev1-l2tp-accel-ppp.conf
This configuration is used for old clients who can't do anything else L2TP-PSK+login\pass
Successful connection logs like:
I installed StrongMan for IKEv2 clients on the same server. Everything works fine until I add or remove any EAP Secrets in StrongMan GUI. Preconfigured L2TP connections immediately stop working with a message in the log - "no shared key found for".
As I understand it, editing EAP Secrets from GUI deletes secrets that are loaded from the static configuration files.
This is bug ?
Also IKEv2+PSK+login/pass start got same error.
The text was updated successfully, but these errors were encountered: