Changes

no edit summary
Line 1: Line 1:  
{{Template: Networking_rutxxx_manual_fw_disclosure
 
{{Template: Networking_rutxxx_manual_fw_disclosure
 
| fw_version = {{#switch: {{{series}}}
 
| fw_version = {{#switch: {{{series}}}
   | RUT2XX = {{{series}}}_R_00.01.12
+
   | RUT2XX = {{{series}}}_R_00.01.13
   | RUT9XX = {{{series}}}_R_00.06.06}}
+
   | RUT9XX = {{{series}}}_R_00.06.07}}
 
}}
 
}}
 
__TOC__
 
__TOC__
Line 25: Line 25:  
     <tr>
 
     <tr>
 
       <td>Interface</td>
 
       <td>Interface</td>
       <td>WAN | LAN | WiFi_WAN | Mobile; default: <b>none</b></td>
+
       <td>WAN | LAN | WiFi_WAN | Mobile</td>
 
       <td>Interface to which the rule applies.</td>
 
       <td>Interface to which the rule applies.</td>
 
     </tr>
 
     </tr>
Line 45: Line 45:  
     <tr>
 
     <tr>
 
     <td>Upload speed (kbit/s)</td>
 
     <td>Upload speed (kbit/s)</td>
         <td>integer; default: <b>128</b></td>
+
         <td>integer; default: <b>none</b></td>
         <td>Maximum upload speed for the specified interface,</td>
+
         <td>Maximum upload speed for the specified interface.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 52: Line 52:  
==Classification Rules==
 
==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.
+
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 device (this {{{name}}}) is handling more important traffic (for example, video streaming, SSH) at a higher priority and less important traffic (FTP, HTTP) a lower 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:Services qos classification rules.PNG|border|class=tlt-border]]
 
[[File:Services qos classification rules.PNG|border|class=tlt-border]]
Line 71: Line 76:  
     <tr>
 
     <tr>
 
       <td>Source host</td>
 
       <td>Source host</td>
       <td>All | ip; default: <b>All</b></td>
+
       <td>All | IP; default: <b>All</b></td>
 
       <td>Host(s) from which data will be transmitted.</td>
 
       <td>Host(s) from which data will be transmitted.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Destination host</td>
 
     <td>Destination host</td>
         <td>All | ip; default: <b>All</b></td>
+
         <td>All | IP; default: <b>All</b></td>
         <td>Host(s) to which data will be transmitted</td>
+
         <td>Host(s) to which data will be transmitted.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 86: Line 91:  
     <tr>
 
     <tr>
 
     <td>Ports</td>
 
     <td>Ports</td>
         <td>All | integer [0..65535]; default: <b>All</b></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>
 
         <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>
 
     </tr>

Navigation menu