Jump to content

Template:Networking rutos manual traffic shaping: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 226: Line 226:


==QoS==
==QoS==
<b>QoS</b> provides the possibility to prioritize network traffic based on hosts, ports or services and limit download & upload speeds on a selected interface.
This chapter of the user manual provides an overview of the <b>QoS</b> page in {{{name}}} devices.


<u><b>Note:</b> QoS is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
<u><b>Note:</b> QoS is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>


===Interfaces===
----
The <b>Interfaces</b> section is used to set up download and upload speed limits on the device's network interfaces.
[[File:Networking_rutos_manual_traffic_shaping_qos_interfaces.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
    <td>Calculate overhead</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Decreases upload and download ratio to prevent link saturation.</td>
    </tr>
    <tr>
      <td>Download speed (kbit/s)</td>
      <td>integer; default: <b>1024</b></td>
      <td>Maximum download speed for the specified interface.</td>
    </tr>
    <tr>
    <td>Upload speed (kbit/s)</td>
        <td>integer; default: <b>128</b></td>
        <td>Maximum upload speed for the specified interface.</td>
    </tr>
    <tr>
    <td>Enable</td>
        <td>yes | no; default: <b>no</b></td>
        <td>Turns the rule on or off.</td>
    </tr>
</table>
===Classification Rules===
----
The <b>Classification Rules</b> section is used to configure rules that prioritize
certain traffic over other, less important traffic. This traffic can be defined by
a source or destination host, port or a network protocol. Traffic that matches a
rule with higher preference will be handled with higher priority.
Generally, this should be used in cases where you want to isolate certain types
of traffic in order to make sure the {{{name}}} is handling more important traffic
(for example, video streaming, SSH) at a higher priority and less important traffic (FTP, HTTP) at a lower priority.
[[File:Networking_rutos_manual_traffic_shaping_qos_classification_rules.png|border|class=tlt-border]]


<!-- add qos description -->
<table class="nd-mantable">
    <tr>
        <th>Field</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Target</td>
      <td>Priority | Express | Normal | Bulk; default: <b>Normal</b></td>
      <td>Defines the priority of handling the type of traffic defined in this rule.</td>
    </tr>
    <tr>
      <td>Source host</td>
      <td>All | IP; default: <b>All</b></td>
      <td>Host(s) from which data will be transmitted.</td>
    </tr>
    <tr>
    <td>Destination host</td>
        <td>All | IP; default: <b>All</b></td>
        <td>Host(s) to which data will be transmitted.</td>
    </tr>
    <tr>
    <td>Protocol</td>
        <td>All | TCP | UDP | ICMP | -- custom --; default: <b>All</b></td>
        <td>Data transmission protocol to match the rule.</td>
    </tr>
    <tr>
    <td>Ports</td>
        <td>All | integer [0..65535]; default: <b>none</b></td>
        <td>Port number(s) to match the rule. You can enter multiple ports by separating them by commas (e.g., <i>22,53,80</i>).</td>
    </tr>
</table>


[[Category:{{{name}}} Services section]]
[[Category:{{{name}}} Services section]]