Requesting Help and Reporting Bugs » History » Version 1

Noel Kuntze, 15.01.2017 21:20
First version

1 1 Noel Kuntze
h1. Requesting help and reporting bugs
2 1 Noel Kuntze
3 1 Noel Kuntze
Before you request help or report bugs, the following items have to be given consideration to avoid
4 1 Noel Kuntze
wasting your and our time and for optimizing the time it takes to find a solution.
5 1 Noel Kuntze
[[SaneExamples|If you look for help regarding configuration, base your configuration on the sane examples first to avoid generic problems.]]
6 1 Noel Kuntze
[[FlawReporting|If you are reporting a security issue, look at this document.]]
7 1 Noel Kuntze
8 1 Noel Kuntze
Please follow the given steps:
9 1 Noel Kuntze
10 1 Noel Kuntze
# Read the [[FAQ]]
11 1 Noel Kuntze
# Read the manuals (the man pages that come with *your* version of strongSwan)
12 1 Noel Kuntze
  and make sure your version of the man page corresponds to strongSwan and not freeswan, openswan or libreswan.
13 1 Noel Kuntze
  The software that a man page belongs to is usually printed in the center top of the man page when it's initially opened.
14 1 Noel Kuntze
# Make sure you put the files into the right directories. On distributions that stem from RHEL, strongSwan configuration files are under @/etc/strongswan@.
15 1 Noel Kuntze
# If charon crashes, [[|make sure it's not because of pebkac]]
16 1 Noel Kuntze
# Make sure your version is up to date. A lot of actual bugs are fixed in newer versions of strongSwan.
17 1 Noel Kuntze
# Search the bug tracker using the "search function": for keywords from the logs
18 1 Noel Kuntze
  or keywords that describe your issue. Make sure to include issues.
19 1 Noel Kuntze
# Search the "mailing list": using google and google search syntax (use the @site:@
20 1 Noel Kuntze
  keyword in the search request for google to specify the site that google should
21 1 Noel Kuntze
  print results for. E.g. NO_PROP_CHOSEN)