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

ipfw(8): clarify layer2 processing abilities

Browse Source 
Make it clear that ipfw action set for layer2 frames it a bit limited.

PR:			59835
Reviewed by:		yuripv
MFC after:		1 month
Differential Revision:	https://reviews.freebsd.org/D17719
This commit is contained in:
eugen 2018-11-04 06:35:48 +00:00
parent b899eb149b
commit 65b1156d8d
1 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
sbin/ipfw/ipfw.8
View File

@ -511,6 +511,27 @@ ipfw add 10 skipto 4000 all from any to any layer2 out
.Pp
(yes, at the moment there is no way to differentiate between
ether_demux and bdg_forward).
.Pp
Also note that only actions
.Cm allow,
.Cm deny,
.Cm netgraph,
.Cm ngtee
and related to
.Cm dummynet
are processed for
.Cm layer2
frames and all other actions act as if they were
.Cm allow
for such frames.
Full set of actions is supported for IP packets without
.Cm layer2
headers only.
For example,
.Cm divert
action does not divert
.Cm layer2
frames.
.Sh SYNTAX
In general, each keyword or argument must be provided as
a separate command line argument, with no leading or trailing