1 .\" $NetBSD: fast_ipsec.4,v 1.7 2008/05/25 20:08:12 wiz Exp $
2 .\" $FreeBSD: fast_ipsec.4,v 1.2 2003/03/03 11:51:30 ru Exp $
5 .\" Jonathan Stone <jonathan@dsg.stanford.edu>. All rights reserved.
8 .\" Sam Leffler <sam@errno.com>. All rights reserved.
10 .\" Redistribution and use in source and binary forms, with or without
11 .\" modification, are permitted provided that the following conditions
13 .\" 1. Redistributions of source code must retain the above copyright
14 .\" notice, this list of conditions and the following disclaimer.
15 .\" 2. Redistributions in binary form must reproduce the above copyright
16 .\" notice, this list of conditions and the following disclaimer in the
17 .\" documentation and/or other materials provided with the distribution.
19 .\" THIS SOFTWARE IS PROVIDED BY Sam Leffler AND CONTRIBUTORS ``AS IS'' AND
20 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
23 .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
29 .\" THE POSSIBILITY OF SUCH DAMAGE.
36 .Nd Fast IPsec hardware-accelerated IP Security Protocols
38 .Cd "options FAST_IPSEC"
39 .Cd "options IPSEC_NAT_T"
40 .Cd "pseudo-device crypto"
43 is a set of protocols,
45 (for Encapsulating Security Payload)
47 (for Authentication Header),
50 (for IP Payload Compression Protocol)
51 that provide security services for IP datagrams.
53 is an implementation of these protocols that uses the
55 subsystem to carry out cryptographic operations.
56 This means, in particular, that cryptographic hardware devices are
57 employed whenever possible to optimize the performance of these protocols.
61 implementation is intended to be compatible with the
64 This documentation concentrates on differences from that software.
65 The user should refer to
67 for basic information on setting up and using these protocols.
69 System configuration requires the
74 protocols are configured for use, all protocols are included in the system.
75 To selectively enable/disable protocols, use
85 The protocols draw heavily on the
90 The policy management code is derived from the
92 implementation found in their
97 protocols are based on code which appeared in
101 version is a close copy of the
103 original, and first appeared in
108 protocols has been added in
111 Support for IPSEC_NAT_T
112 (Network Address Translator Traversal as
113 described in RFCs 3947 and 3948) has been added in
116 There still are some issues in the IPv6 support.
119 does not protect packets with IPv6 extension headers.
121 Certain legacy authentication algorithms are not supported because of
126 This documentation is incomplete.