Correct to match reality regarding interface names.

PR:		51006
Submitted by:	"Dmitry Pryanishnikov" <dmitry@atlantis.dp.ua>
mdoc clue by:	"Simon L. Nielsen" <simon@nitro.dk>
MFC after:	10 days
This commit is contained in:
Daniel Harris 2003-07-08 13:24:42 +00:00
parent d47b06fccf
commit a10c9747dc
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=117334
2 changed files with 11 additions and 6 deletions

View File

@ -2119,9 +2119,13 @@ going through the rule list.
This may be fixed in a later version.
.Pp
Packets diverted to userland, and then reinserted by a userland process
(such as
.Xr natd 8 )
will lose various packet attributes, including their source interface.
may lose various packet attributes.
The packet source interface name
will be preserved if it is shorter than 8 bytes and the userland process
saves and reuses the sockaddr_in
(as does
.Xr natd 8 ) ;
otherwise, it may be lost.
If a packet is reinserted in this manner, later rules may be incorrectly
applied, making the order of
.Cm divert

View File

@ -50,9 +50,10 @@ and the IP address set to the (first) address of
the interface on which the packet was received (if the packet
was incoming) or
.Dv INADDR_ANY
(if the packet was outgoing). In the case of an incoming packet the interface
name will also be placed in the 8 bytes following the address,
(assuming it fits).
(if the packet was outgoing).
The interface name (if defined
for the packet) will be placed in the 8 bytes following the address,
if it fits.
.Sh WRITING PACKETS
Writing to a divert socket is similar to writing to a raw IP socket;
the packet is injected ``as is'' into the normal kernel IP packet