1IPSEC_BARF(8)                   [FIXME: manual]                  IPSEC_BARF(8)
2
3
4

NAME

6       ipsec_barf - spew out collected IPsec debugging information
7

SYNOPSIS

9       ipsec barf [--short --maxlines <100>]
10

DESCRIPTION

12       Barf outputs (on standard output) a collection of debugging information
13       (contents of files, selections from logs, etc.) related to the IPsec
14       encryption/authentication system. It is primarily a convenience for
15       remote debugging, a single command which packages up (and labels) all
16       information that might be relevant to diagnosing a problem in IPsec.
17
18       The --short option limits the length of the log portion of barf´s
19       output, which can otherwise be extremely voluminous if debug logging is
20       turned on.
21
22       --maxlines <100> option sets the length of some bits of information,
23       currently netstat -rn. Useful on boxes where the routing table is
24       thousands of lines long. Default is 100.
25
26       Barf censors its output, replacing keys and secrets with brief
27       checksums to avoid revealing sensitive information.
28
29       Beware that the output of both commands is aimed at humans, not
30       programs, and the output format is subject to change without warning.
31
32       Barf has to figure out which files in /var/log contain the IPsec log
33       messages. It looks for KLIPS and general log messages first in messages
34       and syslog, and for Pluto messages first in secure, auth.log, and
35       debug. In both cases, if it does not find what it is looking for in one
36       of those “likely” places, it will resort to a brute-force search of
37       most (non-compressed) files in /var/log.
38

FILES

40           /proc/net/*
41           /var/log/*
42           /etc/ipsec.conf
43           /etc/ipsec.secrets
44

HISTORY

46       Written for the Linux FreeS/WAN project <http://www.freeswan.org> by
47       Henry Spencer.
48

BUGS

50       Barf uses heuristics to try to pick relevant material out of the logs,
51       and relevant messages which are not labelled with any of the tags that
52       barf looks for will be lost. We think we´ve eliminated the last such
53       case, but one never knows...
54
55       Finding updown scripts (so they can be included in output) is, in
56       general, difficult.  Barf uses a very simple heuristic that is easily
57       fooled.
58
59       The brute-force search for the right log files can get expensive on
60       systems with a lot of clutter in /var/log.
61
62
63
64[FIXME: source]                  17 March 2002                   IPSEC_BARF(8)
Impressum