Changes

no edit summary
Line 2: Line 2:  
| fw_version ={{Template: Networking_rutos_manual_latest_fw
 
| fw_version ={{Template: Networking_rutos_manual_latest_fw
 
  | series = {{{series}}}
 
  | series = {{{series}}}
 +
| name  = {{{name}}}
 
  }}
 
  }}
 
}}
 
}}
Line 382: Line 383:  
     <tr>
 
     <tr>
 
     <td>Protocol</td>
 
     <td>Protocol</td>
         <td>TCP+UDP | TCP | UDP | ICMP | -- custom --; default: <b>TCP+UDP</b></td>
+
         <td>TCP+UDP | TCP | UDP | <span style="color:red">ICMP</span> | -- custom --; default: <b>TCP+UDP</b></td>
 
         <td>Specifies to which protocols the rule should apply.</td>
 
         <td>Specifies to which protocols the rule should apply.</td>
 +
    </tr>
 +
    <tr>
 +
        <td><span style="color:red"> Match ICMP type</span></td>
 +
        <td>-- Custom -- | Any | ICMP-type; default: '''none'''</td>
 +
        <td>Allows matching specific ICMP types.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 948: Line 954:     
The <b>Custom rules</b> tab provides you with the possibility to execute <b>iptables</b> commands which are not otherwise covered by the device's firewall framework. The commands are executed after each firewall restart, right after the default rule set has been loaded.
 
The <b>Custom rules</b> tab provides you with the possibility to execute <b>iptables</b> commands which are not otherwise covered by the device's firewall framework. The commands are executed after each firewall restart, right after the default rule set has been loaded.
 +
 +
<b>Note: </b> Custom rules are not recommended to be used with <i>hostnames</i>. The rules will not remain active after reboot due to security reasons.
    
The figure below is an example of the Custom rules tab:
 
The figure below is an example of the Custom rules tab:

Navigation menu