ipsec_pf_key(8) [centos man page]

IPSEC_PF_KEY(8) 						Executable programs						   IPSEC_PF_KEY(8)

NAME

       ipsec_pf_key - shows pfkey messages emitted by the kernel when using the KLIPS or MAST stack.

SYNOPSIS

       pf_key --ah --esp --ipip --ipcomp --daemon filehmac-md5-96 | hmac-sha1-96

STACK

       Note that pf_key is only supported on the KLIPS and MAST stacks. It is not supported on any other stack.

DESCRIPTION

       pf_key is a program to open a PF_KEY socket and print all messages that are received from it. With no options, it will register itself to
       receive key requests for AH, ESP, IPIP and IPCOMP security associations. If given more specific options, then it will listen only to those
       protocols which are listed.

       If the messages are recognized, the messages will be decoded.

       If the option --daemon is provided, then after doing the registrations, the program will fork into the background. The provided file will
       be opened and the process ID of the background process will be written to it. This option is present to present race conditions in
       regression testing.

FILES

       /proc/net/pf_key

SEE ALSO

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

HISTORY

       Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Michael Richardson <mcr@freeswan.org>

AUTHOR

       Paul Wouters
	   placeholder to suppress warning

libreswan							    12/16/2012							   IPSEC_PF_KEY(8)

IPSEC_TNCFG(8)							Executable programs						    IPSEC_TNCFG(8)

NAME

       ipsec_tncfg - manipulate KLIPS virtual interfaces

SYNOPSIS

       ipsec tncfg
	     ipsec tncfg --create virtual
	     ipsec tncfg --delete virtual
	     ipsec tncfg --attach --virtual virtual --physical physical
	     ipsec tncfg --detach --virtual virtual
	     ipsec tncfg --clear
	     ipsec tncfg --version
	     ipsec tncfg --help

KLIPS

       Note that tncfg is only supported on the KLIPS stack which uses ipsecX interfaces bound to physical interfaces

DESCRIPTION

       The purpose of tncfg is to attach/detach IPsec virtual interfaces (e.g. ipsec0) to/from physical interfaces (e.g. eth0) through which
       packets will be forwarded once processed by KLIPS.

       When using the MAST stack, tncfg is used to create and delete virtual interfaces known as mastXXX. mast stands for Mooring and XXX.

       The form with no additional arguments lists the contents of /proc/net/ipsec_tncfg. The format of /proc/net/ipsec_tncfg is discussed in
       ipsec_tncfg(5).

       The --attach form attaches the virtual interface to the physical one.

       The --detach form detaches the virtual interface from whichever physical interface it is attached to.

       The --clear form clears all the virtual interfaces from whichever physical interfaces they were attached to.

       Virtual interfaces typically have names like ipsec0 or mast0 while physical interfaces typically have names like eth0 or ppp0.

EXAMPLES

       ipsec tncfg --create mast12
	   creates the mast12 device.

       ipsec tncfg --create ipsec4
	   creates an ipsec4 device, but does not attach it.

       ipsec tncfg --attach --virtual ipsec0 --physical eth0
	   attaches the ipsec0 virtual device to the eth0 physical device.

FILES

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

SEE ALSO

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

HISTORY

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

AUTHOR

       Paul Wouters
	   placeholder to suppress warning

libreswan							    12/16/2012							    IPSEC_TNCFG(8)