d/freebsd-nq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Restore sub-chapters order.

Browse Source 
PR:		docs/14766
Submitted by:	Kazutoshi Kubota <kazu@iworks.co.jp>
This commit is contained in:
Alexey Zelkin 1999-11-09 00:24:09 +00:00
parent 55b80e58ba
commit 1855100f8f
2 changed files with 32 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
lib/libalias/libalias.3
View File

@ -495,24 +495,6 @@ functions. If an invalid pointer is passed to
PacketAliasRedirectDelete(), then a program crash
or unpredictable operation could result, so it is
necessary to be careful using this function.
.Sh 5. Fragment Handling
The functions in this section are used to deal with
incoming fragments.
Outgoing fragments are handled within PacketAliasOut()
by changing the address according to any
applicable mapping set by PacketAliasRedirectAddress(),
or the default aliasing address set by
PacketAliasSetAddress().
Incoming fragments are handled in one of two ways.
If the header of a fragmented IP packet has already
been seen, then all subsequent fragments will be
re-mapped in the same manner the header fragment
was. Fragments which arrive before the header
are saved and then retrieved once the header fragment
has been resolved.
.Ss 4.4 PacketAliasProxyRule()
.Ft int
@ -599,7 +581,6 @@ network will be matched.
This function is usually used to redirect outgoing connections for
internal machines that are not permitted certain types of internet
access, or to restrict access to certain external machines.
.Ss 4.5 PacketAliasPptp()
.Ft extern int
@ -627,7 +608,23 @@ If the passed address is
.Pq 255.255.255.255 ,
.Dv PPTP
aliasing is disabled.
.Sh 5. Fragment Handling
The functions in this section are used to deal with
incoming fragments.
Outgoing fragments are handled within PacketAliasOut()
by changing the address according to any
applicable mapping set by PacketAliasRedirectAddress(),
or the default aliasing address set by
PacketAliasSetAddress().
Incoming fragments are handled in one of two ways.
If the header of a fragmented IP packet has already
been seen, then all subsequent fragments will be
re-mapped in the same manner the header fragment
was. Fragments which arrive before the header
are saved and then retrieved once the header fragment
has been resolved.
.Ss 5.1 PacketAliasSaveFragment()
.Ft int

35
sys/netinet/libalias/libalias.3
View File

@ -495,24 +495,6 @@ functions. If an invalid pointer is passed to
PacketAliasRedirectDelete(), then a program crash
or unpredictable operation could result, so it is
necessary to be careful using this function.
.Sh 5. Fragment Handling
The functions in this section are used to deal with
incoming fragments.
Outgoing fragments are handled within PacketAliasOut()
by changing the address according to any
applicable mapping set by PacketAliasRedirectAddress(),
or the default aliasing address set by
PacketAliasSetAddress().
Incoming fragments are handled in one of two ways.
If the header of a fragmented IP packet has already
been seen, then all subsequent fragments will be
re-mapped in the same manner the header fragment
was. Fragments which arrive before the header
are saved and then retrieved once the header fragment
has been resolved.
.Ss 4.4 PacketAliasProxyRule()
.Ft int
@ -599,7 +581,6 @@ network will be matched.
This function is usually used to redirect outgoing connections for
internal machines that are not permitted certain types of internet
access, or to restrict access to certain external machines.
.Ss 4.5 PacketAliasPptp()
.Ft extern int
@ -627,7 +608,23 @@ If the passed address is
.Pq 255.255.255.255 ,
.Dv PPTP
aliasing is disabled.
.Sh 5. Fragment Handling
The functions in this section are used to deal with
incoming fragments.
Outgoing fragments are handled within PacketAliasOut()
by changing the address according to any
applicable mapping set by PacketAliasRedirectAddress(),
or the default aliasing address set by
PacketAliasSetAddress().
Incoming fragments are handled in one of two ways.
If the header of a fragmented IP packet has already
been seen, then all subsequent fragments will be
re-mapped in the same manner the header fragment
was. Fragments which arrive before the header
are saved and then retrieved once the header fragment
has been resolved.
.Ss 5.1 PacketAliasSaveFragment()
.Ft int