ipsec_tncfg(5) [centos man page]

IPSEC_TNCFG(5)							  [FIXME: manual]						    IPSEC_TNCFG(5)

NAME

       ipsec_tncfg - lists IPSEC virtual interfaces attached to real interfaces

SYNOPSIS

       ipsec tncfg
	     cat/proc/net/ipsec_tncfg

OBSOLETE

       Note that tncfg is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in
       future versions. A replacement command still needs to be designed

DESCRIPTION

       /proc/net/ipsec_tncfg is a read-only file which lists which IPSEC virtual interfaces are attached to which real interfaces, through which
       packets will be forwarded once processed by IPSEC.

       Each line lists one ipsec I/F. A table entry consists of:

       +
	   an ipsec virtual I/F name

       +
	   a visual and machine parsable separator '->', separating the virtual I/F and the physical I/F,

       +
	   a physical I/F name, to which the ipsec virtual I/F is attached or NULL if it is not attached,

       +
	   the keyword mtu=,

       +
	   the MTU of the ipsec virtual I/F,

       +
	   the automatically adjusted effective MTU for PMTU discovery, in brackets,

       +
	   a visual and machine parsable separator '->', separating the virtual I/F MTU and the physical I/F MTU,

       +
	   the MTU of the attached physical I/F.

EXAMPLES

       ipsec2 -> eth3 mtu=16260(1443) -> 1500

       shows that virtual device ipsec2 with an MTU of 16260 is connected to physical device eth3 with an MTU of 1500 and that the effective MTU
       as a result of PMTU discovery has been automatically set to 1443.

       ipsec0 -> wvlan0 mtu=1400(16260) -> 1500

       shows that virtual device ipsec0 with an MTU of 1400 is connected to physical device wvlan0 with an MTU of 1500 and no PMTU packets have
       gotten far enough to bump down the effective MTU from its default of 16260.

       ipsec3 -> NULL mtu=0(0) -> 0

       shows that virtual device ipsec3 is not connected to any physical device.

FILES

       /proc/net/ipsec_tncfg, /usr/local/bin/ipsec

SEE ALSO

       ipsec(8), ipsec_manual(8), ipsec_eroute(5), ipsec_spi(5), ipsec_spigrp(5), ipsec_klipsdebug(5), ipsec_tncfg(8), ipsec_version(5),
       ipsec_pf_key(5)

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.

[FIXME: source] 						    10/06/2010							    IPSEC_TNCFG(5)

IPSEC_KLIPSDEBUG(8)						  [FIXME: manual]					       IPSEC_KLIPSDEBUG(8)

NAME

       ipsec_klipsdebug - set KLIPS and MAST debug features and level. Other stacks are not supported.

SYNOPSIS

       ipsec klipsdebug
	     ipsec klipsdebug --set flagname
	     ipsec klipsdebug --clear flagname
	     ipsec klipsdebug --all
	     ipsec klipsdebug --none
	     ipsec klipsdebug --help
	     ipsec klipsdebug --version

DESCRIPTION

       Klipsdebug sets and clears flags that control various parts of the debugging output of Klips (the kernel portion of FreeS/WAN IPSEC). The
       form with no additional arguments lists the present contents of /proc/net/ipsec_klipsdebug. The --set form turns the specified flag on,
       while the --clear form turns the specified flag off. The --all form turns all flags on except verbose, while the --none form turns all
       flags off.

       The current flag names are:

       tunnel
	   tunnelling code

       tunnel-xmit
	   tunnelling transmit only code

       pfkey
	   userspace communication code

       xform
	   transform selection and manipulation code

       eroute
	   eroute table manipulation code

       spi
	   SA table manipulation code

       radij
	   radij tree manipulation code

       esp
	   encryptions transforms code

       ah
	   authentication transforms code rcv receive code

       ipcomp
	   ip compression transforms code

       verbose
	   give even more information, BEWARE: a)this will print authentication and encryption keys in the logs b)this will probably trample the
	   4k kernel printk buffer giving inaccurate output

       All Klips debug output appears as kernel.info messages to syslogd(8). Most systems are set up to log these messages to /var/log/messages.
       Beware that klipsdebug --all produces a lot of output and the log file will grow quickly.

       The file format for /proc/net/ipsec_klipsdebug is discussed in ipsec_klipsdebug(5).

EXAMPLES

       klipsdebug --all
	   turns on all KLIPS debugging except verbose.

       klipsdebug --clear tunnel
	   turns off only the tunnel debugging messages.

FILES

       /proc/net/ipsec_klipsdebug, /usr/local/bin/ipsec

SEE ALSO

       ipsec(8), ipsec_manual(8), ipsec_tncfg(8), ipsec_eroute(8), ipsec_spi(8), ipsec_spigrp(8), ipsec_klipsdebug(5)

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.

BUGS

       It really ought to be possible to set or unset selective combinations of flags.

[FIXME: source] 						    10/06/2010						       IPSEC_KLIPSDEBUG(8)