Requesting Help and Reporting Bugs » History » Version 11

Version 10 (Noel Kuntze, 17.03.2017 10:39) → Version 11/28 (Tobias Brunner, 17.03.2017 12:25)

{{title(Requesting Help and Reporting Bugs)}}

h1. Requesting Help help and Reporting Bugs reporting bugs

Before you request help or report bugs, please give the following items some have to be given consideration to avoid
wasting your and our time and for optimizing the time it takes to find a solution.


you are **new to strongSwan** please read [[IntroductionTostrongSwan|the introduction]].

If you
look for **help help regarding configuration**, configuration, base your configuration on [[UsableExamples|the the usable examples]] examples first to avoid generic problems.

you are **reporting reporting a security issue**, refer to [[FlawReporting|the dedicated security flaw reporting instructions]].

issue, look at this document.]]
you require help with **configuring configuring special features of strongSwan**, strongSwan, look at [[UserDocumentation#HOWTOs|the the how-tos for those features first]]. first.]]

For other problems please Please follow these the given steps:

# Read the [[FAQ|Frequently Asked Questions (FAQ)]] [[FAQ]]
# Read the manuals (i.e. the (the man pages that come with *your* version of strongSwan)
And and make sure your version of the man page corresponds to strongSwan and not FreeS/WAN, Openswan freeswan, openswan or Libreswan. 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 these those things first]]. 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
keywords that describe your issue. Make sure to include issues.
# Search the "mailing list archives": You may also use your favorite list": using google and google search engine by restricting syntax (use the results @site:@
keyword in the search request for google
to (usually specify the syntax is site that google should
print results for. E.g. NO_PROP_CHOSEN)

# Now, you may can ask for help. Please only write issues and emails to the mailing lists in English only. english. Do not write your messages in any other language.
Please attach When you write the issue, please append your complete config files (ipsec.conf, strongswan.conf, swanctl.conf etc.) 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 occurs
* The complete configuration

* The complete firewall rules (output output of @iptables-save@ (on Linux. Analoges to it on Linux, analogously on other operating systems using the corresponding command(s))
* The complete routing table (output output of @ip route show table all@ on Linux, analogously on other operating systems)

* The complete overview over all IP addresses (output output of @ip address@ on Linux, analogously on other operating systems)

When you create the log file, use the following [[LoggerConfiguration|log settings]], 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