
©2016 Cradlepoint. All Rights Reserved.
|
+1.855.813.3385
|
cradlepoint.com
41
User Manual
/
IBR350
5/6/16
•
High
•
Higher
•
Highest
Click
Finish
to save this queue.
Rules
A traffic shaping rule identifies a specific message flow and assigns that flow to one of the queues created
above.
Click
Add
to create a new Traffic Shaping rule.
Traffic Shaping / QoS Rule Editor
The first page of the Traffic Shaping / QoS Rule Editor allows you enable/disable the rule, name the rule, specify
a protocol for the rule, and select a queue to associate the rule with.
Rule Enabled
: (Default: Enabled.) Deselect
this to disable this rule. This can be useful for
quickly changing configurations. If both upload
QoS and download QoS are disabled then the
rule will disable automatically.
Rule Name
: Create a name for the rule that is
meaningful to you.
Protocol
: The protocol used by the messages:
TCP/UDP, TCP, UDP, or ICMP. Select “Any” if your
rule does not control a specific type of message
that uses a specific protocol.
Queue Name
: Select a queue to associate this
rule with.
Click
Next
to continue to the next page.
Use ports and/or IP addresses to define the
type(s) of traffic attached to this rule. Leaving
any field blank will match all values; all fields
are optional.
Source Port(s) and/or Destination Port(s)
: Enter
a port number between 1 and 65535. To enter
a single port number, input the number into
the left box. To enter a range of ports, fill in
both boxes separated by the colon. For example
“80:90” would represent all ports between 80
and 90 including 80 and 90 themselves.
Source IP Address, Source Netmask,
Destination IP Address, and Destination
Netmask
: Specify an IP address or range of IP
addresses by combining an IP address with a
netmask for either “source” or “destination”
(or both). Source vs. destination is defined by
traffic flow. Leave these blank to include all IP
addresses (such as if your rule is defined by a
particular port instead).