Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

setsockopt lives in 2, not 3.

This commit is contained in:
wiz 2001-04-04 10:55:49 +00:00
parent 9c9b947015
commit 1d0d17a4fe
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
share/man/man4/ipsec.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: ipsec.4,v 1.12 2001/01/22 07:30:40 itojun Exp $
.\" $NetBSD: ipsec.4,v 1.13 2001/04/04 10:55:49 wiz Exp $
.\" $KAME: ipsec.4,v 1.14 2001/01/22 07:29:45 itojun Exp $
.\"
.\" Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
@ -104,7 +104,7 @@ by using the above described APIs.
The kernel implements experimental policy management code.
You can manage the IPsec policy in two ways.
One is to configure per-socket policy using
.Xr setsockopt 3 .
.Xr setsockopt 2 .
The other is to configure kernel packet filter-based policy using
.Dv PF_KEY
interface, via
@ -113,7 +113,7 @@ In both cases, IPsec policy must be specified with syntax described in
.Xr ipsec_set_policy 3 .
.Pp
With
.Xr setsockopt 3 ,
.Xr setsockopt 2 ,
you can define IPsec policy in per-socket basis.
You can enforce particular IPsec policy onto packets that go through
particular socket.