Requesting Help and Reporting Bugs » History » Version 8

Version 7 (Noel Kuntze, 10.03.2017 23:20) → Version 8/28 (Noel Kuntze, 16.03.2017 18:39)

h1. Requesting help and reporting bugs

Before you request help or report bugs, the following items have to be given consideration to avoid
wasting your and our time and for optimizing the time it takes to find a solution.
[[SaneExamples|If you look for help regarding configuration, base your configuration on the usable examples first to avoid generic problems.]]
[[FlawReporting|If you are reporting a security issue, look at this document.]]
[[UserDocumentation#HOWTOs|If you require help with configuring special features of strongSwan, look at the how-tos for those first.]]

Please follow the given steps:

# Read the [[FAQ]]
# Read the manuals (the man pages that come with *your* version of strongSwan)
and make sure your version of the man page corresponds to strongSwan and not freeswan, openswan or libreswan.
The software that a man page belongs to is usually printed in the center top of the man page when it's initially opened.
# Make sure you put the files into the right directories. On distributions that stem from RHEL, strongSwan configuration files are under @/etc/strongswan@.
# If charon crashes, [[FAQ#strongSwan-crashes|try those things first.]]
# Make sure your version is up to date. A lot of actual bugs (not user error) are fixed in newer versions of strongSwan.
# Search the bug tracker using the "search function": for keywords from the logs
or keywords that describe your issue. Make sure to include issues.
# Search the "mailing list": using google and google search syntax (use the @site:@
keyword in the search request for google to specify the site that google should
print results for. E.g. NO_PROP_CHOSEN)
# Now, you can ask for help. Please only write issues and emails in english. Do not write your messages in any other language.
When you write the issue, please append your complete ipsec.conf, strongswan.conf and a complete log file showing the problem.
We generally require the following from you
# The complete log from daemon start to the point where the problem appears
# The complete configuration
# The complete output of `iptables-save` (on Linux. Analoges to it on other operating systems)
# The complete output of `ip route show table all`
# The complete output of `ip address`
When you create the log file, use the following log settings, unless we tell you otherwise.
filelog {
/var/log/charon_debug.log {
time_format = %a, %Y-%m-%d %R
default = 2
mgr = 0
net = 1
enc = 1
asn = 1
job = 1
knl = 1
ike_name = yes
append = no
flush_line = yes