Misc typo fixes from Adrian Mrva.
This commit is contained in:
wiz
parent
4027f3ad48
commit
fe6e776886
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: named.conf.5,v 1.8 2002/11/17 14:09:53 itojun Exp $
|
||||
.\" $NetBSD: named.conf.5,v 1.9 2002/12/21 13:30:51 wiz Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1999-2000 by Internet Software Consortium
|
||||
.\"
|
||||
|
|
@ -956,7 +956,7 @@ with
|
|||
.Ic maintain-ixfr-base ,
|
||||
and
|
||||
.Ic rfc2308-type1
|
||||
is order dependant.
|
||||
is order dependent.
|
||||
.It Ic host-statistics
|
||||
If
|
||||
.Li yes ,
|
||||
|
|
@ -970,7 +970,7 @@ can consume huge amounts of memory.
|
|||
.It Ic maintain-ixfr-base
|
||||
If
|
||||
.Li yes ,
|
||||
a IXFR database file is kept for all dynamicaly updated zones.
|
||||
a IXFR database file is kept for all dynamically updated zones.
|
||||
This enables the server to answer IXFR queries which can speed up
|
||||
zone transfers enormously.
|
||||
The default is
|
||||
|
|
@ -1287,7 +1287,7 @@ address must appear in the remote end's
|
|||
.Nm allow-transfer
|
||||
option for the zones being transferred, if one is specified. This statement sets the
|
||||
.Nm transfer-source
|
||||
for all zones, but can be overriden on a per-zone basis by includinga
|
||||
for all zones, but can be overriden on a per-zone basis by including a
|
||||
.Nm transfer-source
|
||||
statement within the zone block in the configuration file.
|
||||
.El
|
||||
|
|
@ -1973,7 +1973,7 @@ statement, to be used for transaction security when talking to the
|
|||
remote server.
|
||||
The
|
||||
.Ic key
|
||||
statememnt must come before the
|
||||
statement must come before the
|
||||
.Ic server
|
||||
statement that references it.
|
||||
.Pp
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: ipsend.5,v 1.2 2000/08/09 21:03:06 veego Exp $
|
||||
.\" $NetBSD: ipsend.5,v 1.3 2002/12/21 13:29:29 wiz Exp $
|
||||
.\"
|
||||
.TH IPSEND 5
|
||||
.SH NAME
|
||||
|
|
@ -118,7 +118,7 @@ set the type of service (TOS) field in the IP header. Default is 0.
|
|||
.TP
|
||||
.B len <number>
|
||||
manually specifies the length of the IP packet. The length will automatically
|
||||
be adjusted to accomodate data or further protocol headers.
|
||||
be adjusted to accommodate data or further protocol headers.
|
||||
.TP
|
||||
.B off <number>
|
||||
sets the fragment offset field of the IP packet. Default is 0.
|
||||
|
|
@ -160,7 +160,7 @@ is used to indicate the a ICMP protocol header is to follow. See the
|
|||
is used to indicate that raw data is to be included in the IP packet. See the
|
||||
\fBDATA\fP section for details on options available.
|
||||
.SH "IPv4 Options"
|
||||
these keywords indicate that the releveant IP option should be added to the
|
||||
these keywords indicate that the relevant IP option should be added to the
|
||||
IP header (the header length field will be adjusted appropriately).
|
||||
.TP
|
||||
.B nop
|
||||
|
|
@ -212,7 +212,7 @@ Strict Source Route [RFC 791].
|
|||
Address Extension
|
||||
.TP
|
||||
.B visa
|
||||
Expermental Access Control.
|
||||
Experimental Access Control.
|
||||
.TP
|
||||
.B imitd
|
||||
IMI Traffic Descriptor.
|
||||
|
|
@ -316,7 +316,7 @@ bytes with any particular data).
|
|||
indicates that the string provided should be added to the current packet as
|
||||
data. A string may be a consecutive list of characters and numbers (with
|
||||
no white spaces) or bounded by "'s (may not contain them, even if \\'d).
|
||||
The \\ charcater is recognised with the appropriate C escaped values, including
|
||||
The \\ character is recognised with the appropriate C escaped values, including
|
||||
octal numbers.
|
||||
.TP
|
||||
.B file <filename>
|
||||
|
|
@ -360,7 +360,7 @@ should be routing packets via another route. The redirect code names are:
|
|||
Echo.
|
||||
.TP
|
||||
.B routerad
|
||||
Router Advertisment.
|
||||
Router Advertisement.
|
||||
.TP
|
||||
.B routersol
|
||||
Router solicitation.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: ipf.5,v 1.8 2002/09/25 12:49:40 martti Exp $
|
||||
.\" $NetBSD: ipf.5,v 1.9 2002/12/21 13:28:25 wiz Exp $
|
||||
.\"
|
||||
.TH IPF 5
|
||||
.SH NAME
|
||||
|
|
@ -6,7 +6,7 @@ ipf, ipf.conf, ipf6.conf \- IP packet filter rule syntax
|
|||
.SH DESCRIPTION
|
||||
.PP
|
||||
A rule file for \fBipf\fP may have any name or even be stdin. As
|
||||
\fBipfstat\fP produces parseable rules as output when displaying the internal
|
||||
\fBipfstat\fP produces parsable rules as output when displaying the internal
|
||||
kernel filter lists, it is quite plausible to use its output to feed back
|
||||
into \fBipf\fP. Thus, to remove all filters on input packets, the following
|
||||
could be done:
|
||||
|
|
@ -138,7 +138,7 @@ with a rule which is being applied to TCP packets. When using
|
|||
\fBreturn-icmp\fP or \fBreturn-icmp-as-dest\fP, it is possible to specify
|
||||
the actual unreachable `type'. That is, whether it is a network
|
||||
unreachable, port unreachable or even administratively
|
||||
prohibitied. This is done by enclosing the ICMP code associated with
|
||||
prohibited. This is done by enclosing the ICMP code associated with
|
||||
it in parenthesis directly following \fBreturn-icmp\fP or
|
||||
\fBreturn-icmp-as-dest\fP as follows:
|
||||
.nf
|
||||
|
|
@ -388,7 +388,7 @@ against, e.g.:
|
|||
.TP
|
||||
.B icmp-type
|
||||
is only effective when used with \fBproto icmp\fP and must NOT be used
|
||||
in conjuction with \fBflags\fP. There are a number of types, which can be
|
||||
in conjunction with \fBflags\fP. There are a number of types, which can be
|
||||
referred to by an abbreviation recognised by this language, or the numbers
|
||||
with which they are associated can be used. The most important from
|
||||
a security point of view is the ICMP redirect.
|
||||
|
|
@ -429,7 +429,7 @@ indicates that the rule should be put in group (number n) rather than group 0.
|
|||
.PP
|
||||
When a packet is logged, with either the \fBlog\fP action or option,
|
||||
the headers of the packet are written to the \fBipl\fP packet logging
|
||||
psuedo-device. Immediately following the \fBlog\fP keyword, the
|
||||
pseudo-device. Immediately following the \fBlog\fP keyword, the
|
||||
following qualifiers may be used (in order):
|
||||
.TP
|
||||
.B body
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: ipnat.5,v 1.10 2002/09/19 08:11:15 martti Exp $
|
||||
.\" $NetBSD: ipnat.5,v 1.11 2002/12/21 13:28:25 wiz Exp $
|
||||
.\"
|
||||
.TH IPNAT 5
|
||||
.SH NAME
|
||||
|
|
@ -112,9 +112,9 @@ Only IP address and port numbers can be compared against. This is available
|
|||
with all NAT rules.
|
||||
.SH TRANSLATION
|
||||
.PP
|
||||
To the right of the "->" is the address and port specificaton which will be
|
||||
To the right of the "->" is the address and port specification which will be
|
||||
written into the packet providing it has already successful matched the
|
||||
prior constraints. The case of redirections (\fBrdr\fP) is the simpliest:
|
||||
prior constraints. The case of redirections (\fBrdr\fP) is the simplest:
|
||||
the new destination address is that specified in the rule. For \fBmap\fP
|
||||
rules, the destination address will be one for which the tuple combining
|
||||
the new source and destination is known to be unique. If the packet is
|
||||
|
|
@ -192,7 +192,7 @@ map ppp0 10.0.0.0/8 -> 209.1.2.0/24
|
|||
.fi
|
||||
.PP
|
||||
so that all TCP/UDP packets were port mapped and only other protocols, such as
|
||||
ICMP, only have their IP# changed. In some instaces, it is more appropriate
|
||||
ICMP, only have their IP# changed. In some instances, it is more appropriate
|
||||
to use the keyword \fBauto\fP in place of an actual range of port numbers if
|
||||
you want to guarantee simultaneous access to all within the given range.
|
||||
However, in the above case, it would default to 1 port per IP address, since
|
||||
|
|
|
|||
Loading…
Reference in New Issue