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

Document the existence of comments in ipfw rules,

Browse Source 
the new flags handled when reading from a file,
and clarify that only numeric values are allowed for icmptypes.

MFC after: 3 days
This commit is contained in:
Luigi Rizzo 2003-07-12 07:01:48 +00:00
parent 62ff38ae06
commit 7d3f835703
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=117470
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
sbin/ipfw/ipfw.8
View File

@ -15,7 +15,7 @@
.Nm
.Op Fl acdeftnNS
.Brq Cm list | show
.Op Ar number ...
.Op Ar rule | first-last ...
.Nm
.Op Fl f | q
.Cm flush
@ -54,7 +54,7 @@
.Op Ar number ...
.Pp
.Nm
.Op Fl nq
.Op Fl cNnqS
.Oo
.Fl p Ar preproc
.Oo
@ -855,6 +855,12 @@ operand, and possibly grouped into
.Pp
The following match patterns can be used (listed in alphabetical order):
.Bl -tag -width indent
.It Cm // this is a comment.
Inserts the specified text as a comment in the rule.
Everything following // is considered as a comment and stored in the rule.
You can have comment-only rules, which are listed as having a
.Cm count
action followed by the comment.
.It Cm bridged
Matches only bridged packets.
.It Cm dst-ip Ar ip-address
@ -879,8 +885,9 @@ may be specified by name or number.
.It Cm icmptypes Ar types
Matches ICMP packets whose ICMP type is in the list
.Ar types .
The list may be specified as any combination of ranges or
individual types separated by commas.
The list may be specified as any combination of
individual types (numeric) separated by commas.
.Em Ranges are not allowed.
The supported ICMP types are:
.Pp
echo reply