Setup guide

burst-time (text; default: 0) - for how long the burst is allowed
Notes
max-limit must be equal or greater than limit-at.
To apply queues on flows, the mangle feature should be used first to mark incomming packets.
The router tries to apply queue trees before simple queues.
Example
To mark all the traffic going from web-servers (TCP port 80) with abc-http mark:
[admin@Wandy] ip firewall mangle> add action=passthrough mark-flow=abc-http \
\... protocol=tcp target-port=80
[admin@Wandy] ip firewall mangle> print
Flags: X - disabled, I - invalid, D - dynamic
0 target-address=:80 protocol=tcp action=passthrough mark-flow=abc-http
[admin@Wandy] ip firewall mangle>
You can add queue using the /queue tree add command:
[admin@Wandy] queue tree> add name=HTTP parent=ether1 flow=abc-http \
max-limit=128000
[admin@Wandy] queue tree> print
Flags: X - disabled, I - invalid, D - dynamic
0 name="HTTP" parent=ether1 flow=abc-http limit-at=0 queue=default
priority=8 max-limit=128000 burst-limit=0 burst-threshold=0
burst-time=0
[admin@Wandy] queue tree>
Troubleshooting
Description
• The queue is not added for the correct interface
Add the queue to the interface through which the traffic is leaving the router. Queuing works
only for packets leaving the router!
• The source/destination addresses of the packets do not match the values specified in the
queue setting
Make sure the source and destination addresses, as well as network masks are specified
correctly! The most common mistake is wrong address/netmask, e.g., 10.0.0.217/24 (wrong),
10.0.0.217/32 (right), or 10.0.0.0/24 (right)
• The priority setting does not work!
In order to take the priority setting in account, you have to specify limit-at parameter.
Otherwise This setting will be ignored or will not work correctly
Queue Applications
Description
One of the ways to avoid network traffic jams is usage of traffic shaping in large networks. Traffic
shaping and data rate allocation is implemented in the Wandy RouterOS as queuing mechanism.