8,907
edits
Changes
Template:Networking rutos manual firewall rut2 rut9 (view source)
Revision as of 15:40, 8 April 2024
, 8 AprilCreated page with "{{Template: Networking_device_manual_fw_disclosure | series = {{{series}}} | name = {{{name}}} | fw_version ={{Template: Networking_device_manual_latest_fw | series = {{{se..."
{{Template: Networking_device_manual_fw_disclosure
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| 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_device_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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==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.
This chapter of the user manual provides an overview of the Firewall page for {{{name}}} devices.
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}
==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:
[[File:Networking_rutos_manual_firewall_general_settings_general_settings_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Drop invalid packets</td>
<td>off | on; default: <b>off</b></td>
<td>If enabled, a "Drop" action will be performed on packets that are determined to be invalid.</td>
</tr>
<tr>
<td>Automatic helper assignment</td>
<td>off | on; default: <b>on</b></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>
<td>Input</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>
</tr>
<tr>
<td>Output</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>
</tr>
<tr>
<td>Forward</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>
</tr>
</table>
<span class="asterisk">*</span> 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:
<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>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>
{{#ifeq: {{{name}}} | TRB500 | | ===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>. {{#switch: {{{series}}} | RUTX | RUTM = <b>Hardware flow offloading</b> is used to execute functions of the router using the hardware directly, instead of a process of software functions. | #default =}}
{{#switch: {{{series}}}
| RUTX | RUTM = [[File:Networking_rutos_manual_firewall_general_settings_routing_nat_offloading_rutx_v2.png|border|class=tlt-border]]
| #default =[[File:Networking_rutos_manual_firewall_general_settings_routing_nat_offloading_v2.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>on</b></td>
<td>Turns software flow offloading on or off.</td>
</tr>
{{#switch: {{{series}}} | RUTX | RUTM =
<tr>
<td>Hardware flow offloading</td>
<td>off {{!}} on; default: <b>on</b></td>
<td>Turns hardware flow offloading on or off.</td>
</tr>| #default =}}
</table>}}
===Zones===
----
The <b>Zones</b> 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:
[[File:Networking_rutos_manual_firewall_general_settings_zones_v2.png|border|class=tlt-border]]
----
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 edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to a zone:
[[File:Networking_rutos_manual_firewall_general_settings_zones_edit_button_v2.png|border|class=tlt-border]]
====Zones: General Settings====
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_general_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>newzone</b></td>
<td>A custom name for the zone. Used for easier management purposes.</td>
</tr>
<tr>
<td>Input</td>
<td>Reject | Drop | Accept; default: <b>Accept</b></td>
<td>Default policy for traffic entering the zone.</td>
</tr>
<tr>
<td>Output</td>
<td>Reject | Drop | Accept; default: <b>Accept</b></td>
<td>Default policy for traffic originating from and leaving the zone.</td>
</tr>
<tr>
<td>Forward</td>
<td>Reject | Drop | Accept; default: <b>Reject</b></td>
<td>Default policy for traffic forwarded between the networks belonging to the zone.</td>
</tr>
<tr>
<td>Masquerading</td>
<td>off | on; default: <b>off</b></td>
<td>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).</td>
</tr>
<tr>
<td>MSS clamping</td>
<td>off | on; default: <b>off</b></td>
<td>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.</td>
</tr>
<tr>
<td>Covered networks</td>
<td>network interface(s); default: <b>none</b></td>
<td>Network or networks that belong to the zone.</td>
</tr>
</table>
====Zones: Advanced Settings====
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_advanced_settings_v4.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Restrict to address family</td>
<td>IPv4 and IPv6 | IPv4 only | IPv6 only; default: <b>IPv4 and IPv6</b></td>
<td>IP address family to which to rule will apply.</td>
</tr>
<tr>
<td>Restrict Masquerading to given source subnets</td>
<td>network/subnet; default: <b>none</b></td>
<td>Applies Masquerading only to the specified source network/subnet.</td>
</tr>
<tr>
<td>Restrict Masquerading to given destinations subnets</td>
<td>network/subnet; default: <b>none</b></td>
<td>Applies Masquerading only to the specified destination network/subnet.</td>
</tr>
<tr>
<td>Force connection tracking</td>
<td>off | on; default: <b>off</b></td>
<td>Always maintains connection state (NEW, ESTABLISHED, RELATED) information.</td>
</tr>
<tr>
<td>Enable logging on this zone</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>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit log messages</span></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>
</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>
</table>
====Zones: Inter-zone Forwarding====
----
The <b>Inter-zone forwarding</b> options control the forwarding policies between the currently edited zone and other zones.
[[File:Networking_rutos_manual_firewall_general_settings_zones_inter-zone_forwarding_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Allow forward to destination zones</td>
<td>zone(s); default: <b>none</b></td>
<td>Allows forward traffic to specified destination zones. Destination zones cover forwarded traffic originating from this source zone.</td>
</tr>
<tr>
<td>Allow forward from source zones</td>
<td>zone(s); default: <b>none</b></td>
<td>Allows forward traffic to specified source zones. Source zones match forwarded traffic originating from other zones that is targeted at this zone.</td>
</tr>
</table>
==Port Forwards==
<b>Port forwarding</b> is a way of redirecting an incoming connection to another IP address, port or the combination of both:
[[File:Networking_rutx_manual_firewall_port_forwards_scheme_v1.png|border|class=tlt-border]]
----
The Port forwards table displays configured port forwarding rules currently configured on the device.
[[File:Networking_rutos_manual_firewall_port_forwards_port_forwards_v2.png|border|class=tlt-border]]
===Add New Port Forward===
----
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_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</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>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which hosts will be connecting.</td>
</tr>
<tr>
<td>Internal IP address</td>
<td>ip; default: <b>none</b></td>
<td>The IP address to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which the incoming connection will be redirected.</td>
</tr>
</table>
===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 edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_port_forwards_edit_button_v3.png|border|class=tlt-border]]
You will be redirected to that rule's configuration general settings page:
[[File:Networking_rutos_manual_firewall_port_forwards_configuration_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on ; default: <b>on</b></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>TCP | UDP | ICMP | All | +Add new; default: <b>TCP+UDP</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td>Source zone</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>
</tr>
<tr>
<td>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) to which hosts will be connecting.<br>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.</td>
</tr>
<tr>
<td>Internal zone</td>
<td>firewall zone name; default: <b>lan</b></td>
<td>The zone to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal IP address</td>
<td>Device LAN IP; default: <b>Device LAN IP</b></td>
<td>The IP address to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which the incoming connection will be redirected.</td>
</tr>
</table>
Advanced settings:
[[File:Networking rutos manual firewall port forwards configuration advanced_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Source MAC address</td>
<td>mac; default: <b>none</b></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>
<td>Source IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment used by connecting hosts.<br>The rule will apply only to hosts that connect from IP addresses specified in this field.<br>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, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Source port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) used by the connecting host.<br>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.</td>
</tr>
<tr>
<td>External IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment to which hosts will be connecting.<br>The rule will apply only to hosts that connect to IP addresses specified in this field.<br>To specify a subnet instead of one IP, add a forward slash followed by the netmask length after the network indication (for example, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Enable NAT loopback</td>
<td>off | on ; default: <b>on</b></td>
<td>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.</td>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra iptables options to the rule.</td>
</tr>
</table>
==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:
[[File:Networking_rutos_manual_firewall_traffic_rules_v2.png|border|class=tlt-border]]
===Traffic Rule Configuration===
----
In order to begin editing a traffic rule, click the edit button [[File:Networking rutx trb14x manual edit button v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_traffic_rules_edit_button_v2.png|border|class=tlt-border]]
You will be redirected to that rule's configuration page:
====General settings====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_general_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default <b>on</b></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>TCP | UDP | All | +Add new |<span style="color:red">ICMP</span>; default: <b>depends on the rule</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td><span style="color:red"> Match ICMP type</span></td>
<td>Any | ICMP-type | + Add new; default: '''none'''</td>
<td>Allows matching specific ICMP types.</td>
</tr>
<tr>
<td>Source zone</td>
<td>firewall zone name; default: '''wan'''</td>
<td>The zone to which the third party will be connecting.</td>
</tr>
<tr>
<td>Source IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment used by connecting hosts.<br>The rule will apply only to hosts that connect from IP addresses specified in this field.<br>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, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Source port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) used by the connecting host.<br>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. Port negation using is also available, for ex. <b>!1</b>.<td>
</tr>
<tr>
<td>Destination zone</td>
<td>firewall zone; default: <b>Device (input)</b></td>
<td>Target zone of the incoming connection.</td>
</tr>
<tr>
<td>Destination address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>Tagert IP address or network segment of the incoming connection.</td>
</tr>
<tr>
<td>Destination port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Tagert port or range of ports of the incoming connection. Port negation using is also available, for ex. <b>!1</b>.</td>
</tr>
<tr>
<td>Action</td>
<td>Drop | Accept | Reject | Don't track | <span style="color:green">DSCP</span> | <span style="color:blue">Mark</span>; default: <b>Accept</b></td>
<td>Action that is to be taken when a packet matches the conditions of the rule.
<ul>
<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>Don't track</b> – packet is no longer tracked as it moves forward.</li>
<li><b>DSCP</b> – packet is marked with specified DiffServ Code Point value.</li>
<li><b>Mark</b> – packet is marked with specified firewall mark..</li>
</ul>
</td>
</tr>
</table>
====Advanced settings====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_advanced_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<td>Restrict to address family</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>
</tr>
<tr>
<td>Source MAC address</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>
</tr>
<tr>
<td><span style="color:green">DSCP</span>: Set Target value</td>
<td>Default | DSCP values; default: <b>Default</b></td>
<td>If specified, target traffic against the given firewall DSCP value.</td>
</tr>
<tr>
<td><span style="color:blue">Mark</span>: Set Target value</td>
<td>hex; default: <b>none</b></td>
<td>If specified, target traffic against the given firewall mark, e.g. FF or ff to target mark 255.</td>
</tr>
<tr>
<td>Match</td>
<td><span style="color:green">DSCP</span> | <span style="color:blue">Mark</span>; default: <b>none</b></td>
<td>Match traffic against the given DSCP value or firewall mark</td>
</tr>
<tr>
<td><span style="color:green">DSCP</span>: Set Match value</td>
<td>Default | DSCP values; default: <b>Default</b></td>
<td>Match traffic against the given firewall DSCP value.</td>
</tr>
<tr>
<td><span style="color:blue">Mark</span>: Set Match value</td>
<td>hex; default: <b>none</b></td>
<td>If specified, match traffic against the given firewall mark, e.g. FF or ff to match mark 255.</td>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra .iptables options to the rule.</td>
</tr>
</table>
====Time restrictions====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_time_restrictions_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<td>Week days</td>
<td>days of the week [Monday..Sunday]; default: <b>none</b></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 System → Administration → [[{{{name}}}_Administration#NTP|NTP]] page will be used.</td>
</tr>
</table>
===Open Ports on Router===
----
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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</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>
</tr>
<tr>
<td>Protocol</td>
<td>TCP | UDP | ICMP | All | +Add new; default: <b>none</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Specifies which port(s) should be opened.</td>
</tr>
</table>
===Add New Forward Rule===
----
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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the rule. This is used for easier management purposes.</td>
</tr>
<tr>
<td>Source zone</td>
<td>firewall zone; default: <b>wan</b></td>
<td>The zone from which traffic has originated.</td>
</tr>
<tr>
<td>Destination zone</td>
<td>firewall zone; default: <b>lan</b></td>
<td>The zone to which traffic will be forwarded to.</td>
</tr>
<tr>
<td>Add</td>
<td>- (interactive button)</td>
<td>Creates the rule and redirects you to the rule's configuration page</td>
</tr>
</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===
----
<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_v2.png|border|class=tlt-border]]
===Add New Source NAT===
----
The <b>Add New Source NAT</b> section is used to create new source NAT rules.
[[File:Networking_rutos_manual_firewall_nat_rules_add_new_source_nat_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the rule. Used only for easier management purposes.</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>Destination Zone</td>
<td>firewall zone; default: <b>wan</b></td>
<td>Matches traffic destined for the specified zone.</td>
</tr>
<tr>
<td>To source IP</td>
<td>ip | do not rewrite; default: <b>none</b></td>
<td>Changes the source IP address in the packet header to the value specified in this field.</td>
</tr>
<tr>
<td>To Source Port</td>
<td>integer [0..65335] | port inversion [!0..!65535] | 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>
</tr>
<tr>
<td>Add</td>
<td>- (interactive button)</td>
<td>Creates the rule in accordance with the given parameter and redirects you to the rule's configuration page.</td>
</tr>
</table>
===Source NAT Configuration===
----
In order to begin editing a traffic rule, click the edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_nat_rules_source_nat_edit_button_v2.png|border|class=tlt-border]]
You will be redirected to that rule's configuration page:
[[File:Networking rutos manual firewall nat rules configuration mobile general.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default <b>on</b></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>TCP | UDP | ICMP | +Add new; 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] | port inversion [!0..!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] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Matches traffic destined for the specified port number.</td>
</tr>
<tr>
<td>Rewrite port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>No rewrite</b></td>
<td>Rewrite matched traffic to the given source port.</td>
</tr>
</table>
[[File:Networking rutos manual firewall nat rules configuration mobile advanced.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra .iptables options to the rule.</td>
</tr>
</table>
[[File:Networking rutos manual firewall nat rules configuration mobile time restriction.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Week days</td>
<td>days of the week [Monday..Sunday]; default: <b>none</b></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 System → Administration → [[{{{name}}}_Administration#NTP|NTP]] page will be used.</td>
</tr>
</table>
==Attack Prevention==
The <b>Attack Prevention</b> menu tab provides the possibility to configure protections against certain types of online attacks.
===SYN Flood Protection===
----
<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_flood_protection_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable SYN flood protection</td>
<td>off | on; default: <b>on</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>SYN flood rate</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>
</tr>
<tr>
<td>SYN flood burst</td>
<td>integer; default: <b>10</b></td>
<td>Sets burst limit for SYN packets above which the traffic is considered flooded if it exceeds the allowed rate</td>
</tr>
<tr>
<td>TCP SYN cookies</td>
<td>off | on; default: <b>on</b></td>
<td>Enables the use of SYN cookies (particular choices of initial TCP sequence numbers by TCP servers)</td>
</tr>
</table>
===Remote ICMP Requests===
----
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_remote_icmp_requests_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable ICMP requests</td>
<td>off | on; default: <b>on</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Enable ICMP limit</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>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit period</span></td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit</span></td>
<td>integer; default: <b>5</b></td>
<td>Maximum ICMP echo-request number during the period.</td>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit burst</span></td>
<td>integer; default: <b>10</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===SSH Attack Prevention===
----
This protection prevent <b>SSH attacks</b> by limiting connections in a defined period.
[[File:Networking_rutos_manual_firewall_attack_prevention_ssh_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable SSH limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum SSH connections during the set period</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===HTTP Attack Prevention===
----
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_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable HTTP limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum HTTP connections during the set period.</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===HTTPS Attack Prevention===
----
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.
[[File:Networking_rutos_manual_firewall_attack_prevention_https_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable HTTPS limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum HTTPS connections during the set period.</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst number before the above limit kicks in.</td>
</tr>
</table>
===Port Scan===
----
<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 <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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the function on or off.</td>
</tr>
<tr>
<td>Scan count</td>
<td>integer [5..10000]; default: <b>none</b></td>
<td>How many port scans before blocked.</td>
</tr>
<tr>
<td>Interval</td>
<td>integer [10..4096]; default: <b>none</b></td>
<td>Time interval in seconds in which port scans are counted.</td>
</tr>
<tr>
<td>SYN-FIN attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from SYN-FIN attacks on or off.</td>
</tr>
<tr>
<td>SYN-RST attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from SYN-RST attacks on or off.</td>
</tr>
<tr>
<td>X-Mas attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from X-Mas attacks on or off.</td>
</tr>
<tr>
<td>FIN scan</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from FIN scan attacks on or off.</td>
</tr>
<tr>
<td>NULLflags attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from NULLflags attacks on or off.</td>
</tr>
</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.
==DMZ==
The <b>DMZ</b> is a security concept. It comprises the separation of the LAN-side network into at least two networks: the user LAN and the DMZ. Generally the DMZ is imprisoned: only access to certain ports from the Internet are allowed into the DMZ, while the DMZ is not allowed to establish new connections to the WAN-side or LAN-side networks. That way, if a server inside of the DMZ is hacked the potential damage that can be done remains restricted! The whole point of the DMZ is to cleanly create a unique firewall rule set that dramatically restricts access in to, and out of the, DMZ.
[[File:Networking rutos manual network firewall dmz_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Enables the DMZ configuration.</td>
</tr>
<tr>
<td>Host IP</td>
<td>ipv4; default: <b>none</b></td>
<td>Specifies the IP address of the DMZ host.</td>
</tr>
<tr>
<td>Protocol</td>
<td>All | <span style="color:blue">TCP</span> | <span style="color:blue">UDP</span> | ICMP; default: <b>None</b></td>
<td>Specifies for which protocols the DMZ will be used.</td>
</tr>
<tr>
<td><span style="color:blue">Ports</span></td>
<td>0..65535 | port range | port negation; default: <b>none</b></td>
<td>Match incoming traffic directed at the given destination port or port range on DMZ host IP.</td>
</tr>
</table>
[[Category:{{{name}}} Network section]]
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| 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_device_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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==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.
This chapter of the user manual provides an overview of the Firewall page for {{{name}}} devices.
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
}}
==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:
[[File:Networking_rutos_manual_firewall_general_settings_general_settings_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Drop invalid packets</td>
<td>off | on; default: <b>off</b></td>
<td>If enabled, a "Drop" action will be performed on packets that are determined to be invalid.</td>
</tr>
<tr>
<td>Automatic helper assignment</td>
<td>off | on; default: <b>on</b></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>
<td>Input</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>
</tr>
<tr>
<td>Output</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>
</tr>
<tr>
<td>Forward</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>
</tr>
</table>
<span class="asterisk">*</span> 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:
<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>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>
{{#ifeq: {{{name}}} | TRB500 | | ===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>. {{#switch: {{{series}}} | RUTX | RUTM = <b>Hardware flow offloading</b> is used to execute functions of the router using the hardware directly, instead of a process of software functions. | #default =}}
{{#switch: {{{series}}}
| RUTX | RUTM = [[File:Networking_rutos_manual_firewall_general_settings_routing_nat_offloading_rutx_v2.png|border|class=tlt-border]]
| #default =[[File:Networking_rutos_manual_firewall_general_settings_routing_nat_offloading_v2.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>on</b></td>
<td>Turns software flow offloading on or off.</td>
</tr>
{{#switch: {{{series}}} | RUTX | RUTM =
<tr>
<td>Hardware flow offloading</td>
<td>off {{!}} on; default: <b>on</b></td>
<td>Turns hardware flow offloading on or off.</td>
</tr>| #default =}}
</table>}}
===Zones===
----
The <b>Zones</b> 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:
[[File:Networking_rutos_manual_firewall_general_settings_zones_v2.png|border|class=tlt-border]]
----
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 edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to a zone:
[[File:Networking_rutos_manual_firewall_general_settings_zones_edit_button_v2.png|border|class=tlt-border]]
====Zones: General Settings====
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_general_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>newzone</b></td>
<td>A custom name for the zone. Used for easier management purposes.</td>
</tr>
<tr>
<td>Input</td>
<td>Reject | Drop | Accept; default: <b>Accept</b></td>
<td>Default policy for traffic entering the zone.</td>
</tr>
<tr>
<td>Output</td>
<td>Reject | Drop | Accept; default: <b>Accept</b></td>
<td>Default policy for traffic originating from and leaving the zone.</td>
</tr>
<tr>
<td>Forward</td>
<td>Reject | Drop | Accept; default: <b>Reject</b></td>
<td>Default policy for traffic forwarded between the networks belonging to the zone.</td>
</tr>
<tr>
<td>Masquerading</td>
<td>off | on; default: <b>off</b></td>
<td>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).</td>
</tr>
<tr>
<td>MSS clamping</td>
<td>off | on; default: <b>off</b></td>
<td>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.</td>
</tr>
<tr>
<td>Covered networks</td>
<td>network interface(s); default: <b>none</b></td>
<td>Network or networks that belong to the zone.</td>
</tr>
</table>
====Zones: Advanced Settings====
----
[[File:Networking_rutos_manual_firewall_general_settings_zones_advanced_settings_v4.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Restrict to address family</td>
<td>IPv4 and IPv6 | IPv4 only | IPv6 only; default: <b>IPv4 and IPv6</b></td>
<td>IP address family to which to rule will apply.</td>
</tr>
<tr>
<td>Restrict Masquerading to given source subnets</td>
<td>network/subnet; default: <b>none</b></td>
<td>Applies Masquerading only to the specified source network/subnet.</td>
</tr>
<tr>
<td>Restrict Masquerading to given destinations subnets</td>
<td>network/subnet; default: <b>none</b></td>
<td>Applies Masquerading only to the specified destination network/subnet.</td>
</tr>
<tr>
<td>Force connection tracking</td>
<td>off | on; default: <b>off</b></td>
<td>Always maintains connection state (NEW, ESTABLISHED, RELATED) information.</td>
</tr>
<tr>
<td>Enable logging on this zone</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>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit log messages</span></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>
</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>
</table>
====Zones: Inter-zone Forwarding====
----
The <b>Inter-zone forwarding</b> options control the forwarding policies between the currently edited zone and other zones.
[[File:Networking_rutos_manual_firewall_general_settings_zones_inter-zone_forwarding_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Allow forward to destination zones</td>
<td>zone(s); default: <b>none</b></td>
<td>Allows forward traffic to specified destination zones. Destination zones cover forwarded traffic originating from this source zone.</td>
</tr>
<tr>
<td>Allow forward from source zones</td>
<td>zone(s); default: <b>none</b></td>
<td>Allows forward traffic to specified source zones. Source zones match forwarded traffic originating from other zones that is targeted at this zone.</td>
</tr>
</table>
==Port Forwards==
<b>Port forwarding</b> is a way of redirecting an incoming connection to another IP address, port or the combination of both:
[[File:Networking_rutx_manual_firewall_port_forwards_scheme_v1.png|border|class=tlt-border]]
----
The Port forwards table displays configured port forwarding rules currently configured on the device.
[[File:Networking_rutos_manual_firewall_port_forwards_port_forwards_v2.png|border|class=tlt-border]]
===Add New Port Forward===
----
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_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</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>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which hosts will be connecting.</td>
</tr>
<tr>
<td>Internal IP address</td>
<td>ip; default: <b>none</b></td>
<td>The IP address to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which the incoming connection will be redirected.</td>
</tr>
</table>
===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 edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_port_forwards_edit_button_v3.png|border|class=tlt-border]]
You will be redirected to that rule's configuration general settings page:
[[File:Networking_rutos_manual_firewall_port_forwards_configuration_v3.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on ; default: <b>on</b></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>TCP | UDP | ICMP | All | +Add new; default: <b>TCP+UDP</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td>Source zone</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>
</tr>
<tr>
<td>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) to which hosts will be connecting.<br>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.</td>
</tr>
<tr>
<td>Internal zone</td>
<td>firewall zone name; default: <b>lan</b></td>
<td>The zone to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal IP address</td>
<td>Device LAN IP; default: <b>Device LAN IP</b></td>
<td>The IP address to which the incoming connection will be redirected.</td>
</tr>
<tr>
<td>Internal port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>The port number to which the incoming connection will be redirected.</td>
</tr>
</table>
Advanced settings:
[[File:Networking rutos manual firewall port forwards configuration advanced_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Source MAC address</td>
<td>mac; default: <b>none</b></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>
<td>Source IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment used by connecting hosts.<br>The rule will apply only to hosts that connect from IP addresses specified in this field.<br>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, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Source port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) used by the connecting host.<br>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.</td>
</tr>
<tr>
<td>External IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment to which hosts will be connecting.<br>The rule will apply only to hosts that connect to IP addresses specified in this field.<br>To specify a subnet instead of one IP, add a forward slash followed by the netmask length after the network indication (for example, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Enable NAT loopback</td>
<td>off | on ; default: <b>on</b></td>
<td>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.</td>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra iptables options to the rule.</td>
</tr>
</table>
==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:
[[File:Networking_rutos_manual_firewall_traffic_rules_v2.png|border|class=tlt-border]]
===Traffic Rule Configuration===
----
In order to begin editing a traffic rule, click the edit button [[File:Networking rutx trb14x manual edit button v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_traffic_rules_edit_button_v2.png|border|class=tlt-border]]
You will be redirected to that rule's configuration page:
====General settings====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_general_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default <b>on</b></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>TCP | UDP | All | +Add new |<span style="color:red">ICMP</span>; default: <b>depends on the rule</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td><span style="color:red"> Match ICMP type</span></td>
<td>Any | ICMP-type | + Add new; default: '''none'''</td>
<td>Allows matching specific ICMP types.</td>
</tr>
<tr>
<td>Source zone</td>
<td>firewall zone name; default: '''wan'''</td>
<td>The zone to which the third party will be connecting.</td>
</tr>
<tr>
<td>Source IP address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>IP address or network segment used by connecting hosts.<br>The rule will apply only to hosts that connect from IP addresses specified in this field.<br>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, <i>10.0.0.0/8</i>).</td>
</tr>
<tr>
<td>Source port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Port number(s) used by the connecting host.<br>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. Port negation using is also available, for ex. <b>!1</b>.<td>
</tr>
<tr>
<td>Destination zone</td>
<td>firewall zone; default: <b>Device (input)</b></td>
<td>Target zone of the incoming connection.</td>
</tr>
<tr>
<td>Destination address</td>
<td>ip | ip/netmask; default: <b>any</b></td>
<td>Tagert IP address or network segment of the incoming connection.</td>
</tr>
<tr>
<td>Destination port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Tagert port or range of ports of the incoming connection. Port negation using is also available, for ex. <b>!1</b>.</td>
</tr>
<tr>
<td>Action</td>
<td>Drop | Accept | Reject | Don't track | <span style="color:green">DSCP</span> | <span style="color:blue">Mark</span>; default: <b>Accept</b></td>
<td>Action that is to be taken when a packet matches the conditions of the rule.
<ul>
<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>Don't track</b> – packet is no longer tracked as it moves forward.</li>
<li><b>DSCP</b> – packet is marked with specified DiffServ Code Point value.</li>
<li><b>Mark</b> – packet is marked with specified firewall mark..</li>
</ul>
</td>
</tr>
</table>
====Advanced settings====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_advanced_settings_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<td>Restrict to address family</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>
</tr>
<tr>
<td>Source MAC address</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>
</tr>
<tr>
<td><span style="color:green">DSCP</span>: Set Target value</td>
<td>Default | DSCP values; default: <b>Default</b></td>
<td>If specified, target traffic against the given firewall DSCP value.</td>
</tr>
<tr>
<td><span style="color:blue">Mark</span>: Set Target value</td>
<td>hex; default: <b>none</b></td>
<td>If specified, target traffic against the given firewall mark, e.g. FF or ff to target mark 255.</td>
</tr>
<tr>
<td>Match</td>
<td><span style="color:green">DSCP</span> | <span style="color:blue">Mark</span>; default: <b>none</b></td>
<td>Match traffic against the given DSCP value or firewall mark</td>
</tr>
<tr>
<td><span style="color:green">DSCP</span>: Set Match value</td>
<td>Default | DSCP values; default: <b>Default</b></td>
<td>Match traffic against the given firewall DSCP value.</td>
</tr>
<tr>
<td><span style="color:blue">Mark</span>: Set Match value</td>
<td>hex; default: <b>none</b></td>
<td>If specified, match traffic against the given firewall mark, e.g. FF or ff to match mark 255.</td>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra .iptables options to the rule.</td>
</tr>
</table>
====Time restrictions====
----
[[File:Networking_rutos_manual_firewall_traffic_rules_configuration_time_restrictions_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<td>Week days</td>
<td>days of the week [Monday..Sunday]; default: <b>none</b></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 System → Administration → [[{{{name}}}_Administration#NTP|NTP]] page will be used.</td>
</tr>
</table>
===Open Ports on Router===
----
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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</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>
</tr>
<tr>
<td>Protocol</td>
<td>TCP | UDP | ICMP | All | +Add new; default: <b>none</b></td>
<td>Specifies to which protocols the rule should apply.</td>
</tr>
<tr>
<td>External port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Specifies which port(s) should be opened.</td>
</tr>
</table>
===Add New Forward Rule===
----
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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the rule. This is used for easier management purposes.</td>
</tr>
<tr>
<td>Source zone</td>
<td>firewall zone; default: <b>wan</b></td>
<td>The zone from which traffic has originated.</td>
</tr>
<tr>
<td>Destination zone</td>
<td>firewall zone; default: <b>lan</b></td>
<td>The zone to which traffic will be forwarded to.</td>
</tr>
<tr>
<td>Add</td>
<td>- (interactive button)</td>
<td>Creates the rule and redirects you to the rule's configuration page</td>
</tr>
</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===
----
<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_v2.png|border|class=tlt-border]]
===Add New Source NAT===
----
The <b>Add New Source NAT</b> section is used to create new source NAT rules.
[[File:Networking_rutos_manual_firewall_nat_rules_add_new_source_nat_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Name</td>
<td>string; default: <b>none</b></td>
<td>The name of the rule. Used only for easier management purposes.</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>Destination Zone</td>
<td>firewall zone; default: <b>wan</b></td>
<td>Matches traffic destined for the specified zone.</td>
</tr>
<tr>
<td>To source IP</td>
<td>ip | do not rewrite; default: <b>none</b></td>
<td>Changes the source IP address in the packet header to the value specified in this field.</td>
</tr>
<tr>
<td>To Source Port</td>
<td>integer [0..65335] | port inversion [!0..!65535] | 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>
</tr>
<tr>
<td>Add</td>
<td>- (interactive button)</td>
<td>Creates the rule in accordance with the given parameter and redirects you to the rule's configuration page.</td>
</tr>
</table>
===Source NAT Configuration===
----
In order to begin editing a traffic rule, click the edit button [[File:Networking_rutx_trb14x_manual_edit_button_v2.png|20px]] next to it:
[[File:Networking_rutos_manual_firewall_nat_rules_source_nat_edit_button_v2.png|border|class=tlt-border]]
You will be redirected to that rule's configuration page:
[[File:Networking rutos manual firewall nat rules configuration mobile general.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default <b>on</b></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>TCP | UDP | ICMP | +Add new; 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] | port inversion [!0..!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] | port inversion [!0..!65535]; default: <b>none</b></td>
<td>Matches traffic destined for the specified port number.</td>
</tr>
<tr>
<td>Rewrite port</td>
<td>integer [0..65535] | range of integers [0..65534] - [1..65535] | port inversion [!0..!65535]; default: <b>No rewrite</b></td>
<td>Rewrite matched traffic to the given source port.</td>
</tr>
</table>
[[File:Networking rutos manual firewall nat rules configuration mobile advanced.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Extra arguments</td>
<td>string; default: <b>none</b></td>
<td>Adds extra .iptables options to the rule.</td>
</tr>
</table>
[[File:Networking rutos manual firewall nat rules configuration mobile time restriction.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Week days</td>
<td>days of the week [Monday..Sunday]; default: <b>none</b></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 System → Administration → [[{{{name}}}_Administration#NTP|NTP]] page will be used.</td>
</tr>
</table>
==Attack Prevention==
The <b>Attack Prevention</b> menu tab provides the possibility to configure protections against certain types of online attacks.
===SYN Flood Protection===
----
<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_flood_protection_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable SYN flood protection</td>
<td>off | on; default: <b>on</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>SYN flood rate</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>
</tr>
<tr>
<td>SYN flood burst</td>
<td>integer; default: <b>10</b></td>
<td>Sets burst limit for SYN packets above which the traffic is considered flooded if it exceeds the allowed rate</td>
</tr>
<tr>
<td>TCP SYN cookies</td>
<td>off | on; default: <b>on</b></td>
<td>Enables the use of SYN cookies (particular choices of initial TCP sequence numbers by TCP servers)</td>
</tr>
</table>
===Remote ICMP Requests===
----
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_remote_icmp_requests_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable ICMP requests</td>
<td>off | on; default: <b>on</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Enable ICMP limit</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>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit period</span></td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit</span></td>
<td>integer; default: <b>5</b></td>
<td>Maximum ICMP echo-request number during the period.</td>
</tr>
<tr>
<td><span style="color: #1550bf;">Limit burst</span></td>
<td>integer; default: <b>10</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===SSH Attack Prevention===
----
This protection prevent <b>SSH attacks</b> by limiting connections in a defined period.
[[File:Networking_rutos_manual_firewall_attack_prevention_ssh_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable SSH limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum SSH connections during the set period</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===HTTP Attack Prevention===
----
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_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable HTTP limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum HTTP connections during the set period.</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst before the above limit kicks in.</td>
</tr>
</table>
===HTTPS Attack Prevention===
----
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.
[[File:Networking_rutos_manual_firewall_attack_prevention_https_attack_prevention_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable HTTPS limit</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Limit period</td>
<td>Second | Minute | Hour | Day; default: <b>Second</b></td>
<td>Period length for matching the conditions of the rule.</td>
</tr>
<tr>
<td>Limit</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Maximum HTTPS connections during the set period.</td>
</tr>
<tr>
<td>Limit burst</td>
<td>integer [1..10000]; default: <b>none</b></td>
<td>Indicates the maximum burst number before the above limit kicks in.</td>
</tr>
</table>
===Port Scan===
----
<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 <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_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the function on or off.</td>
</tr>
<tr>
<td>Scan count</td>
<td>integer [5..10000]; default: <b>none</b></td>
<td>How many port scans before blocked.</td>
</tr>
<tr>
<td>Interval</td>
<td>integer [10..4096]; default: <b>none</b></td>
<td>Time interval in seconds in which port scans are counted.</td>
</tr>
<tr>
<td>SYN-FIN attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from SYN-FIN attacks on or off.</td>
</tr>
<tr>
<td>SYN-RST attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from SYN-RST attacks on or off.</td>
</tr>
<tr>
<td>X-Mas attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from X-Mas attacks on or off.</td>
</tr>
<tr>
<td>FIN scan</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from FIN scan attacks on or off.</td>
</tr>
<tr>
<td>NULLflags attack</td>
<td>off | on; default: <b>off</b></td>
<td>Turns protection from NULLflags attacks on or off.</td>
</tr>
</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.
==DMZ==
The <b>DMZ</b> is a security concept. It comprises the separation of the LAN-side network into at least two networks: the user LAN and the DMZ. Generally the DMZ is imprisoned: only access to certain ports from the Internet are allowed into the DMZ, while the DMZ is not allowed to establish new connections to the WAN-side or LAN-side networks. That way, if a server inside of the DMZ is hacked the potential damage that can be done remains restricted! The whole point of the DMZ is to cleanly create a unique firewall rule set that dramatically restricts access in to, and out of the, DMZ.
[[File:Networking rutos manual network firewall dmz_v2.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Enables the DMZ configuration.</td>
</tr>
<tr>
<td>Host IP</td>
<td>ipv4; default: <b>none</b></td>
<td>Specifies the IP address of the DMZ host.</td>
</tr>
<tr>
<td>Protocol</td>
<td>All | <span style="color:blue">TCP</span> | <span style="color:blue">UDP</span> | ICMP; default: <b>None</b></td>
<td>Specifies for which protocols the DMZ will be used.</td>
</tr>
<tr>
<td><span style="color:blue">Ports</span></td>
<td>0..65535 | port range | port negation; default: <b>none</b></td>
<td>Match incoming traffic directed at the given destination port or port range on DMZ host IP.</td>
</tr>
</table>
[[Category:{{{name}}} Network section]]
