-
Notifications
You must be signed in to change notification settings - Fork 759
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
Implemented wildcard includes for ipsec/strongswan #3311
Conversation
|
does this require empty stub files or is it ok for strongswan if no files are present? |
|
It complains for some but does start... |
|
ok, thanks for the clarification :) |
|
Thanks for being so quick - this is really cool!!! |
|
@stumbaumr can you test a4d157d ? I've dropped the files in directories, which is more aligned with the standard samples that are shipped with the software on our end.
|
|
@AdSchellevis I created comments in your PR - there seems to be a mixup with directory names... |
|
@stumbaumr oops, my mistake, it seems that I mixed them up indeed. take 2 --> dfd48d2 |
|
@AdSchellevis ok, now it works as intended. |
|
@stumbaumr ok, thanks for confirming |
… sample configurations we ship
… sample configurations we ship
So this is the PR mentioned here
#3298
It just adds wildcard includes to
ipsec.conf
ipsec.secrets
strongswan.conf
Best regards
Rainer