upstream/opnsense-src
1
0
Fork 0
mirror of https://github.com/opnsense/src.git synced 2026-02-18 18:20:26 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

ipfw.8: fix documentation bug for setmark

Browse source 
A mark set with "setmark" keyword is intended to be "sticky"
and documented as such but in fact it is not yet,
as current implementation lacks "sticky" feature
and its implementation will be not MFC'd, most probably.

Correct the manual page until the implementation improved.

Discussed with:	Boris Lytochkin <lytboris@gmail.com> (author)

(cherry picked from commit a7b8a5d37bcb0009297962137bfb6c6570e5af12)
(cherry picked from commit 9fdf49e8a501047b61a615ab1b4b133159ad76e1)
This commit is contained in:
Eugene Grosbein 2025-12-29 00:05:22 +07:00 committed by Franco Fichtner
parent a325b21530
commit b8efad09a0
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
sbin/ipfw/ipfw.8
View file

@ -801,8 +801,12 @@ When a packet matches a rule with the
.Cm setmark
keyword, a 32-bit numeric mark is assigned to the packet.
The mark is an extension to the tags.
As tags, mark is "sticky" so the value is kept the same within the kernel and
is lost when the packet leaves the kernel.
The mark is preserved for a packet within a single ipfw ruleset traversal
and is lost when the packet is checked against the active ruleset
next time (see
.Sx PACKET FLOW
section) or leaves ipfw context (e.g. accepted,
diverted, bridged or routed).
Unlike tags, mark can be matched as a lookup table key or compared with bitwise
mask applied against another value.
Each packet can have only one mark, so