Справочник Пользователя для SonicWALL 5.8.1

The following table describes the behavior of each action on both methods of marking:

None

When packets match-
ing this class of traffic 
(as defined by the 
Access Rule) are sent 
out the egress inter-
face, no 802.1p tag 
will be added.

The DSCP tag is explicitly set (or 
reset) to 0.

If the target interface for this class 
of traffic is a VLAN subinterface, 
the 802.1p portion of the 802.1q 
tag will be explicitly set to 0. If this 
class of traffic is destined for a 
VLAN and is using 802.1p for prior-
itization, a specific Access Rule 
using the Preserve, Explicit, or 
Map action should be defined for 
this class of traffic. 

Preserve

Existing 802.1p tag 
will be preserved.

Existing DSCP tag value will be pre-
served.

Explicit

An explicit 802.1p tag 
value can be 
assigned (0-7) from a 
drop-down menu that 
will be presented.

An explicit DSCP tag value can be 
assigned (0-63) from a drop-down 
menu that will be presented.

If either the 802.1p or the DSCP 
action is set to Explicit while the 
other is set to Map, the explicit 
assignment occurs first, and then 
the other is mapped according to 
that assignment.

Map

The mapping setting 
defined in the Fire-
wall Settings > QoS 
Mapping page will be 
used to map from a 
DSCP tag to an 
802.1p tag.

The mapping setting defined in the 
Firewall Settings > QoS Mapping 
page will be used to map from an 
802.1 tag to a DSCP tag. An additional 
checkbox will be presented to Allow 
802.1p Marking to override DSCP 
values. Selecting this checkbox will 
assert the mapped 802.1p value over 
any DSCP value that might have been 
set by the client. This is useful to over-
ride clients setting their own DSCP 
CoS values.

If Map is set as the action on both 
DSCP and 802.1p, mapping will 
only occur in one direction: if the 
packet is from a VLAN and arrives 
with an 802.1p tag, then DSCP will 
be mapped from the 802.1p tag; if 
the packet is destined to a VLAN, 
then 802.1p will be mapped from 
the DSCP tag.