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
ipsec: Not well-formed (invalid token) at line 1 in /tmp/strongswan_leases.xml error #139
Comments
From a production system -- found while skimming the logs. |
Another "nice" custom patch, /usr/local/sbin/ipsec stroke leases normally doesn't deliver xml output. Eventually we might need to look at https://wiki.strongswan.org/projects/strongswan/wiki/VICI to replace all the custom hooks and not very well supported process communication (smp) and handle the commands in the backend using configd. |
Agreed, that sounds a lot better... |
…entries We do need to rethink the interaction with ipsec, It looks like a strange mix of parts now. Ideally we should ask ipsec about the connections that can be made instead of creating a strange mix of configuration and daemon entries. related issue #139
…entries We do need to rethink the interaction with ipsec, It looks like a strange mix of parts now. Ideally we should ask ipsec about the connections that can be made instead of creating a strange mix of configuration and daemon entries. related issue #139
First step is to switch the current status page away from legacy smp. (work in progress)
First step is to switch the current status page away from legacy smp. (work in progress) (cherry picked from commit a876238)
This is relevant ;) |
I think VICI delivers the same data also, but not 100%, will have to look at that... parsing of "ipsec leases" is also an option. |
Getting it all into VICI sounds like the best approach in the long run. |
I will look into that as soon as I have the time. |
Yay, you get one holiday well-deserved :) |
(cherry picked from commit 1d1c2c6)
The text was updated successfully, but these errors were encountered: