Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ipsec.conf(5) [netbsd man page]

IPSEC.CONF(5)						      BSD File Formats Manual						     IPSEC.CONF(5)

ipsec.conf -- static IPsec configuration read at system startup DESCRIPTION
The ipsec.conf file is read at system startup time if ipsec is set to ``yes'' in rc.conf(5). setkey(8) is run with the -f option to load in IPsec manual keys and policies from /etc/ipsec.conf at boot time, before any interfaces are configured. Please see the setkey(8) manpage for all the commands available. FILES
/etc/ipsec.conf The file ipsec.conf resides in /etc. SEE ALSO
ipsec(4), setkey(8) HISTORY
The ipsec.conf file appeared in NetBSD 1.5. BSD
February 19, 2001 BSD

Check Out this Related Man Page

IPSEC_TNCFG(8)							Executable programs						    IPSEC_TNCFG(8)

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 <> by Richard Guy Briggs. AUTHOR
Paul Wouters placeholder to suppress warning libreswan 12/16/2012 IPSEC_TNCFG(8)
Man Page

2 More Discussions You Might Find Interesting

1. Cybersecurity

IPSec - VPN using shared key

Hello! I have some trouble trying to configure a VPN with two gateways. One of them uses IPSec with a single key, 256bits length, specified in /etc/ipsec.secrets. As FreeSwan manual page says, if i put esp=3des-md5-96, will be used a "64bit IV key (internally generated), a 192bit 3des ekey and a... (3 Replies)
Discussion started by: eNTer
3 Replies

2. IP Networking

How to establish site to site vpn - Linux machine and cisco asa?

Hi, I am trying to establish vpn between my linux server and cisco asa at client side. I installed openswan on my cent os. Linux Server eth0 - Gateway - eth1 - I have simple IPtables Like WAN="eth0" LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies