Changes

Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version ={{Template: Networking_rutos_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }} __TOC__ =..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
__TOC__

==Static Routes==

<b>Routes</b> ensure that network traffic finds its path to a specified host or network, both in local and remote network scenarios. Static routes are simply fixed routing entries in the routing table(s).

This section provides the possibility to configure custom static routes.

===Static IPv4 Routes===
----
The <b>Static IPv4 Routes</b> section displays a list of user defined static IPv4 routes and provides the possibility to add and configure new ones. The list is empty by default.

[[File:Networking tswos manual static routes static ipv4 routes.png|border|class=tlt-border]]

To add a new route and begin editing, simply click the 'Add' button. Refer to the table below for information on static route configuration fields.

[[File:Networking tswos manual static routes static ipv4 new routes.png|border|class=tlt-border]]

<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Interface</td>
<td>static | dhcp | dhcp6; default: <b>static</b></td>
<td>The zone where the target network resides. </td>
</tr>
<tr>
<td>Target<span class="asterisk">*</span></td>
<td>ip4; default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv4-Netmask<span class="asterisk">*</span></td>
<td>netmask; default: <b>none</b></td>
<td>A netmask is used to divide an IP address into sub-networks (subnets). Combined together, the 'Netmask' and 'Target' values define the exact destination network or IP address to which this route applies.</td>
</tr>
<tr>
<td>IPv4-Gateway</td>
<td>ip4; default: <b>none</b></td>
<td>A gateway can be any machine in a network that is capable of serving as an access point to another network. Traffic that matches this route will be directed over the IP address specified in this field.</td>
</tr>
<tr>
<td>MTU</td>
<td>integer [68..9200]; default: <b>1500</b></td>
<td>Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
</tr>
<tr>
<td>Route Type</td>
<td>unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: <b>unicast</b></td>
<td>Selects route type. Each type specifies a different behavior for the route:
<ul>
<li><b>unicast</b> - most common type of route, simply describes a path to a destination.</li>
<li><b>local</b> - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.</li>
<li><b>broadcast</b> - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.</li>
<li><b>multicast</b> - used for distribution of multicast traffic.</li>
<li><b>unreachable</b> - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.</li>
<li><b>prohibit</b> - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.</li>
<li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li>
<li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li>
<li><b>-- custom --</b> - does not use any of the predefined route types.</li>
</ul>
</td>
</tr>
</table>

<span class="asterisk">*</span><b>Additional notes on 'Target' & 'Netmask' fields:</b>
----
You can define a rule that applies to a single IP like this:

<ul>
<li><b>Target</b>: some IP</li>
<li><b>Netmask</b>: 255.255.255.255</li>
</ul>

Furthermore, you can create target/netmask combinations that apply to a range of IPs. Refer to the table below for examples.

<table class="nd-mantable">
<tr>
<th>Target</th>
<th>Netmask</th>
<th>Network range</th>
</tr>
<tr>
<td>192.168.2.0</td>
<td>255.255.255.240</td>
<td>192.168.2.0 - 192.168.2.15</td>
</tr>
<tr>
<td>192.168.2.240</td>
<td>255.255.255.240</td>
<td>192.168.2.240 - 192.168.2.255</td>
</tr>
<tr>
<td>192.168.2.161</td>
<td>255.255.255.0</td>
<td>192.168.2.0 - 192.168.55.255</td>
</tr>
<tr>
<td>192.168.0.0</td>
<td>255.255.0.0</td>
<td>192.168.0.0 - 192.168.255.255</td>
</tr>
<tr>
<td>192.168.2.161</td>
<td>255.255.255.255</td>
<td>192.168.2.161</td>
</tr>
</table>

===Static IPv6 Routes===
----
The <b>Static IPv6 Routes</b> section displays a list of user defined static IPv6 routes and provides the possibility to add and configure new ones. The list is empty by default.

[[File:Networking tswos manual static routes static ipv6 routes.png|border|class=tlt-border]]

To add a new route and begin editing, simply click the 'Add' button. Refer to the table below for information on static route configuration fields.

[[File:Networking tswos manual static routes static ipv6 new routes.png|border|class=tlt-border]]

<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Interface</td>
<td>static | dhcp | dhcp6; default: <b>static</b></td>
<td>The zone where the target network resides. </td>
</tr>
<tr>
<td>Target</td>
<td>ip6; default: <b>none</b></td>
<td>Destination network address.</td>
</tr>
<tr>
<td>IPv6-Gateway</td>
<td>ip6; default: <b>none</b></td>
<td>A gateway can be any machine in a network that is capable of serving as an access point to another network. Traffic that matches this route will be directed over the IP address specified in this field.</td>
</tr>
<tr>
<td>MTU</td>
<td>integer [68..9200]; default: <b>1500</b></td>
<td>Sets the maximum transmission unit (MTU) size. It is the largest size of a protocol data unit (PDU) that can be transmitted in a single network layer transaction.</td>
</tr>
<tr>
<td>Route Type</td>
<td>unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: <b>unicast</b></td>
<td>Selects route type. Each type specifies a different behavior for the route:
<ul>
<li><b>unicast</b> - most common type of route, simply describes a path to a destination.</li>
<li><b>local</b> - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.</li>
<li><b>broadcast</b> - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.</li>
<li><b>multicast</b> - used for distribution of multicast traffic.</li>
<li><b>unreachable</b> - sends an ICMP "unreachable" response to the source address when a request for a routing decision returns a "destination with an unreachable route type" message.</li>
<li><b>prohibit</b> - used to prohibit traffic to specified host or network. When a destination is prohibited, the kernel sends a 'Network is unreachable' response the source address.</li>
<li><b>blackhole</b> - packets that match this type of route are discarded without any response.</li>
<li><b>anycast</b> - provides a possibility to route incoming requests to multiple different network locations.</li>
<li><b>-- custom --</b> - does not use any of the predefined route types.</li>
</ul>
</td>
</tr>
</table>



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