Changes

Template:Networking rutos manual firewall (view source)

Revision as of 11:51, 19 May 2022

1,065 bytes added ,  11:51, 19 May 2022
no edit summary
Line 1: Line 1: −
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
−
| fw_version = {{{series}}}_R_00.02.06
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
−
| series    = {{{series}}}
+
| series = {{{series}}}
 +
| name  = {{{name}}}
 +
}}
 
}}
 
}}
 +
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Firewall (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
 +
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Firewall (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
 
==Summary==
 
==Summary==
   Line 17: Line 21:  
The <b>General Settings</b> section is used to configure the main policies of the device's firewall. The figure below is an example of the General Settings section and the table below provides information on the fields contained in that section:
 
The <b>General Settings</b> section is used to configure the main policies of the device's firewall. The figure below is an example of the General Settings section and the table below provides information on the fields contained in that section:
   −
[[File:Networking_rutos_manual_firewall_general_settings_general_settings_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_firewall_general_settings_general_settings.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 24: Line 28:  
         <th>Value</th>
 
         <th>Value</th>
 
         <th>Description</th>
 
         <th>Description</th>
−
    </tr>
  −
    <tr>
  −
      <td>Enable SYN flood protection</td>
  −
      <td>off | on; default: <b>on</b></td>
  −
      <td>Enables protection from SYN flood type attacks. A SYN flood is a type of denial-of-service (DOS) attack where an attacker sends bursts of SYN requests in an attempt to make the target host machine consume enough resources and become unresponsive.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 42: Line 41:  
     <tr>
 
     <tr>
 
       <td>Input</td>
 
       <td>Input</td>
−
       <td>Reject | Drop | Accept; default: <b>Accept</b></td>
+
       <td>Reject | Drop | Accept; default: <b>Reject</b></td>
 
       <td>Default action<span class="asterisk">*</span> of the INPUT chain if a packet does not match any existing rule on that chain.</td>
 
       <td>Default action<span class="asterisk">*</span> of the INPUT chain if a packet does not match any existing rule on that chain.</td>
 
     </tr>
 
     </tr>
Line 63: Line 62:  
     <li><b>Reject</b> – packet is stopped, deleted and, differently from Drop, a message of rejection is sent to the source from which the packet came.</li>
 
     <li><b>Reject</b> – packet is stopped, deleted and, differently from Drop, a message of rejection is sent to the source from which the packet came.</li>
 
</ul>
 
</ul>
 +
 +
===Routing/NAT Offloading===
 +
----
 +
The <b>Routing/NAT Offloading</b> is used to turns software flow offloading on or off.
 +
 +
The device checks whether the flow (sequence of related packets) is of a received a packed is known. Packets of unknown flow are forwarded to the networking stack. Meanwhile, if the flow is known, NAT is applied (if matched) and the packet is forwarded to the correct destination port. This process is called <b>software flow offloading</b>.
 +
 +
[[File:Networking_rutos_manual_firewall_general_settings_routing_nat_offloading.png|border|class=tlt-border]]
 +
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
        <th>Value</th>
 +
        <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
        <td>Software flow offloading</td>
 +
        <td>off {{!}} on; default: <b>off</b></td>
 +
        <td>Turns software flow offloading on or off.</td>
 +
    </tr>
 +
</table>
    
===Zones===
 
===Zones===
Line 123: Line 143:  
====Zones: Advanced Settings====
 
====Zones: Advanced Settings====
 
----
 
----
−
[[File:Networking_rutos_manual_firewall_general_settings_zones_advanced_settings_v2.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_firewall_general_settings_zones_advanced_settings_v3.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 218: Line 238:  
         <td>string; default: <b>none</b></td>
 
         <td>string; default: <b>none</b></td>
 
         <td>Name of the rule. This is used for easier management purposes.</td>
 
         <td>Name of the rule. This is used for easier management purposes.</td>
−
    </tr>
  −
    <tr>
  −
        <td>Protocol</td>
  −
        <td>TCP+UDP | TCP | UDP | Other; default: <b>TCP+UDP</b></td>
  −
        <td>Specifies to which protocols the rule should apply.</td>
  −
    </tr>
  −
    <tr>
  −
        <td>External zone</td>
  −
        <td>firewall zone name; default: '''wan'''</td>
  −
        <td>The zone to which hosts will be connecting.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 233: Line 243:  
         <td>integer [0..65535] | range of integers [0..65534] - [1..65535]; default: <b>none</b></td>
 
         <td>integer [0..65535] | range of integers [0..65534] - [1..65535]; default: <b>none</b></td>
 
         <td>The port number to which hosts will be connecting.<td>
 
         <td>The port number to which hosts will be connecting.<td>
−
    </tr>
  −
    <tr>
  −
        <td>Internal zone</td>
  −
        <td>firewall zone name; default: '''lan'''</td>
  −
        <td>The zone to which the incoming connection will be redirected.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 259: Line 264:  
You will be redirected to that rule's configuration page:
 
You will be redirected to that rule's configuration page:
   −
[[File:Networking_rutos_manual_firewall_port_forwards_configuration_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]
+
[[File:Networking_rutos_manual_firewall_port_forwards_configuration.png|border|class=tlt-border]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 290: Line 295:  
         <td>Source MAC address</td>
 
         <td>Source MAC address</td>
 
         <td>mac; default: <b>none</b></td>
 
         <td>mac; default: <b>none</b></td>
−
         <td>MAC address(es) of connecting hosts.<br>The rule will apply only to hosts that match MAC addresses specified in this field. Leave empty to make the rule skip MAC address matching.</td>
+
         <td>MAC address of connecting hosts.<br>The rule will apply only to hosts that match MAC addresses specified in this field. Leave empty to make the rule skip MAC address matching.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 378: 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 472: Line 482:  
===Open Ports on Router===
 
===Open Ports on Router===
 
----
 
----
−
The <b>Open Ports on Router</b> section provides a quick way to set simple rules that allow traffic on specified ports of the device. The figure below is an example of the Open ports on device section and the table below provides information on the fields contained in that section:
+
In the <b>Add new instance</b> section, select <b>Open ports on router</b>. This provides a quick way to set simple rules that allow traffic on specified ports of the device. The figure below is an example of the Open ports on device section and the table below provides information on the fields contained in that section:
    
[[File:Networking_rutos_manual_firewall_traffic_rules_open_ports_on_router.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_firewall_traffic_rules_open_ports_on_router.png|border|class=tlt-border]]
Line 501: Line 511:  
===Add New Forward Rule===
 
===Add New Forward Rule===
 
----
 
----
−
The <b>Add New Forward Rule</b> section is used to create firewall rules that control traffic on the FORWARD chain. The figure below is an example of the Add New Forward Rule section and the table below provides information on the fields contained in that section:
+
In the <b>Add new instance</b> section, select <b>Add new forward rule</b>. This is used to create firewall rules that control traffic on the FORWARD chain. The figure below is an example of the Add New Forward Rule section and the table below provides information on the fields contained in that section:
    
[[File:Networking_rutos_manual_firewall_traffic_rules_add_new_forward_rule.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_firewall_traffic_rules_add_new_forward_rule.png|border|class=tlt-border]]
Line 704: Line 714:  
     </tr>
 
     </tr>
 
</table>
 
</table>
−
  −
==Custom rules==
  −
  −
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 figure below is an example of the Custom rules tab:
  −
  −
[[File:Networking_rutos_manual_firewall_custom_rules.png|border|class=tlt-border]]
  −
  −
The rules added here are saved in the <b>/etc/firewall.user</b> file. Feel free to edit that file instead for the same effect in case you don't have access to the device's WebUI.
  −
  −
The <b>Save</b> button restarts the firewall service. Thus, adding the custom rules specified in this section to the device's list of firewall rules.
  −
  −
The <b>Reset</b> button resets the custom rules field to its default state.
      
==Attack Prevention==
 
==Attack Prevention==
Line 776: Line 772:  
     <tr>
 
     <tr>
 
       <td>Enable ICMP limit</td>
 
       <td>Enable ICMP limit</td>
−
       <td>off | on; default: <b>no</b></td>
+
       <td>off | <span style="color: #1550bf;">on</span>; default: <b>off</b></td>
 
       <td>Turns ICMP echo-request limit in selected period on or off.</td>
 
       <td>Turns ICMP echo-request limit in selected period on or off.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
     <td>Limit period</td>
+
     <td><span style="color: #1550bf;">Limit period</span></td>
 
         <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
 
         <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
 
       <td>Period length for matching the conditions of the rule.</td>
 
       <td>Period length for matching the conditions of the rule.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
     <td>Limit</td>
+
     <td><span style="color: #1550bf;">Limit</span></td>
 
         <td>integer; default: <b>5</b></td>
 
         <td>integer; default: <b>5</b></td>
 
         <td>Maximum ICMP echo-request number during the period.</td>
 
         <td>Maximum ICMP echo-request number during the period.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
−
     <td>Limit burst</td>
+
     <td><span style="color: #1550bf;">Limit burst</span></td>
 
         <td>integer; default: <b>10</b></td>
 
         <td>integer; default: <b>10</b></td>
 
         <td>Indicates the maximum burst before the above limit kicks in.</td>
 
         <td>Indicates the maximum burst before the above limit kicks in.</td>
Line 954: Line 950:  
     </tr>
 
     </tr>
 
</table>
 
</table>
 +
 +
==Custom Rules==
 +
 +
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:
 +
 +
[[File:Networking_rutos_manual_firewall_custom_rules.png|border|class=tlt-border]]
 +
 +
The rules added here are saved in the <b>/etc/firewall.user</b> file. Feel free to edit that file instead for the same effect in case you don't have access to the device's WebUI.
 +
 +
The <b>Save</b> button restarts the firewall service. Thus, adding the custom rules specified in this section to the device's list of firewall rules.
 +
 +
The <b>Reset</b> button resets the custom rules field to its default state.
    
[[Category:{{{name}}} Network section]]
 
[[Category:{{{name}}} Network section]]
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/77824...91569"

Navigation menu