User's Manual

EnRoute500 User’s Guide
TR0149 Rev. C5
84
13 Quality of Service (QoS) Configuration
The EnRoute500 has extensive support for quality of service settings that allow traffic to be
prioritized based on the source interface, destination interface, and type of traffic. The
EnRoute500 QoS scheme allows both rate limiting and rate reservation for all interfaces.
13.1 Priority Levels
The available priority levels are listed in Table 14.
Abbreviation Description Priority level
VO Voice 4 (highest)
VI Video 3
BE Best Effort 2
BK Background 1 (lowest)
Table 14. Priority levels
When sending data out through any of the wireless interfaces (wlanN, mesh0), these priorities
map directly to the hardware priority output queues on the wireless card if the receiver has
802.11e support, as the EnRoute500 does. The default level is Best Effort.
Priority levels are set with the following CLI parameters in the ‘qos’ interface:
in.<intf>.hwpri{max,min}
in.<intf>.flow_priority
where <intf> is one of the following: default, local, eth0, mesh0, wlan1, wlan2, wlan3, wlan4.
‘local’ refers to traffic originating on the node itself, not from its clients (in practice this means
mesh network control traffic).
Flow priorities can be set via the web interface under the “QoS” tab on the “QoS” page (see
Figure 43).
The ‘in.<intf>.flow_priority’ parameters set the relative priority of outbound traffic based on the
source interface. These parameters can be set to a value in the range from 0 to 99, with a
higher number indicating a higher priority. If a priority level parameter is set to ‘inherit’, the
interface will assume the default priority level of ‘in.default.flow_priority’.
Traffic originating from an interface with a higher priority will take priority over traffic from all
interfaces with a lower priority value until the higher-priority interface has no more data to
send. If multiple interfaces have the same priority level, their traffic will be given equal access