User's Manual - Verizon

Appendix A Quality of Service
Set Priority - Activate this check box to add a priority to the rule. The screen
will refresh, allowing a selection of one of eight priority levels, zero being the
lowest and seven the highest (each priority level is mapped to low/medium/high
priority). This sets the priority of a packet on the connection matching the rule,
while routing the packet.
Log Packets Matched by This Rule - Check this check box to log the first packet
from a connection that was matched by this rule.
When should this rule occur? - By default, the rule will always be active.
However, scheduler rules can be configured to define time periods during which
the rule is active. To learn how to configure scheduler rules, see the “Advanced
Settings” chapter.
☞ Note:
Ingress Data
The hierarchy of the class rules is determined by the addition
order to the class. For example, if the first rule is “match
packets with any source address, any destination address, and
any protocol to this class,” all packets traveling through Router
will be associated with the specific class. Any rules defined later
will not have any effect.
The Router can control outgoing data fairly easily. It can queue packets, delay them,
give precedence to other packets, or drop them. This helps in resolving upload (Tx)
traffic bottlenecks, and in most cases is sufficient. However, in the case of download
(Rx) traffic bottlenecks, the ability to control the flow is much more limited. The
Router cannot queue packets, since in most cases the local network (LAN) is much
faster then the Internet (WAN), and when the Router receives a packet from the
Internet, it passes it immediately to the local network.
QoS for ingress data has the following limitations, which do not exist for
outgoing data:
• QoS can only be applied to TCP streams (UDP streams cannot be delayed)
• No borrowing mechanism
• When reserving Rx bandwidth, it is strictly taken from the bandwidth of all
other classes
155