diff options
| author | sobomax <sobomax@FreeBSD.org> | 2001-06-05 12:50:33 +0000 |
|---|---|---|
| committer | sobomax <sobomax@FreeBSD.org> | 2001-06-05 12:50:33 +0000 |
| commit | 94f6dd139dc6e81e23c708a958736368859f94df (patch) | |
| tree | a4f3d77ce595814121c7aa83d5c4d853e3e2ac9c /share/man/man4/ipsec.4 | |
| parent | 0c29f662fa3edb02681d8c010e1077e64f22cec8 (diff) | |
| download | FreeBSD-src-94f6dd139dc6e81e23c708a958736368859f94df.zip FreeBSD-src-94f6dd139dc6e81e23c708a958736368859f94df.tar.gz | |
Correct cross-references:
setsockopt.3 --> setsockopt.2
syslog.8 --> syslogd.8
tcpdump.8 --> tcpdump.1
MFC after: 1 week
Diffstat (limited to 'share/man/man4/ipsec.4')
| -rw-r--r-- | share/man/man4/ipsec.4 | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man4/ipsec.4 b/share/man/man4/ipsec.4 index ff404cc..f5a81df 100644 --- a/share/man/man4/ipsec.4 +++ b/share/man/man4/ipsec.4 @@ -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. |
