View | Details | Raw Unified | Return to bug 51006
Collapse All | Expand All

(-)divert.4 (-2 / +2 lines)
Lines 50-57 Link Here
50 
the interface on which the packet was received (if the packet
 50 
the interface on which the packet was received (if the packet
51 
was incoming) or
 51 
was incoming) or
52 
.Dv INADDR_ANY
 52 
.Dv INADDR_ANY
53 
(if the packet was outgoing). In the case of an incoming packet the interface
 53 
(if the packet was outgoing). Incoming interface name (if defined
54 
name will also be placed in the 8 bytes following the address,
 54 
for the packet) will also be placed in the 8 bytes following the address,
55 
(assuming it fits).
 55 
(assuming it fits).
56 
.Sh WRITING PACKETS
 56 
.Sh WRITING PACKETS
57 
Writing to a divert socket is similar to writing to a raw IP socket;
 57 
Writing to a divert socket is similar to writing to a raw IP socket;
(-)ipfw.8 (-2 / +4 lines)
Lines 2018-2026 Link Here
2018 
This may be fixed in a later version.
 2018 
This may be fixed in a later version.
2019 
.Pp
 2019 
.Pp
2020 
Packets diverted to userland, and then reinserted by a userland process
 2020 
Packets diverted to userland, and then reinserted by a userland process
2021 
may lose various packet attributes. Packet source interface name
2022 
will be preserved (assuming it is shorter than 8 bytes) if userland process
2023 
saves and reuses the sockaddr_in
2021 
(such as
 2024 
(such as
2022 
.Xr natd 8 )
 2025 
.Xr natd 8 ), otherwise it may be lost.
2023 
will lose various packet attributes, including their source interface.
2024 
If a packet is reinserted in this manner, later rules may be incorrectly
 2026 
If a packet is reinserted in this manner, later rules may be incorrectly
2025 
applied, making the order of
 2027 
applied, making the order of
2026 
.Cm divert
 2028 
.Cm divert

Return to bug 51006