summaryrefslogtreecommitdiffstats
path: root/lib/libalias
diff options
context:
space:
mode:
authorjkoshy <jkoshy@FreeBSD.org>1998-06-06 05:50:53 +0000
committerjkoshy <jkoshy@FreeBSD.org>1998-06-06 05:50:53 +0000
commit0d7d76d9824e92ac3e2d5c95c38338e47b940aad (patch)
treebe821f05efcc76f3383e79528b109973541e2d79 /lib/libalias
parentb4a37e244c5a9f59a7cc8f6048914ad390dd6bb6 (diff)
downloadFreeBSD-src-0d7d76d9824e92ac3e2d5c95c38338e47b940aad.zip
FreeBSD-src-0d7d76d9824e92ac3e2d5c95c38338e47b940aad.tar.gz
Spelling corrections.
PR: 6868 Submitted by: Josh Gilliam <josh@quick.net>
Diffstat (limited to 'lib/libalias')
-rw-r--r--lib/libalias/libalias.322
1 files changed, 11 insertions, 11 deletions
diff --git a/lib/libalias/libalias.3 b/lib/libalias/libalias.3
index 37e1786..b3fcc91 100644
--- a/lib/libalias/libalias.3
+++ b/lib/libalias/libalias.3
@@ -76,7 +76,7 @@ different groups of private addresses
can be linked to different public addresses,
comprising several distinct many-to-one
mappings. Also, a given public address
-and port can be staticly redirected to
+and port can be statically redirected to
a private address/port.
The packet aliasing engine was designed
@@ -212,7 +212,7 @@ unknown host address or unknown port number
(e.g. an FTP data connection), this mode bit
specifies that a socket be allocated as a place
holder to prevent port conflicts. Once a
-connection is extablished, usually within a
+connection is established, usually within a
minute or so, the socket is closed.
.It PKT_ALIAS_UNREGISTERED_ONLY.
If this mode bit is set, traffic on the
@@ -299,7 +299,7 @@ Return codes:
.Bl -hang -offset left
.It PKT_ALIAS_ERROR.
An internal error within the packet aliasing
-engine occured.
+engine occurred.
.It PKT_ALIAS_OK.
The packet aliasing process was successful.
.It PKT_ALIAS_IGNORED.
@@ -333,9 +333,9 @@ The IP packet is pointed to by
.Em buffer r,
and
.Em maxpacketsize
-indicates the maximum packet size permissable
+indicates the maximum packet size permissible
should the packet length be changed. IP encoding
-protocols place addresss and port information in
+protocols place address and port information in
the encapsulated data stream which have to be
modified and can account for changes in packet
length. Well known examples of such protocols
@@ -345,7 +345,7 @@ Return codes:
.Bl -hang -offset left
.It PKT_ALIAS_ERROR.
An internal error within the packet aliasing
-engine occured.
+engine occurred.
.It PKT_ALIAS_OK.
The packet aliasing process was successful.
.It PKT_ALIAS_IGNORED.
@@ -376,7 +376,7 @@ address translations can be designated.
This function specifies that traffic from a
given remote address/port to an alias address/port
be redirected to a specified local address/port.
-The paramater
+The parameter
.Em proto
can be either IPPROTO_TCP or IPPROTO_UDP, as
defined in <netinet/in.h>.
@@ -682,7 +682,7 @@ number for identifying how individual packets
should be handled.)
Each aliasing link must have a unique
-combination of the following five quanties:
+combination of the following five quantities:
alias address/port, remote address/port
and protocol. This ensures that several
machines on a local network can share the
@@ -699,7 +699,7 @@ sequence. For the case of TCP, the connection
can be monitored to see when the associated
aliasing link should be deleted. Aliasing links
for UDP transactions (and ICMP echo and timestamp
-equests) work on a simple timeout rule. When
+requests) work on a simple timeout rule. When
no activity is observed on a dynamic link for
a certain amount of time it is automatically
deleted. Timeout rules also apply to TCP
@@ -708,7 +708,7 @@ properly.
.Ss A.3 Partially Specified Aliasing Links
Aliasing links can be partially specified,
meaning that the remote address and/or remote
-ports are unkown. In this case, when a packet
+ports are unknown. In this case, when a packet
matching the incomplete specification is found,
a fully specified dynamic link is created. If
the original partially specified link is dynamic,
@@ -750,7 +750,7 @@ the alias address to be used. If no mapping
exists, then a default address, usually the
address of the packet aliasing host, is used.
If necessary, this default address can be
-changed as often as each indvidual packet
+changed as often as each individual packet
arrives.
The aliasing port number is determined
OpenPOWER on IntegriCloud