Template:Networking rutos manual firewall: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
(43 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Template:Networking_rutos_manual_fw_disclosure
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05
| 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==
{{{name}}} devices use a standard Linux iptables package as its <b>firewall</b>, which uses routing chains and policies to facilitate control over inbound and outbound traffic.


{{{name}}} devices use a standard Linux iptables package as its <b>firewall</b>, which uses routing chains and policies to facilitate control over inbound and outbound traffic. This chapter is an overview of the Firewall section for {{{name}}} devices.
This chapter of the user manual provides an overview of the Firewall page for {{{name}}} devices.


{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
Line 12: Line 17:
}}
}}


==General settings==
==General Settings==


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:
Line 25: Line 30:
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable SYN flood protection</td>
       <td>Drop invalid packets</td>
       <td>off | on; Default: <b>on</b></td>
       <td>off | on; default: <b>off</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>
       <td>If enabled, a "Drop" action will be performed on packets that are determined to be invalid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Drop invalid packets</td>
       <td>Automatic helper assignment</td>
       <td>off | on; Default: <b>off</b></td>
       <td>off | on; default: <b>on</b></td>
       <td>If enabled, a "Drop" action will be performed on packets that are determined to be invalid.</td>
       <td>Automatically assigns conntrack helpers based on traffic protocol and port. If turned off, conntrack helpers can be selected for each zone.</td>
     </tr>
     </tr>
     <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>
     <tr>
     <tr>
     <td>Output</td>
     <td>Output</td>
         <td>Reject | Drop | Accept; Default: <b>Accept</b></td>
         <td>Reject | Drop | Accept; default: <b>Accept</b></td>
         <td>Default action<span class="asterisk">*</span> of the OUTPUT chain if a packet does not match any existing rule on that chain.</td>
         <td>Default action<span class="asterisk">*</span> of the OUTPUT chain if a packet does not match any existing rule on that chain.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Forward</td>
     <td>Forward</td>
         <td>Reject | Drop | Accept; Default: <b>Reject</b></td>
         <td>Reject | Drop | Accept; default: <b>Reject</b></td>
         <td>Default action<span class="asterisk">*</span> of the FORWARD chain if a packet does not match any existing rule on that chain.</td>
         <td>Default action<span class="asterisk">*</span> of the FORWARD chain if a packet does not match any existing rule on that chain.</td>
     </tr>
     </tr>
Line 57: 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 68: Line 94:
[[File:Networking_rutos_manual_firewall_general_settings_zones_edit_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_general_settings_zones_edit_button.png|border|class=tlt-border]]


====Zones: general settings====
====Zones: General Settings====
----
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_general_settings.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_general_settings_zones_general_settings.png|border|class=tlt-border]]
Line 85: Line 111:
     <tr>
     <tr>
         <td>Input</td>
         <td>Input</td>
       <td>Reject | Drop | Accept; Default: <b>Accept</b></td>
       <td>Reject | Drop | Accept; default: <b>Accept</b></td>
         <td>Default policy for traffic entering the zone.</td>
         <td>Default policy for traffic entering the zone.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Output</td>
         <td>Output</td>
       <td>Reject | Drop | Accept; Default: <b>Accept</b></td>
       <td>Reject | Drop | Accept; default: <b>Accept</b></td>
         <td>Default policy for traffic originating from and leaving the zone.</td>
         <td>Default policy for traffic originating from and leaving the zone.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Forward</td>
         <td>Forward</td>
       <td>Reject | Drop | Accept; Default: <b>Reject</b></td>
       <td>Reject | Drop | Accept; default: <b>Reject</b></td>
         <td>Default policy for traffic forwarded between the networks belonging to the zone.</td>
         <td>Default policy for traffic forwarded between the networks belonging to the zone.</td>
     </tr>
     </tr>
Line 115: Line 141:
</table>
</table>


====Zones: advanced settings====
====Zones: Advanced Settings====
----
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_advanced_settings.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 147: Line 173:
     <tr>
     <tr>
         <td>Enable logging on this zone</td>
         <td>Enable logging on this zone</td>
         <td>off | <span style="color: red;">on</span>; default: <b>off</b></td>
         <td>off | <span style="color: #1550bf; font-weight: bold;">on</span>; default: <b>off</b></td>
         <td>Logs packets that hit this rule.</td>
         <td>Logs packets that hit this rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><span style="color: red;">Limit log messages</span></td>
         <td><span style="color: #1550bf;">Limit log messages</span></td>
         <td>integer/minute; default: <b>none</b></td>
         <td>integer/minute; default: <b>none</b></td>
         <td>Limit how many messages can be logged in the span of 1 minute. For example, to log 50 packets per minute use: <i>50/minute</i>.</td>
         <td>Limit how many messages can be logged in the span of 1 minute. For example, to log 50 packets per minute use: <i>50/minute</i>.</td>
    </tr>
    <tr>
        <td>Conntrack helpers</td>
        <td> Amanda backup and archiving proto (AMANDA) | FTP passive connection tracking (FTP) | RAS proto tracking (RAS) | Q.931 proto tracking (Q.931) | IRC DCC connection tracking (IRC) | NetBIOS name service broadcast tracking (NETBIOS-NS) | PPTP VPN connection tracking (PPTP) | SIP VoIP connection tracking (SIP) | SNMP monitoring connection tracking (SNMP) | TFTP connection tracking (TFTP); default: <b>none</b></td>
        <td><b>This option appears only when automatic helper assignment option in the firewall's general settings is disabled. </b>Explicitly choses allowed connection tracking helpers for zone traffic.</td>
     </tr>
     </tr>
</table>
</table>


====Zones: inter-zone forwarding====
====Zones: Inter-zone Forwarding====
----
----
The <b>Inter-zone forwarding</b> options control the forwarding policies between the currently edited zone and other zones.  
The <b>Inter-zone forwarding</b> options control the forwarding policies between the currently edited zone and other zones.  
Line 181: Line 212:
</table>
</table>


==Port forwards==
==Port Forwards==


<b>Port forwarding</b> is a way of redirecting an incoming connection to another IP address, port or the combination of both:  
<b>Port forwarding</b> is a way of redirecting an incoming connection to another IP address, port or the combination of both:  
Line 189: Line 220:
The Port forwards table displays configured port forwarding rules currently configured on the device.
The Port forwards table displays configured port forwarding rules currently configured on the device.


[[File:Networking_rutos_manual_firewall_port_forwards_port_forwards.png]]
[[File:Networking_rutos_manual_firewall_port_forwards_port_forwards.png|border|class=tlt-border]]


===New port forward===
===Add New Port Forward===
----
----
The <b>New port forward</b> section is used to quickly add additional port forwarding rules. The figure below is an example of the New port forward section and the table below provides information on the fields contained in that section:
The <b>Add New Port Forward</b> section is used to quickly add additional port forwarding rules. The figure below is an example of the Add New Port Forward section and the table below provides information on the fields contained in that section:


[[File:Networking_rutos_manual_firewall_port_forwards_add_new_port_forward.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_port_forwards_add_new_port_forward.png|border|class=tlt-border]]
Line 207: 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 222: 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 240: Line 256:
</table>
</table>


===Port forwards configuration===
===Port Forwards Configuration===
----
----
While the New port forward section provides the possibility to add port forwarding rules fast, it does not contain all possible configuration options to customize a rule. In order to create a more complicated rule, add one using the New port forward section and click the button that looks like a pencil [[File:Networking_rutx_trb14x_manual_edit_button_v1.png|20px]] next to it:
While the New port forward section provides the possibility to add port forwarding rules fast, it does not contain all possible configuration options to customize a rule. In order to create a more complicated rule, add one using the New port forward section and click the button that looks like a pencil [[File:Networking_rutx_trb14x_manual_edit_button_v1.png|20px]] next to it:


[[File:Networking_rutx_manual_firewall_port_forwards_edit_v1.png]]
[[File:Networking_rutos_manual_firewall_port_forwards_edit_button.png|border|class=tlt-border]]


You will be redirected to that rule's configuration page:
You will be redirected to that rule's configuration page:
{{#ifeq:{{{mobile}}}| 1|
 
[[File:Networking_rutx_manual_firewall_port_forwards_configuration_v1.png]]
[[File:Networking_rutos_manual_firewall_port_forwards_configuration.png|border|class=tlt-border]]
|
 
[[File:Networking_rutx08_10_manual_firewall_port_forwards_configuration_v1.png]]
}}
<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
Line 275: Line 289:
     <tr>
     <tr>
         <td>Source zone</td>
         <td>Source zone</td>
         <td>firewall zone name; default: '''wan'''</td>
         <td>firewall zone name; default: <b>wan</b></td>
         <td>The zone to which the third party will be connecting. (Same thing as "External zone" in the New port forward section.)</td>
         <td>The zone to which the third party will be connecting. (Same thing as "External zone" in the New port forward section.)</td>
     </tr>
     </tr>
Line 281: 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 305: Line 319:
     <tr>
     <tr>
         <td>Internal zone</td>
         <td>Internal zone</td>
         <td>firewall zone name; default: '''lan'''</td>
         <td>firewall zone name; default: <b>lan</b></td>
         <td>The zone to which the incoming connection will be redirected.</td>
         <td>The zone to which the incoming connection will be redirected.</td>
     </tr>
     </tr>
Line 330: Line 344:
</table>
</table>


==Traffic rules==
==Traffic Rules==


The <b>Traffic rules</b> tab is used to set firewall rules that filter traffic moving through the device. The figure below is an example of the Traffic rules table:
The <b>Traffic rules</b> tab is used to set firewall rules that filter traffic moving through the device. The figure below is an example of the Traffic rules table:


[[File:Networking_rutx_manual_firewall_traffic_rules_v1.png]]
[[File:Networking_rutos_manual_firewall_traffic_rules.png|border|class=tlt-border]]


===Traffic rules configuration===
===Traffic Rule Configuration===
----
----
In order to begin editing a traffic rule, click the button that looks like a pencil [[File:Networking_rutx_trb14x_manual_edit_button_v1.png|20px]] next to it:
In order to begin editing a traffic rule, click the button that looks like a pencil [[File:Networking_rutx_trb14x_manual_edit_button_v1.png|20px]] next to it:


[[File:Networking_rutx_manual_firewall_traffic_rules_edit_v1.png]]
[[File:Networking_rutos_manual_firewall_traffic_rules_edit_button.png|border|class=tlt-border]]


You will be redirected to that rule's configuration page:
You will be redirected to that rule's configuration page:


[[File:Networking_rutx09_rutx11_manual_firewall_traffic_rules_configuration_v1.png]]
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 354: Line 368:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off | on; Default <b>on</b></td>
       <td>off | on; default <b>on</b></td>
       <td>Turns the rule on or off.</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Name</td>
       <td>Name</td>
       <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>
     <tr>
     <tr>
       <td>Restrict to address family</td>
       <td>Restrict to address family</td>
       <td>IPv4 and IPv6 | IPv4 only | IPv6 only; Default: <b>IPv4 and IPv6</b></td>
       <td>IPv4 and IPv6 | IPv4 only | IPv6 only; default: <b>IPv4 and IPv6</b></td>
       <td>IP address family to which the rule will apply to.</td>
       <td>IP address family to which the rule will apply to.</td>
     </tr>
     </tr>
     <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 394: Line 413:
     <tr>
     <tr>
     <td>Destination zone</td>
     <td>Destination zone</td>
         <td>firewall zone; Default: <b>Device (input)</b></td>
         <td>firewall zone; default: <b>Device (input)</b></td>
         <td>Target zone of the incoming connection.</td>
         <td>Target zone of the incoming connection.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Destination address</td>
     <td>Destination address</td>
         <td>ip | ip/netmask; Default: <b>any</b></td>
         <td>ip | ip/netmask; default: <b>any</b></td>
         <td>Tagert IP address or network segment of the incoming connection.</td>
         <td>Tagert IP address or network segment of the incoming connection.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Destination port</td>
     <td>Destination port</td>
         <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>Tagert port or range of ports of the incoming connection.</td>
         <td>Tagert port or range of ports of the incoming connection.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Action</td>
     <td>Action</td>
         <td>DROP | ACCEPT | REJECT; Default: <b>ACCEPT</b></td>
         <td>Drop | Accept | Reject | Don't track; default: <b>Accept</b></td>
         <td>Action that is to be taken when a packet meets the MATCH conditions.
         <td>Action that is to be taken when a packet matches the conditions of the rule.
             <ul>
             <ul>
                 <li><b>ACCEPT</b> – packet gets to continue to the next chain.</li>
                 <li><b>Drop</b> – packet is stopped and deleted.</li>
                 <li><b>DROP</b> – packet is stopped and deleted.</li>
                 <li><b>Accept</b> – packet gets to continue to the next chain.</li>
                 <li><b>REJECT</b> – packet is stopped, deleted and, differently from Drop, an ICMP packet containing a message of rejection is sent to the source from which the dropped packet came.</li>
                 <li><b>Reject</b> – packet is stopped, deleted and, differently from Drop, an ICMP packet containing a message of rejection is sent to the source from which the dropped packet came.</li>
                <li><b>Don't track</b> – packet is no longer tracked as it moves forward.</li>
             </ul>
             </ul>
         </td>
         </td>
Line 420: Line 440:
     <tr>
     <tr>
     <td>Extra arguments</td>
     <td>Extra arguments</td>
         <td>string; Default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
         <td>Adds extra .iptables options to the rule.</td>
         <td>Adds extra .iptables options to the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Week days</td>
     <td>Week days</td>
         <td>days of the week [Sunday..Saturday]; Default: <b>none</b></td>
         <td>days of the week [Sunday..Saturday]; default: <b>none</b></td>
         <td>Specifies on which days of the week the rule is valid.</td>
         <td>Specifies on which days of the week the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Month days</td>
     <td>Month days</td>
         <td>days of the month [1..31]; Default: <b>none</b></td>
         <td>days of the month [1..31]; default: <b>none</b></td>
         <td>Specifies on which days of the month the rule is valid.</td>
         <td>Specifies on which days of the month the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Start Time (hh:mm:ss)</td>
     <td>Start Time (hh:mm:ss)</td>
         <td>time [0..23:0..59:0..59]; Default: <b>none</b></td>
         <td>time [0..23:0..59:0..59]; default: <b>none</b></td>
         <td>Indicates the beginning of the time period during which the rule is valid.</td>
         <td>Indicates the beginning of the time period during which the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Stop Time (hh:mm:ss)</td>
     <td>Stop Time (hh:mm:ss)</td>
         <td>time [0..23:0..59:0..59]; Default: <b>none</b></td>
         <td>time [0..23:0..59:0..59]; default: <b>none</b></td>
         <td>Indicates the end of the time period during which the rule is valid.</td>
         <td>Indicates the end of the time period during which the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Start Date (yyyy-mm-dd)</td>
     <td>Start Date (yyyy-mm-dd)</td>
         <td>date [0000..9999:1..12:1..31]; Default: <b>none</b></td>
         <td>date [0000..9999:1..12:1..31]; default: <b>none</b></td>
         <td>Indicates the first day of the date of the period during which the rule is valid.</td>
         <td>Indicates the first day of the date of the period during which the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Stop Date (yyyy-mm-dd)</td>
     <td>Stop Date (yyyy-mm-dd)</td>
         <td>date [0000..9999:1..12:1..31]; Default: <b>none</b></td>
         <td>date [0000..9999:1..12:1..31]; default: <b>none</b></td>
         <td>Indicates the last day of the date of the period during which the rule is valid.</td>
         <td>Indicates the last day of the date of the period during which the rule is valid.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Time in UTC</td>
     <td>Time in UTC</td>
         <td>yes | no; Default: <b>no</b></td>
         <td>off | on; default: <b>no</b></td>
         <td>Specifies whether the device should use UTC time. If this is disabled, the time zone specified in the <b>[[{{{name}}}<nowiki> NTP|NTP]]</nowiki></b> section will be used.</td>
         <td>Specifies whether the device should use UTC time. If this is disabled, the time zone specified in the Services → [[{{{name}}} NTP|NTP]] page will be used.</td>
     </tr>
     </tr>
</table>
</table>


 
===Open Ports on Router===
===Open ports on device===
----
----
The <b>Open ports on device</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_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_traffic_rules_open_ports_on_router.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 475: Line 494:
     <tr>
     <tr>
       <td>Name</td>
       <td>Name</td>
       <td>string; Default: <b>none</b></td>
       <td>string; default: <b>none</b></td>
       <td>The name of the rule. This is used for easier management purposes.<br>The name field is filled automatically when port numbers are specified, unless the name was specified beforehand by the user.</td>
       <td>The name of the rule. This is used for easier management purposes.<br>The name field is filled automatically when port numbers are specified, unless the name was specified beforehand by the user.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Protocol</td>
     <td>Protocol</td>
         <td>TCP+UDP | TCP | UDP | Other; Default: <b>TCP+UDP</b></td>
         <td>TCP+UDP | TCP | UDP | Other; 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>
     <tr>
     <tr>
     <td>External port</td>
     <td>External port</td>
         <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>Specifies which port(s) should be opened.</td>
         <td>Specifies which port(s) should be opened.</td>
     </tr>
     </tr>
</table>
</table>


===New forward rule===
===Add New Forward Rule===
----
----
The <b>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 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_rutx_manual_firewall_traffic_rules_new_forward_rule_v1.png]]
[[File:Networking_rutos_manual_firewall_traffic_rules_add_new_forward_rule.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 504: Line 523:
     <tr>
     <tr>
       <td>Name</td>
       <td>Name</td>
       <td>string; Default: <b>none</b></td>
       <td>string; default: <b>none</b></td>
       <td>The name of the rule. This is used for easier management purposes.</td>
       <td>The name of the rule. This is used for easier management purposes.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Source zone</td>
     <td>Source zone</td>
         <td>firewall zone; Default: <b>WAN</b></td>
         <td>firewall zone; default: <b>wan</b></td>
         <td>The zone from which traffic has originated.</td>
         <td>The zone from which traffic has originated.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Destination zone</td>
     <td>Destination zone</td>
         <td>firewall zone; Default: <b>LAN</b></td>
         <td>firewall zone; default: <b>lan</b></td>
         <td>The zone to which traffic will be forwarded to.</td>
         <td>The zone to which traffic will be forwarded to.</td>
     </tr>
     </tr>
Line 523: Line 542:
     </tr>
     </tr>
</table>
</table>
==NAT Rules==
<b>Network address translation</b> (<b>NAT</b>) is method of modifying the source/destination address and/or port information in a packet's IP header.


===Source NAT===
===Source NAT===
----
----
<b>Source NAT</b> is a specific form of masquerading which allows fine grained control over the source IP used for outgoing traffic. For example, to map multiple WAN addresses to internal subnets.
<b>Source NAT</b> (<b>SNAT</b>) is a form of masquerading used to change a packet's source address and/or port number to a static, user-defined value. SNAT is performed in the POSTROUTING chain, just before a packet leaves the device.
 
The Source NAT section displays currently existing SNAT rules.
 
[[File:Networking_rutos_manual_firewall_nat_rules_source_nat.png|border|class=tlt-border]]


====New source NAT====
===Add New Source NAT===
----
----
The <b>New Source NAT</b> section is used to add custom source NAT rules. The figure below is an example of the New source NAT section and the table below provides information on the fields contained in that section:
The <b>Add New Source NAT</b> section is used to create new source NAT rules.


[[File:Networking_rutx_manual_firewall_traffic_rules_source_nat_new_source_nat_v1.png| border | class=tlt-border| 1102x1102px]]
[[File:Networking_rutos_manual_firewall_nat_rules_add_new_source_nat.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 542: Line 569:
     <tr>
     <tr>
       <td>Name</td>
       <td>Name</td>
       <td>string; Default: <b>none</b></td>
       <td>string; default: <b>none</b></td>
       <td>The name of the rule. This is used for easier management purposes.</td>
       <td>The name of the rule. Used only for easier management purposes.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Source zone</td>
     <td>Source zone</td>
         <td>firewall zone; Default: <b>LAN</b></td>
         <td>firewall zone; default: <b>lan</b></td>
         <td>The zone from which traffic has originated.</td>
         <td>Matches traffic originated from the specified zone.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Destination zone</td>
     <td>Destination Zone</td>
         <td>firewall zone; Default: <b>WAN</b></td>
         <td>firewall zone; default: <b>wan</b></td>
         <td>The zone to which traffic will be forwarded to.</td>
         <td>Matches traffic destined for the specified zone.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>To source IP</td>
     <td>To source IP</td>
         <td>ip | do not rewrite; Default: <b>Do not rewrite</b></td>
         <td>ip | do not rewrite; default: <b>none</b></td>
         <td>Changes the source IP in the packet header to the value specified in this field.</td>
         <td>Changes the source IP address in the packet header to the value specified in this field.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>To source port</td>
     <td>To Source Port</td>
         <td>integer [0..65335] | do not rewrite; Default: <b>Do not rewrite</b></td>
         <td>integer [0..65335] | do not rewrite; default: <b>none</b></td>
         <td>Changes the source port in the packet header to the value specified in this field.</td>
         <td>Changes the source port in the packet header to the value specified in this field.</td>
     </tr>
     </tr>
Line 568: Line 595:
     <td>Add</td>
     <td>Add</td>
         <td>- (interactive button)</td>
         <td>- (interactive button)</td>
         <td>Creates the rule and redirects you to the rule's configuration page.</td>
         <td>Creates the rule in accordance with the given parameter and redirects you to the rule's configuration page.</td>
     </tr>
     </tr>
</table>
</table>


==Custom rules==
===Source NAT Configuration===
----
In order to begin editing a traffic rule, click the button that looks like a pencil [[File:Networking_rutx_trb14x_manual_edit_button_v1.png|20px]] next to it:


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.
{{#ifeq: {{{series}}} | TRB1
| [[File:Networking_trb1_manual_firewall_nat_rules_source_nat_edit_button.png|border|class=tlt-border]]
| [[File:Networking_rutos_manual_firewall_nat_rules_source_nat_edit_button.png|border|class=tlt-border]]
}}


The figure below is an example of the Custom rules tab:
You will be redirected to that rule's configuration page:
 
[[File:Networking_rutx_manual_firewall_custom_rules_v1.png]]
 
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.
{{#ifeq: {{{series}}} | RUTX|
==NAT helpers==


The <b>NAT Helpers</b> section provides you with the possibility to add firewall exceptions for some VoIP protocols, namely SIP and H.323. In other words, these functions provide a pass-through for VoIP communications between the device's LAN and WAN.
[[File:Networking_rutos_manual_firewall_nat_rules_configuration_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]
 
<b>Technical explanation:</b>
 
FTP, SIP and H.323 protocols are harder to filter by firewalls since they violate layering by introducing OSI layer 3/4 parameters in the OSI layer 7. NAT helpers are modules that are able to assist the firewall in tracking these protocols. These helpers create the so-called expectations that can be used to open necessary ports for RELATED connections. For example, FTP, GRE and PPTP helpers are enabled by default.
 
[[File:Networking_rutx_manual_firewall_nat_helpers_v1.png]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 603: Line 619:
     </tr>
     </tr>
     <tr>
     <tr>
       <td>H323</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; Default: <b>off</b></td>
       <td>off | on; default <b>on</b></td>
      <td>Turns H323 filtering on or off.</td>
      <td>Turns the rule on or off.</td>
    </tr>
    <tr>
      <td>Name</td>
      <td>string; default <b>none</b></td>
      <td>Name of the rule. This is used for easier management purposes.</td>
    </tr>
    <tr>
    <td>Protocol</td>
        <td>All protocols | TCP+UDP | TCP | UDP | ICMP | -- custom --; default: <b>All protocols</b></td>
        <td>Specifies to which protocols the rule should apply.</td>
    </tr>
    <tr>
    <td>Source zone</td>
        <td>firewall zone; default: <b>lan</b></td>
        <td>Matches traffic originated from the specified zone.</td>
    </tr>
    <tr>
        <td>Source IP address</td>
        <td>ip | ip/netmask; default: <b>Any</b></td>
        <td>Mathes traffic originated from specified IP address or network segment.</td>
    </tr>
    <tr>
        <td>Source port</td>
        <td>integer [0..65535] | range of integers [0..65534] - [1..65535]; default: <b>none</b></td>
        <td>Mathes traffic originated from specified port number.<td>
    </tr>
    <tr>
    <td>Destination zone</td>
        <td>firewall zone; default: <b>wan</b></td>
        <td>Matches traffic destined for the specified zone.</td>
    </tr>
    <tr>
    <td>Destination IP address</td>
        <td>ip | ip/netmask; default: <b>any</b></td>
        <td>Matches traffic destined for the specified IP address or network segment.</td>
    </tr>
    <tr>
    <td>Destination port</td>
        <td>integer [0..65535] | range of integers [0..65534] - [1..65535]; default: <b>none</b></td>
        <td>Matches traffic destined for the specified port number.</td>
    </tr>
    <tr>
        <td>SNAT address</td>
        <td>ip; default: <b>none</b></td>
        <td>Changes matched traffic packet source IP address to the value specified in this field.</td>
    </tr>
    <tr>
        <td>SNAT port</td>
        <td>integer [0..65535] | range of integers [0..65534] - [1..65535]; default: <b>none</b></td>
        <td>Changes matched traffic packet source port number to the value specified in this field.</td>
    </tr>
    <tr>
    <td>Extra arguments</td>
        <td>string; default: <b>none</b></td>
        <td>Adds extra .iptables options to the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
      <td>SIP</td>
    <td>Week days</td>
      <td>off <nowiki>|</nowiki> on; Default: <b>off</b></td>
        <td>days of the week [Sunday..Saturday]; default: <b>none</b></td>
      <td>Turns SIP filtering on or off.</td>
        <td>Specifies on which days of the week the rule is valid.</td>
    </tr>
    <tr>
    <td>Month days</td>
        <td>days of the month [1..31]; default: <b>none</b></td>
        <td>Specifies on which days of the month the rule is valid.</td>
    </tr>
    <tr>
    <td>Start Time (hh:mm:ss)</td>
        <td>time [0..23:0..59:0..59]; default: <b>none</b></td>
        <td>Indicates the beginning of the time period during which the rule is valid.</td>
    </tr>
    <tr>
    <td>Stop Time (hh:mm:ss)</td>
        <td>time [0..23:0..59:0..59]; default: <b>none</b></td>
        <td>Indicates the end of the time period during which the rule is valid.</td>
    </tr>
    <tr>
    <td>Start Date (yyyy-mm-dd)</td>
        <td>date [0000..9999:1..12:1..31]; default: <b>none</b></td>
        <td>Indicates the first day of the date of the period during which the rule is valid.</td>
    </tr>
    <tr>
    <td>Stop Date (yyyy-mm-dd)</td>
        <td>date [0000..9999:1..12:1..31]; default: <b>none</b></td>
        <td>Indicates the last day of the date of the period during which the rule is valid.</td>
    </tr>
    <tr>
    <td>Time in UTC</td>
        <td>off | on; default: <b>no</b></td>
        <td>Specifies whether the device should use UTC time. If this is disabled, the time zone specified in the Services → [[{{{name}}} NTP|NTP]] page will be used.</td>
     </tr>
     </tr>
</table>
</table>
}}


==Attack Prevention==
==Attack Prevention==
The <b>Attack Prevention</b> menu tab provides the possibility to configure protections against certain types of online attacks.


===SYN Flood Protection===
===SYN Flood Protection===
----
----
'''SYN Flood Protection''' allows you to protect yourself from attacks that exploit part of the normal TCP three-way handshake to consume resources on the targeted server and render it unresponsive. Essentially, with SYN flood DDOS, the offender sends TCP connection requests faster than the targeted machine can process them, causing network over-saturation.
<b>SYN Flood Protection</b> allows you to protect yourself from attacks that exploit part of the normal TCP three-way handshake to consume resources on the targeted server and render it unresponsive. Essentially, with SYN flood DDOS, the offender sends TCP connection requests faster than the targeted machine can process them, causing network over-saturation.


[[File:Networking_rutos_manual_firewall_attack_prevention_syn.PNG|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_attack_prevention_syn_flood_protection.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable SYN flood protection</td>
       <td>Enable SYN flood protection</td>
       <td>yes | no; Default: '''yes'''</td>
       <td>off | on; default: <b>on</b></td>
       <td>Toggles the rule ON or OFF</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>SYN flood rate</td>
       <td>SYN flood rate</td>
       <td>integer; Default: '''5'''</td>
       <td>integer; default: <b>5</b></td>
       <td>Set rate limit (packets per second) for SYN packets above which the traffic is considered flooded</td>
       <td>Set rate limit (packets per second) for SYN packets above which the traffic is considered floodedb</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>SYN flood burst</td>
     <td>SYN flood burst</td>
         <td>integer; Default: '''10'''</td>
         <td>integer; default: <b>10</b></td>
         <td>Set burst limit for SYN packets above which the traffic is considered flooded if it exceeds the allowed rate</td>
         <td>Sets burst limit for SYN packets above which the traffic is considered flooded if it exceeds the allowed ratbe</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>TCP SYN cookies</td>
     <td>TCP SYN cookies</td>
         <td>yes | no; Default: '''no'''</td>
         <td>off | on; default: <b>off<b></b></td>
         <td>Enable the use of SYN cookies (particular choices of initial TCP sequence numbers by TCP servers)</td>
         <td>Enables the use of SYN cookies (particular choices of initial TCP sequence numbers by TCP servers)b</td>
     </tr>
     </tr>
</table>
</table>
Line 653: Line 755:
===Remote ICMP Requests===
===Remote ICMP Requests===
----
----
Some attackers use '''ICMP echo''' request packets directed to IP broadcast addresses from remote locations to generate denial-of-service attacks. You can set up some custom restrictions to help protect your router from ICMP bursts.  
Some attackers use <b>ICMP echo request</b> packets directed to IP broadcast addresses from remote locations to generate denial-of-service attacks. You can set up some custom restrictions to help protect your router from ICMP bursts.  
 
[[File:Networking_rutos_manual_firewall_attack_prevention_icmp.PNG|border|class=tlt-border]]


[[File:Networking_rutos_manual_firewall_attack_prevention_remote_icmp_requests.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable ICMP requests</td>
       <td>Enable ICMP requests</td>
       <td>yes | no; Default: '''yes'''</td>
       <td>off | on; default: <b>on</b></td>
       <td>Toggles the rule ON or OFF</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable ICMP limit</td>
       <td>Enable ICMP limit</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | <span style="color: #1550bf;">on</span>; default: <b>off</b></td>
       <td>Toggles 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: '''Second'''</td>
         <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
        <td>Select ICMP echo-request period limit</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: '''5'''</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: '''10'''</td>
         <td>integer; default: <b>10</b></td>
         <td>Indicate the maximum burst before the above limit kicks in</td>
         <td>Indicates the maximum burst before the above limit kicks in.</td>
     </tr>
     </tr>
</table>
</table>
Line 693: Line 794:
===SSH Attack Prevention===
===SSH Attack Prevention===
----
----
Prevent SSH (allows a user to run commands on a machine's command prompt without them being physically present near the machine) attacks by limiting connections in a defined period.
This protection prevent <b>SSH attacks</b> by limiting connections in a defined period.
 
[[File:Networking_rutos_manual_firewall_attack_prevention_ssh.PNG|border|class=tlt-border]]


[[File:Networking_rutos_manual_firewall_attack_prevention_ssh_attack_prevention.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable SSH limit</td>
       <td>Enable SSH limit</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles the rule ON or OFF</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Limit period</td>
       <td>Limit period</td>
       <td>Second | Minute | Hour | Day; Default: '''Second'''</td>
       <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
       <td>The period in which SSH connections are to be limited</td>
       <td>Period length for matching the conditions of the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit</td>
     <td>Limit</td>
         <td>integer; Default: '''5'''</td>
         <td>integer; default: <b>5</b></td>
         <td>Maximum SSH connections during the set period</td>
         <td>Maximum SSH connections during the set period</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit burst</td>
     <td>Limit burst</td>
         <td>integer; Default: '''10'''</td>
         <td>integer; default: <b>10</b></td>
         <td>Indicate the maximum burst before the above limit kicks in</td>
         <td>Indicates the maximum burst before the above limit kicks in.</td>
     </tr>
     </tr>
</table>
</table>
Line 728: Line 828:
===HTTP Attack Prevention===
===HTTP Attack Prevention===
----
----
An HTTP attack sends a complete, legitimate HTTP header, which includes a 'Content-Length' field to specify the size of the message body to follow. However, the attacker then proceeds to send the actual message body at an extremely slow rate (e.g. 1 byte/100 seconds.) Due to the entire message being correct and complete, the target server will attempt to obey the 'Content-Length' field in the header, and wait for the entire body of the message to be transmitted, hence slowing it down.
An <b>HTTP attack</b> sends a complete, legitimate HTTP header, which includes a 'Content-Length' field to specify the size of the message body to follow. However, the attacker then proceeds to send the actual message body at an extremely slow rate (e.g. 1 byte/100 seconds.) Due to the entire message being correct and complete, the target server will attempt to obey the 'Content-Length' field in the header, and wait for the entire body of the message to be transmitted, hence slowing it down.
 
[[File:Networking_rutos_manual_firewall_attack_prevention_http.PNG|border|class=tlt-border]]


[[File:Networking_rutos_manual_firewall_attack_prevention_http_attack_prevention.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable HTTP limit</td>
       <td>Enable HTTP limit</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles the rule ON or OFF</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Limit period</td>
       <td>Limit period</td>
       <td>Second | Minute | Hour | Day; Default: '''Second'''</td>
       <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
       <td>The period in which HTTP connections are to be limited</td>
       <td>Period length for matching the conditions of the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit</td>
     <td>Limit</td>
         <td>integer; Default: '''5'''</td>
         <td>integer; default: <b>5</b></td>
         <td>Maximum HTTP connections during the set period</td>
         <td>Maximum HTTP connections during the set period<./td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit burst</td>
     <td>Limit burst</td>
         <td>integer; Default: '''10'''</td>
         <td>integer; default: <b>10</b></td>
         <td>Indicate the maximum burst before the above limit kicks in</td>
         <td>Indicates the maximum burst before the above limit kicks in.</td>
     </tr>
     </tr>
</table>
</table>
Line 763: Line 862:
===HTTPS Attack Prevention===
===HTTPS Attack Prevention===
----
----
This section allows you to enable protection against '''HTTPS''' attacks, also known as '''man-in-the-middle attacks''' ('''MITM''').
This section allows you to enable protection against <b>HTTPS attacks</b>, also known as "man-in-the-middle" attacks (MITM).


In cryptography and computer security, a man-in-the-middle attack (MITM) is an attack where the perpetrator secretly relays and possibly alters the communication between two parties who believe they are directly communicating with each other. One example of man-in-the-middle attacks is active eavesdropping, in which the attacker makes independent connections with the victims and relays messages between them to make them believe they are talking directly to each other over a private connection, when in fact the entire conversation is controlled by the attacker.
In cryptography and computer security, a man-in-the-middle attack (MITM) is an attack where the perpetrator secretly relays and possibly alters the communication between two parties who believe they are directly communicating with each other. One example of man-in-the-middle attacks is active eavesdropping, in which the attacker makes independent connections with the victims and relays messages between them to make them believe they are talking directly to each other over a private connection, when in fact the entire conversation is controlled by the attacker.


[[File:Networking_rutos_manual_firewall_attack_prevention_hhtps.PNG|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_attack_prevention_https_attack_prevention.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable HTTPS limit</td>
       <td>Enable HTTPS limit</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles the rule ON or OFF</td>
       <td>Turns the rule on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Limit period</td>
       <td>Limit period</td>
       <td>Second | Minute | Hour | Day; Default: '''Second'''</td>
       <td>Second | Minute | Hour | Day; default: <b>Second</b></td>
       <td>The period in which HTTPS connections are to be limited</td>
       <td>Period length for matching the conditions of the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit</td>
     <td>Limit</td>
         <td>integer; Default: '''5'''</td>
         <td>integer; default: <b>5</b></td>
         <td>Maximum HTTPS connections during the set period</td>
         <td>Maximum HTTPS connections during the set period.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Limit burst</td>
     <td>Limit burst</td>
         <td>integer; Default: '''10'''</td>
         <td>integer; default: <b>10</b></td>
         <td>Indicate the maximum burst before the above limit kicks in</td>
         <td>Indicates the maximum burst number before the above limit kicks in.</td>
     </tr>
     </tr>
</table>
</table>


==Port Scan Prevention==
===Port Scan===
 
----
Port scan attacks scan which of the targeted host's ports are open. Network ports are the entry points to a machine that is connected to the Internet. A service that listens on a port is able to receive data from a client application, process it and send a response back. Malicious clients can sometimes exploit vulnerabilities in the server code so they gain access to sensitive data or execute malicious code on the machine remotely.
<b>Port Scan</b> attacks scan which of the targeted host's ports are open. Network ports are the entry points to a machine that is connected to the Internet. A service that listens on a port is able to receive data from a client application, process it and send a response back. Malicious clients can sometimes exploit vulnerabilities in the server code so they gain access to sensitive data or execute malicious code on the machine remotely.
Port scanning is usually done in the initial phase of a penetration test in order to discover all network entry points into the target system. The Port Scan section provides you with the possibility to enable protection against port scanning software. The Defending Type section provides the possibility for the user to enable protections from certain types of online attacks. These include '''SYN-FIN''', '''SYN-RST''', '''X-Mas''', '''FIN scan''' and '''NULLflags''' attacks.
Port scanning is usually done in the initial phase of a penetration test in order to discover all network entry points into the target system. The Port Scan section provides you with the possibility to enable protection against port scanning software. The Defending Type section provides the possibility for the user to enable protections from certain types of online attacks. These include <b>SYN-FIN</b>, <b>SYN-RST</b>, <b>X-Mas</b>, <b>FIN scan</b> and <b>NULLflags</b> attacks.
 


[[File:Networking_rutos_manual_firewall_attack_prevention_port_scan_def.PNG|border|class=tlt-border]]
[[File:Networking_rutos_manual_firewall_attack_prevention_port_scan.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
     <tr>
     <tr>
         <th>field name</th>
         <th>Field</th>
       <th>value</th>
       <th>Value</th>
       <th>description</th>
       <th>Description</th>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles the function ON or OFF</td>
       <td>Turns the function on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Scan count</td>
     <td>Scan count</td>
         <td>integer [5..65534]; Default: '''5'''</td>
         <td>integer [5..65534]; default: <b>5</b></td>
         <td>How many port scans before blocked</td>
         <td>How many port scans before blocked.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Interval</td>
       <td>Interval</td>
       <td>integer [10..60]; Default: '''10'''</td>
       <td>integer [10..60]; default: <b>10</b></td>
       <td>Time interval in seconds in which port scans are counted</td>
       <td>Time interval in seconds in which port scans are counted.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>SYN-FIN attack</td>
       <td>SYN-FIN attack</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles protection from SYN-FIN attacks ON or OFF</td>
       <td>Turns protection from SYN-FIN attacks on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>SYN-RST attack</td>
       <td>SYN-RST attack</td>
       <td>yes | no; Default: '''no'''</td>
       <td>off | on; default: <b>off</b></td>
       <td>Toggles protection from SYN-RST attacks ON or OFF</td>
       <td>Turns protection from SYN-RST attacks on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>X-Mas attack</td>
     <td>X-Mas attack</td>
         <td>yes | no; Default: '''no'''</td>
         <td>off | on; default: <b>off</b></td>
         <td>Toggles protection from X-Mas attacks ON or OFF</td>
         <td>Turns protection from X-Mas attacks on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>FIN scan</td>
     <td>FIN scan</td>
         <td>yes | no; Default: '''no'''</td>
         <td>off | on; default: <b>off</b></td>
         <td>Toggles protection from FIN scan attacks ON or OFF</td>
         <td>Turns protection from FIN scan attacks on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>NULLflags attack</td>
     <td>NULLflags attack</td>
         <td>yes | no; Default: '''no'''</td>
         <td>off | on; default: <b>off</b></td>
         <td>Toggles protection from NULLflags attacks ON or OFF</td>
         <td>Turns protection from NULLflags attacks on or off.</td>
     </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]]

Revision as of 10:51, 19 May 2022

Template:Networking rutos manual fw disclosure


Summary

{{{name}}} devices use a standard Linux iptables package as its firewall, which uses routing chains and policies to facilitate control over inbound and outbound traffic.

This chapter of the user manual provides an overview of the Firewall page for {{{name}}} devices.

If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.

General Settings

The General Settings 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:

Field Value Description
Drop invalid packets off | on; default: off If enabled, a "Drop" action will be performed on packets that are determined to be invalid.
Automatic helper assignment off | on; default: on Automatically assigns conntrack helpers based on traffic protocol and port. If turned off, conntrack helpers can be selected for each zone.
Input Reject | Drop | Accept; default: Reject Default action* of the INPUT chain if a packet does not match any existing rule on that chain.
Output Reject | Drop | Accept; default: Accept Default action* of the OUTPUT chain if a packet does not match any existing rule on that chain.
Forward Reject | Drop | Accept; default: Reject Default action* of the FORWARD chain if a packet does not match any existing rule on that chain.

* When a packet goes through a firewall chain it is matched against all the rules of that specific chain. If no rule matches said packet, an according Action (Drop, Reject or Accept) is performed:

  • Accept – packet gets to continue to the next chain.
  • Drop – packet is stopped and deleted.
  • Reject – packet is stopped, deleted and, differently from Drop, a message of rejection is sent to the source from which the packet came.

Routing/NAT Offloading


The Routing/NAT Offloading 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 software flow offloading.

Field Value Description
Software flow offloading off | on; default: off Turns software flow offloading on or off.

Zones


The Zones section is used to manage default traffic forwarding policies between different device zones. The figure below is an example of the Zones section and the table below provides information on the fields contained in that section:


You can change a zone's settings from this page by interacting with entries in the zones table. For a more in-depth configuration click the button that looks like a pencil next to a zone:

Zones: General Settings


Field Value Description
Name string; default: newzone A custom name for the zone. Used for easier management purposes.
Input Reject | Drop | Accept; default: Accept Default policy for traffic entering the zone.
Output Reject | Drop | Accept; default: Accept Default policy for traffic originating from and leaving the zone.
Forward Reject | Drop | Accept; default: Reject Default policy for traffic forwarded between the networks belonging to the zone.
Masquerading off | on; default: off Turns Masquerading off or on. MASQUERADE is an iptables target that can be used instead of the SNAT (source NAT) target when the external IP of the network interface is not known at the moment of writing the rule (when the interface gets the external IP dynamically).
MSS clamping off | on; default: off Turns MSS clamping off or on. MSS clamping is a workaround used to change the maximum segment size (MSS) of all TCP connections passing through links with an MTU lower than the Ethernet default of 1500.
Covered networks network interface(s); default: none Network or networks that belong to the zone.

Zones: Advanced Settings


Field Value Description
Restrict to address family IPv4 and IPv6 | IPv4 only | IPv6 only; default: IPv4 and IPv6 IP address family to which to rule will apply.
Restrict Masquerading to given source subnets network/subnet; default: none Applies Masquerading only to the specified source network/subnet.
Restrict Masquerading to given destinations subnets network/subnet; default: none Applies Masquerading only to the specified destination network/subnet.
Force connection tracking off | on; default: off Always maintains connection state (NEW, ESTABLISHED, RELATED) information.
Enable logging on this zone off | on; default: off Logs packets that hit this rule.
Limit log messages integer/minute; default: none Limit how many messages can be logged in the span of 1 minute. For example, to log 50 packets per minute use: 50/minute.
Conntrack helpers Amanda backup and archiving proto (AMANDA) | FTP passive connection tracking (FTP) | RAS proto tracking (RAS) | Q.931 proto tracking (Q.931) | IRC DCC connection tracking (IRC) | NetBIOS name service broadcast tracking (NETBIOS-NS) | PPTP VPN connection tracking (PPTP) | SIP VoIP connection tracking (SIP) | SNMP monitoring connection tracking (SNMP) | TFTP connection tracking (TFTP); default: none This option appears only when automatic helper assignment option in the firewall's general settings is disabled. Explicitly choses allowed connection tracking helpers for zone traffic.

Zones: Inter-zone Forwarding


The Inter-zone forwarding options control the forwarding policies between the currently edited zone and other zones.

[[File:Networking_rutos_manual_firewall_general_settings_zones_inter-zone_forwarding_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]

Field Value Description
Allow forward to destination zones zone(s); default: none Allows forward traffic to specified destination zones. Destination zones cover forwarded traffic originating from this source zone.
Allow forward from source zones zone(s); default: none Allows forward traffic to specified source zones. Source zones match forwarded traffic originating from other zones that is targeted at this zone.

Port Forwards

Port forwarding is a way of redirecting an incoming connection to another IP address, port or the combination of both:


The Port forwards table displays configured port forwarding rules currently configured on the device.

Add New Port Forward


The Add New Port Forward section is used to quickly add additional port forwarding rules. The figure below is an example of the Add New Port Forward section and the table below provides information on the fields contained in that section:

Field Value Description
Name string; default: none Name of the rule. This is used for easier management purposes.
External port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none The port number to which hosts will be connecting.
Internal IP address ip; default: none The IP address to which the incoming connection will be redirected.
Internal port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none The port number to which the incoming connection will be redirected.

Port Forwards Configuration


While the New port forward section provides the possibility to add port forwarding rules fast, it does not contain all possible configuration options to customize a rule. In order to create a more complicated rule, add one using the New port forward section and click the button that looks like a pencil next to it:

You will be redirected to that rule's configuration page:

Field Value Description
Enable off | on ; default: on Turns the rule on or off
Name string; default: none Name of the rule. This is used for easier management purposes.
Protocol TCP+UDP | TCP | UDP | Other; default: TCP+UDP Specifies to which protocols the rule should apply.
Source zone firewall zone name; default: wan The zone to which the third party will be connecting. (Same thing as "External zone" in the New port forward section.)
Source MAC address mac; default: none MAC address of connecting hosts.
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.
Source IP address ip | ip/netmask; default: any IP address or network segment used by connecting hosts.
The rule will apply only to hosts that connect from IP addresses specified in this field.
To specify a network segment instead of one IP address, add a forward slash followed by the netmask length after the network indication (for example, 10.0.0.0/8).
Source port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Port number(s) used by the connecting host.
The rule will match the source port used by the connecting host with the port number(s) specified in this field. Leave empty to make the rule skip source port matching.
External IP address ip | ip/netmask; default: any IP address or network segment to which hosts will be connecting.
The rule will apply only to hosts that connect to IP addresses specified in this field.
To specify a subnet instead of one IP, add a forward slash followed by the netmask length after the network indication (for example, 10.0.0.0/8).
External port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Port number(s) to which hosts will be connecting.
The rule will apply only to hosts that connect to the port number(s) specified in this field. Leave empty to make the rule skip external port matching.
Internal zone firewall zone name; default: lan The zone to which the incoming connection will be redirected.
Internal IP address ip; default: none The IP address to which the incoming connection will be redirected.
Internal port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none The port number to which the incoming connection will be redirected.
Enable NAT loopback off | on ; default: on NAT loopback a.k.a. NAT reflection a.k.a. NAT hairpinning is a method of accessing an internal server using a public IP. NAT loopback enables your local network (i.e., behind your NAT device) to connect to a forward-facing IP address of a machine that it also on your local network.
Extra arguments string; default: none Adds extra iptables options to the rule.

Traffic Rules

The Traffic rules tab is used to set firewall rules that filter traffic moving through the device. The figure below is an example of the Traffic rules table:

Traffic Rule Configuration


In order to begin editing a traffic rule, click the button that looks like a pencil next to it:

You will be redirected to that rule's configuration page:

[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]

Field Value Description
Enable off | on; default on Turns the rule on or off.
Name string; default none Name of the rule. This is used for easier management purposes.
Restrict to address family IPv4 and IPv6 | IPv4 only | IPv6 only; default: IPv4 and IPv6 IP address family to which the rule will apply to.
Protocol TCP+UDP | TCP | UDP | ICMP | -- custom --; default: TCP+UDP Specifies to which protocols the rule should apply.
Match ICMP type -- Custom -- | Any | ICMP-type; default: none Allows matching specific ICMP types.
Source zone firewall zone name; default: wan The zone to which the third party will be connecting.
Source MAC address mac; default: none MAC address(es) of connecting hosts.
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.
Source address ip | ip/netmask; default: any IP address or network segment used by connecting hosts.
The rule will apply only to hosts that connect from IP addresses specified in this field.
To specify a network segment instead of one IP address, add a forward slash followed by the netmask length after the network indication (for example, 10.0.0.0/8).
Source port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Port number(s) used by the connecting host.
The rule will match the source port used by the connecting host with the port number(s) specified in this field. Leave empty to make the rule skip source port matching.
Destination zone firewall zone; default: Device (input) Target zone of the incoming connection.
Destination address ip | ip/netmask; default: any Tagert IP address or network segment of the incoming connection.
Destination port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Tagert port or range of ports of the incoming connection.
Action Drop | Accept | Reject | Don't track; default: Accept Action that is to be taken when a packet matches the conditions of the rule.
  • Drop – packet is stopped and deleted.
  • Accept – packet gets to continue to the next chain.
  • Reject – packet is stopped, deleted and, differently from Drop, an ICMP packet containing a message of rejection is sent to the source from which the dropped packet came.
  • Don't track – packet is no longer tracked as it moves forward.
Extra arguments string; default: none Adds extra .iptables options to the rule.
Week days days of the week [Sunday..Saturday]; default: none Specifies on which days of the week the rule is valid.
Month days days of the month [1..31]; default: none Specifies on which days of the month the rule is valid.
Start Time (hh:mm:ss) time [0..23:0..59:0..59]; default: none Indicates the beginning of the time period during which the rule is valid.
Stop Time (hh:mm:ss) time [0..23:0..59:0..59]; default: none Indicates the end of the time period during which the rule is valid.
Start Date (yyyy-mm-dd) date [0000..9999:1..12:1..31]; default: none Indicates the first day of the date of the period during which the rule is valid.
Stop Date (yyyy-mm-dd) date [0000..9999:1..12:1..31]; default: none Indicates the last day of the date of the period during which the rule is valid.
Time in UTC off | on; default: no Specifies whether the device should use UTC time. If this is disabled, the time zone specified in the Services → [[{{{name}}} NTP|NTP]] page will be used.

Open Ports on Router


In the Add new instance section, select Open ports on router. 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:

Field Value Description
Name string; default: none The name of the rule. This is used for easier management purposes.
The name field is filled automatically when port numbers are specified, unless the name was specified beforehand by the user.
Protocol TCP+UDP | TCP | UDP | Other; default: TCP+UDP Specifies to which protocols the rule should apply.
External port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Specifies which port(s) should be opened.

Add New Forward Rule


In the Add new instance section, select Add new forward rule. 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:

Field Value Description
Name string; default: none The name of the rule. This is used for easier management purposes.
Source zone firewall zone; default: wan The zone from which traffic has originated.
Destination zone firewall zone; default: lan The zone to which traffic will be forwarded to.
Add - (interactive button) Creates the rule and redirects you to the rule's configuration page

NAT Rules

Network address translation (NAT) is method of modifying the source/destination address and/or port information in a packet's IP header.

Source NAT


Source NAT (SNAT) is a form of masquerading used to change a packet's source address and/or port number to a static, user-defined value. SNAT is performed in the POSTROUTING chain, just before a packet leaves the device.

The Source NAT section displays currently existing SNAT rules.

Add New Source NAT


The Add New Source NAT section is used to create new source NAT rules.

Field Value Description
Name string; default: none The name of the rule. Used only for easier management purposes.
Source zone firewall zone; default: lan Matches traffic originated from the specified zone.
Destination Zone firewall zone; default: wan Matches traffic destined for the specified zone.
To source IP ip | do not rewrite; default: none Changes the source IP address in the packet header to the value specified in this field.
To Source Port integer [0..65335] | do not rewrite; default: none Changes the source port in the packet header to the value specified in this field.
Add - (interactive button) Creates the rule in accordance with the given parameter and redirects you to the rule's configuration page.

Source NAT Configuration


In order to begin editing a traffic rule, click the button that looks like a pencil next to it:

You will be redirected to that rule's configuration page:

[[File:Networking_rutos_manual_firewall_nat_rules_configuration_mobile_{{{mobile}}}_dualsim_{{{dualsim}}}_wired_{{{wired}}}.png|border|class=tlt-border]]

Field Value Description
Enable off | on; default on Turns the rule on or off.
Name string; default none Name of the rule. This is used for easier management purposes.
Protocol All protocols | TCP+UDP | TCP | UDP | ICMP | -- custom --; default: All protocols Specifies to which protocols the rule should apply.
Source zone firewall zone; default: lan Matches traffic originated from the specified zone.
Source IP address ip | ip/netmask; default: Any Mathes traffic originated from specified IP address or network segment.
Source port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Mathes traffic originated from specified port number.
Destination zone firewall zone; default: wan Matches traffic destined for the specified zone.
Destination IP address ip | ip/netmask; default: any Matches traffic destined for the specified IP address or network segment.
Destination port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Matches traffic destined for the specified port number.
SNAT address ip; default: none Changes matched traffic packet source IP address to the value specified in this field.
SNAT port integer [0..65535] | range of integers [0..65534] - [1..65535]; default: none Changes matched traffic packet source port number to the value specified in this field.
Extra arguments string; default: none Adds extra .iptables options to the rule.
Week days days of the week [Sunday..Saturday]; default: none Specifies on which days of the week the rule is valid.
Month days days of the month [1..31]; default: none Specifies on which days of the month the rule is valid.
Start Time (hh:mm:ss) time [0..23:0..59:0..59]; default: none Indicates the beginning of the time period during which the rule is valid.
Stop Time (hh:mm:ss) time [0..23:0..59:0..59]; default: none Indicates the end of the time period during which the rule is valid.
Start Date (yyyy-mm-dd) date [0000..9999:1..12:1..31]; default: none Indicates the first day of the date of the period during which the rule is valid.
Stop Date (yyyy-mm-dd) date [0000..9999:1..12:1..31]; default: none Indicates the last day of the date of the period during which the rule is valid.
Time in UTC off | on; default: no Specifies whether the device should use UTC time. If this is disabled, the time zone specified in the Services → [[{{{name}}} NTP|NTP]] page will be used.

Attack Prevention

The Attack Prevention menu tab provides the possibility to configure protections against certain types of online attacks.

SYN Flood Protection


SYN Flood Protection allows you to protect yourself from attacks that exploit part of the normal TCP three-way handshake to consume resources on the targeted server and render it unresponsive. Essentially, with SYN flood DDOS, the offender sends TCP connection requests faster than the targeted machine can process them, causing network over-saturation.

Field Value Description
Enable SYN flood protection off | on; default: on Turns the rule on or off.
SYN flood rate integer; default: 5 Set rate limit (packets per second) for SYN packets above which the traffic is considered floodedb
SYN flood burst integer; default: 10 Sets burst limit for SYN packets above which the traffic is considered flooded if it exceeds the allowed ratbe
TCP SYN cookies off | on; default: off Enables the use of SYN cookies (particular choices of initial TCP sequence numbers by TCP servers)b

Remote ICMP Requests


Some attackers use ICMP echo request packets directed to IP broadcast addresses from remote locations to generate denial-of-service attacks. You can set up some custom restrictions to help protect your router from ICMP bursts.

Field Value Description
Enable ICMP requests off | on; default: on Turns the rule on or off.
Enable ICMP limit off | on; default: off Turns ICMP echo-request limit in selected period on or off.
Limit period Second | Minute | Hour | Day; default: Second Period length for matching the conditions of the rule.
Limit integer; default: 5 Maximum ICMP echo-request number during the period.
Limit burst integer; default: 10 Indicates the maximum burst before the above limit kicks in.

SSH Attack Prevention


This protection prevent SSH attacks by limiting connections in a defined period.

Field Value Description
Enable SSH limit off | on; default: off Turns the rule on or off.
Limit period Second | Minute | Hour | Day; default: Second Period length for matching the conditions of the rule.
Limit integer; default: 5 Maximum SSH connections during the set period
Limit burst integer; default: 10 Indicates the maximum burst before the above limit kicks in.

HTTP Attack Prevention


An HTTP attack sends a complete, legitimate HTTP header, which includes a 'Content-Length' field to specify the size of the message body to follow. However, the attacker then proceeds to send the actual message body at an extremely slow rate (e.g. 1 byte/100 seconds.) Due to the entire message being correct and complete, the target server will attempt to obey the 'Content-Length' field in the header, and wait for the entire body of the message to be transmitted, hence slowing it down.

Field Value Description
Enable HTTP limit off | on; default: off Turns the rule on or off.
Limit period Second | Minute | Hour | Day; default: Second Period length for matching the conditions of the rule.
Limit integer; default: 5 Maximum HTTP connections during the set period<./td>
Limit burst integer; default: 10 Indicates the maximum burst before the above limit kicks in.

HTTPS Attack Prevention


This section allows you to enable protection against HTTPS attacks, also known as "man-in-the-middle" attacks (MITM).

In cryptography and computer security, a man-in-the-middle attack (MITM) is an attack where the perpetrator secretly relays and possibly alters the communication between two parties who believe they are directly communicating with each other. One example of man-in-the-middle attacks is active eavesdropping, in which the attacker makes independent connections with the victims and relays messages between them to make them believe they are talking directly to each other over a private connection, when in fact the entire conversation is controlled by the attacker.

Field Value Description
Enable HTTPS limit off | on; default: off Turns the rule on or off.
Limit period Second | Minute | Hour | Day; default: Second Period length for matching the conditions of the rule.
Limit integer; default: 5 Maximum HTTPS connections during the set period.
Limit burst integer; default: 10 Indicates the maximum burst number before the above limit kicks in.

Port Scan


Port Scan attacks scan which of the targeted host's ports are open. Network ports are the entry points to a machine that is connected to the Internet. A service that listens on a port is able to receive data from a client application, process it and send a response back. Malicious clients can sometimes exploit vulnerabilities in the server code so they gain access to sensitive data or execute malicious code on the machine remotely. Port scanning is usually done in the initial phase of a penetration test in order to discover all network entry points into the target system. The Port Scan section provides you with the possibility to enable protection against port scanning software. The Defending Type section provides the possibility for the user to enable protections from certain types of online attacks. These include SYN-FIN, SYN-RST, X-Mas, FIN scan and NULLflags attacks.

Field Value Description
Enable off | on; default: off Turns the function on or off.
Scan count integer [5..65534]; default: 5 How many port scans before blocked.
Interval integer [10..60]; default: 10 Time interval in seconds in which port scans are counted.
SYN-FIN attack off | on; default: off Turns protection from SYN-FIN attacks on or off.
SYN-RST attack off | on; default: off Turns protection from SYN-RST attacks on or off.
X-Mas attack off | on; default: off Turns protection from X-Mas attacks on or off.
FIN scan off | on; default: off Turns protection from FIN scan attacks on or off.
NULLflags attack off | on; default: off Turns protection from NULLflags attacks on or off.

Custom Rules

The Custom rules tab provides you with the possibility to execute iptables 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.

Note: Custom rules are not recommended to be used with hostnames. The rules will not remain active after reboot due to security reasons.

The figure below is an example of the Custom rules tab:

The rules added here are saved in the /etc/firewall.user 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 Save button restarts the firewall service. Thus, adding the custom rules specified in this section to the device's list of firewall rules.

The Reset button resets the custom rules field to its default state.

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