Template:Networking rutos manual routing: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
Line 331: Line 331:
====General Settings====
====General Settings====
----
----
Below is an example of BGP <b>General</b> settings section.
The <b>General Settings</b> section is used to turn BGP protocol usage on or off or to upload an external BGP configuration. Below is an example of the BGP General Settings section.


[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_general_settings.png|border|class=tlt-border]]
Line 360: Line 360:
====BGP Instance====
====BGP Instance====
----
----
Below is an example of '''BGP Instance''' settings section.
The <b>BGP Instance</b> section is used to configure some of the main operating parameters of the BGP protocol. Below is an example of the BGP Instance section.


[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_bgp_bgp_instance.png|border|class=tlt-border]]
Line 377: Line 377:
     <tr>
     <tr>
       <td>AS</td>
       <td>AS</td>
       <td>default: <b>none</b></td>
       <td>integer [1..65535]default: <b>none</b></td>
      <td>AS number is an identification of an autonomous system. The BGP protocol uses the AS number for detecting whether the BGP connection is internal or an external one.</td>
        <td>BGP Autonomous System (AS) number. It is an identifier that represents a routing domain; BGP routers can exchange routes within the same Autonomous System.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>BGP router ID</td>
     <td>BGP router ID</td>
         <td>default: <b>none</b></td>
         <td>32-bit integer; default: <b>none</b></td>
         <td>The router ID is used by BGP to identify the routing device from which a packet originated. Fefault router ID value is selected as the largest IP Address of the interface.</td>
         <td>The router ID is used by BGP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Network</td>
         <td>default: <b>none</b></td>
         <td>ip/netmask; default: <b>none</b></td>
         <td>Adds an announcement network(s).</td>
         <td>Adds an announcement network(s). Routes to these networks will be shared over BGP.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Redistribution options</td>
         <td>Redistribution options</td>
         <td>default: <b>none</b></td>
         <td>Connected routes <nowiki>|</nowiki> Kernel added routes <nowiki>|</nowiki> NHRP routes <nowiki>|</nowiki> OSPF routes <nowiki>|</nowiki> Static routes <nowiki>|</nowiki> custom; default: <b>none</b></td>
         <td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td>
         <td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td>
     </tr>
     </tr>
Line 424: Line 424:
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>default: <b>none</b></td>
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Remote autonomous system number of this remote BGP Neighbour.</td>
       <td>Remote autonomous system number of this remote BGP Neighbour.</td>
     </tr>
     </tr>
Line 460: Line 460:
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>default: <b>none</b></td>
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Remote autonomous system number of this remote BGP Neighbour.</td>
       <td>Remote autonomous system number of this remote BGP Neighbour.</td>
     </tr>
     </tr>
Line 512: Line 512:
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>default: <b>none</b></td>
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Remote autonomous system number.</td>
       <td>Remote autonomous system number.</td>
     </tr>
     </tr>
Line 538: Line 538:
     <tr>
     <tr>
       <td>Remote AS</td>
       <td>Remote AS</td>
       <td>default: <b>none</b></td>
       <td>integer [1..65535]; default: <b>none</b></td>
       <td>Remote autonomous system number.</td>
       <td>Remote autonomous system number.</td>
     </tr>
     </tr>
Line 962: Line 962:
====General====
====General====
----
----
Below is an example of EIGRP '''General''' settings section.
The <b>General Settings</b> section is used to configure some of the main operating parameters of the EIGRP protocol. Below is an example of the EIGRP General Settings section.


[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_eigrp_general_settings.png|border|class=tlt-border]]
Line 975: Line 975:
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>Toggles EIGRP network on or off</td>
       <td>Turns EIGRP protocol usage on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Enable logging</td>
         <td>Enable logging</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>Enable logging of EIGRP</td>
         <td>Turns logging of EIGRP traffic on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>AS</td>
         <td>AS</td>
         <td>default: <b>none</b></td>
         <td>integer [1..65535]; default: <b>none</b></td>
         <td>'''EIGRP''' uses this number so that it makes sure it only talks to other EIGRP speakers that are in the same AS. For instance, if you have two routers, one with "router eigrp 1" and one with "router eigrp 2," then they would not form an adjacency</td>
         <td>EIGRP Autonomous System (AS) number. It is an identifier that represents a routing domain; EIGRP routers can exchange routes within the same Autonomous System.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Router ID</td>
         <td>Router ID</td>
         <td>IP; default: <b>none</b></td>
         <td>ip4; default: <b>none</b></td>
         <td>'''EIGRP''' router-ID in IP address format</td>
         <td>The router ID is used by EIGRP to identify the routing device from which a packet originated. Default router ID value is selected as the largest IP Address of the interface.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Network</td>
       <td>Network</td>
      <td>IP; default: <b>none</b></td>
        <td>ip/netmask; default: <b>none</b></td>
      <td>The announcement network</td>
        <td>Adds an announcement network(s). Routes to these networks will be shared over EIGRP.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Redistribution options</td>
         <td>Redistribution options</td>
         <td>default: <b>none</b></td>
         <td>Connected routes <nowiki>|</nowiki> Kernel added routes <nowiki>|</nowiki> NHRP routes <nowiki>|</nowiki> OSPF routes <nowiki>|</nowiki> Static routes <nowiki>|</nowiki> custom; default: <b>none</b></td>
         <td>'''Route redistribution''' is a process that allows a network to use a '''routing''' protocol to dynamically '''route''' traffic based on information learned from a different '''routing''' protocol.</td>
         <td>Distributes selected routes. Route redistribution is a process that allows a network to use a routing protocol to dynamically route traffic based on information learned from a separate routing protocol.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Neighbors</td>
     <td>Neighbors</td>
         <td>IP; default: <b>none</b></td>
         <td>ip4; default: <b>none</b></td>
         <td>Neighbour IP addres</td>
         <td>Defines the EIGRP Neighbours (based on their IP addresses) that this device is meant to associate with.</td>
     </tr>
     </tr>
</table>
</table>


===NHRP Protocol===
===NHRP===
----
----
Next Hop Resolution Protocol (NHRP) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer.
<b>Next Hop Resolution Protocol</b> (<b>NHRP</b>) is a protocol or method that can be used so that a computer sending data to another computer can learn the most direct route (the fewest number of hops) to the receiving computer.


====General Settings====
====General Settings====
----
----
Below is an example of NHRP '''General''' settings section.
The <b>General Settings</b> section is used to turn NHRP protocol usage on or off. Below is an example of the NHRP General Settings section.


[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_general_settings.png|border|class=tlt-border]]
Line 1,028: Line 1,028:
       <td>Enable service</td>
       <td>Enable service</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>Toggles NHRP network on or off</td>
       <td>Turns NHRP protocol usage on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable logging</td>
       <td>Enable logging</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>Toggles NHRP logging on or off</td>
       <td>Turns NHRP traffic logging on or off.</td>
     </tr></table>
     </tr></table>


====Interfaces====
====Interfaces====
----
----
Below is an example of NHRP <b>Interfaces</b> settings section. By default, it is empty.
The <b>Interfaces</b> section is used to define which existing network interfaces can participate in NHRP communication. Below is an example of the NHRP Interfaces section which is empty by default.  


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


To add a new NHRP interface, look to the 'Add New Interface' section. Enter a custom name and click the 'Add' button. Your new interface will appear in the 'Interfaces' list.
To create a new NHRP Interface, look to the Add New Interface section; enter a custom name and click the 'Add' button.
 
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_add_button.png|border|class=tlt-border]]
 
The newly added NHRP interface will appear in the Interfaces list and should look similar to this:


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


<table class="nd-mantable">
To see more settings for an NHRP Interface, click the 'Edit' button next to it:
    <tr>
 
        <th>Field</th>
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_edit_button.png|border|class=tlt-border]]
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
      <td>Toggles interface on or off</td>
    </tr>
</table>


=====NHRP Interface Configuration=====
You should redirected to a windows that looks similar to this:
----
By pressing the '''Edit''' button you can find more settings related to '''NHRP Interface.'''


[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_interface_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_interface_configuration.png|border|class=tlt-border]]
Line 1,073: Line 1,066:
     <tr>
     <tr>
         <td>Enabled</td>
         <td>Enabled</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
        </td><td>Enables DMVPN client</td>
        <td>Turns the NHRP Interface on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Interface</td>
         <td>Interface</td>
         <td>default: <b>br-lan</b></td>
         <td>network interface; default: <b>br-lan</b></td>
         <td>Interface which will be using NHRP</td>
         <td>Network interface associated with this NHRP Interface.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Network ID</td>
         <td>Network ID</td>
         <td>default: <b>none</b></td>
         <td>32-bit integer; default: <b>none</b></td>
         <td>Network ID of NHRP</td>
         <td>A numerical identifier for this NHRP Interface.</td>
    </tr>
    <tr>
        <td>NHRP authentication key</td>
        <td>string; default: <b>none</b></td>
        <td>A password used in NHRP authentication.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>NHS</td>
         <td>NHS</td>
         <td>Dynamic <nowiki>|</nowiki> custom; default: <b>none</b></td>
         <td>Dynamic <nowiki>|</nowiki> custom(ip4); default: <b>none</b></td>
         <td>IP address of Next-Hop Server.</td>
         <td>IP address of a Next-Hop server.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>NBMA</td>
         <td>NBMA</td>
         <td>default: <b>none</b></td>
         <td>ip4; default: <b>none</b></td>
         <td>Non-Broadcast Multi-Access(NBMA) network IP address</td>
         <td>Non-Broadcast Multi-Access (NBMA) network IP address.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Hold-time</td>
         <td>Hold-time</td>
         <td>default: '''7200'''</td>
         <td>integer; default: <b>7200</b></td>
         <td>Specifies the holding time for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target. The holdtime is specified in seconds and defaults to two hours.</td>
         <td>Specifies the holding time (in seconds) for NHRP Registration Requests and Resolution Replies sent from this interface or shortcut-target.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>IPsec support</td>
         <td>IPsec support</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off <nowiki>|</nowiki> <span style="color: red;">on</span>; default: <b>off</b></td>
         <td>Use NHRP over IPsec</td>
         <td>Turns usage of NHRP over IPsec for this Interface on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>IP address</td>
         <td><span style="color: red;">IPsec instance</span></td>
        <td>IP; default: <b>none</b></td>
         <td>string; default: <b>none</b></td>
        <td>Network ID of NHRP</td>
         <td>Specifies which existing IPsec instance should be associated with this NHRP Interface.</td>
    </tr>
    <tr>
        <td>NBMA</td>
         <td>IP; default: <b>none</b></td>
         <td>IP address of Next-Hop Server</td>
     </tr>
     </tr>
</table>
</table>
Line 1,120: Line 1,113:
=====NHRP Mappings Configuration=====
=====NHRP Mappings Configuration=====
----
----
Below is an example of the <b>NHRP Mappings Configuration</b> section.  
The <b>NHRP Mappings Configuration</b> section is used to configure (map) associations between NHRP router IP address and NBMAs. Below is an example of the NHRP Mappings Configuration section which is empty by default. To add a new configuration, simply click the 'Add' button:


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


To add a new configuration click the 'Add' button and it will appear in the 'NHRP Mappings Configuration' list.
The newly added configuration should appear in the NHRP Mappings Configuration list and look similar to this:


[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_edit.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_routing_dynamic_routes_nhrp_interfaces_nhrp_mappings_configuration_edit.png|border|class=tlt-border]]
Line 1,141: Line 1,134:
     <tr>
     <tr>
         <td>IP Address</td>
         <td>IP Address</td>
         <td>ip; default: <b>none</b></td>
         <td>ip4; default: <b>none</b></td>
         <td>Network ID of another NHRP.</td>
         <td>Network ID of another NHRP router.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>NBMA</td>
         <td>NBMA</td>
         <td>ip; default: <b>none</b></td>
         <td>ip4; default: <b>none</b></td>
         <td>IP address of next-hop server.</td>
         <td>IP address of a Next-Hop server.</td>
     </tr>
     </tr>
</table>|}}
</table>|}}
[[Category:{{{name}}} Network section]]
[[Category:{{{name}}} Network section]]

Revision as of 07:34, 21 October 2020

Template:Networking rutos manual fw disclosure

Summary

The Routing page is used to set up static routes, routing tables and rules.

This manual page provides an overview of the Routing windows in {{{name}}} devices.

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

Static Routes

Routes 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 Static IPv4 Routes 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.

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.

Field Value Description
Interface network interface; default: lan Network interface of the target network.
Target* ip4; default: none Destination network address.
IPv4-Netmask* netmask; default: none 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.
IPv4-Gateway ip4; default: none 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.
Metric integer [0..255]; default: none The metric value acts as a measurement of priority. If a packet about to be routed matches two or more rules, the one with the lower metric is applied.
MTU integer [64..9000]; default: 1500 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.
Route Type unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: unicast Selects route type. Each type specifies a different behavior for the route:
  • unicast - most common type of route, simply describes a path to a destination.
  • local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.
  • broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.
  • multicast - used for distribution of multicast traffic.
  • unreachable - 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.
  • prohibit - 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.
  • blackhole - packets that match this type of route are discarded without any response.
  • anycast - provides a possibility to route incoming requests to multiple different network locations.
  • -- custom -- - does not use any of the predefined route types.

*Additional notes on 'Target' & 'Netmask' fields:

You can define a rule that applies to a single IP like this:

  • Target: some IP
  • Netmask: 255.255.255.255

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

Target Netmask Network range
192.168.2.0 255.255.255.240 192.168.2.0 - 192.168.2.15
192.168.2.240 255.255.255.240 192.168.2.240 - 192.168.2.255
192.168.2.161 255.255.255.0 192.168.2.0 - 192.168.55.255
192.168.0.0 255.255.0.0 192.168.0.0 - 192.168.255.255
192.168.2.161 255.255.255.255 192.168.2.161

Static IPv6 Routes

The Static IPv6 Routes 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.

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.

Field Value Description
Interface network interface; default: lan Network interface of the target network.
Target ip6; default: none Destination network address.
IPv6-Gateway ip6; default: none 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.
Metric integer [0..255]; default: none The metric value acts as a measurement of priority. If a packet about to be routed matches two or more rules, the one with the lower metric is applied.
MTU integer [64..9000]; default: 1500 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.
Route Type unicast | local | broadcast | multicast | unreachable | prohibit | backhole | anycast | -- custom -- ; default: unicast Selects route type. Each type specifies a different behavior for the route:
  • unicast - most common type of route, simply describes a path to a destination.
  • local - routes of this type are added to the 'local' routing table and used only for locally hosted IPs.
  • broadcast - routes of this type are added to the 'local' routing table and used by link layer devices that support the broadcast address principle.
  • multicast - used for distribution of multicast traffic.
  • unreachable - 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.
  • prohibit - 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.
  • blackhole - packets that match this type of route are discarded without any response.
  • anycast - provides a possibility to route incoming requests to multiple different network locations.
  • -- custom -- - does not use any of the predefined route types.

Advanced Static Routes

The Advanced Static Routes section is used to configure policy-based routing infrastructures, which are usually used in more complex or specific networking scenarios.

Routing Tables

Routing Tables store network routes. Tables are checked before every routing decision until a matching route is found. Having multiple tables allows the user to set up a policy routing infrastructure. Policy-based routing is a technique where routing decisions are based on policies (rule) set by the user.

The 'Routing Tables' section displays user created routing tables. By default, the list is empty.

To create a new table, look to the 'Add New Routing Table' section below. Enter an ID for the new table in the range of [1..252], enter a custom name and click the 'Add' button. The new table should appear in the 'Routing Tables' list. Click the 'Edit' button next to it to begin editing.

Refer to the table below for information on configuration fields for routing tables.

Field Value Description
ID of Table integer [1..252]; default: none Unique numerical identifier for the table. A table can be invoked by the both its ID or name.
Name of Table string; default: none A custom name for the table. A table can be invoked by the both its ID or name.

Routing Rules For IPv4

Routing Rules provide a way to route certain packets with exceptions, i.e., in accordance to a rule. 'Routing Rules For IPv4' displays user defined routing rules. It is empty by default. To create a new rule, click the 'Add' button and begin editing by clicking the 'Edit' button located to the right of the newly created rule.

Refer to table below for information on each configuration field.

Field Value Description
Priority integer [0..65535]; default: none Controls the order of IP rules. Rules with a lower priority value will be checked first.
Incoming interface network interface | Any; default: Any Logical interface name for incoming traffic. Select 'Any' to make the rule apply to all network interfaces.
Outgoing interface network interface | None; default: None Logical interface name for incoming traffic. Select 'None' to ignore outgoing interface.
Source subnet netmask; default: none Source subnet to match the rule.
Destination subnet netmask; default: none Destination subnet to match the rule.
TOS Value to Match integer [0..255]; default: none The type of service (ToS) value to match in IP headers.
Firewall Mark integer [0..255] | hex [0x00..0xFF]; default: none Specifies the fwmark and optionally its mask to match. For example, 0xFF to match mark 255 or 0x0/0x1 to match any even mark value.
Invert matches off | on; default: off If enabled, the meaning of the match options (Firewall Mark, TOS Value, Source and Destination subnets) is inverted.
Matched Traffic Action Lookup Table | Jump to rule | Routing Action; default: Lookup Table When network traffic matches this rule, the device will take an action specified in this field:
  • Lookup Table - routes traffic in accordance with the specified routing table.
  • Jump to rule - specifies another routing rule to follow.
  • Routing Action - executes one of four predefined routing actions.
Lookup Table routing table; default: none Specifies a table for routing traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to Lookup Table.
Jump to rule rule priority number; default: none Specifies a another rule to follow for traffic that matches this rule. This field is visible only when 'Matched Traffic Action' is set to Jump to rule.
Routing Action Prohibit | Unreachable | Blackhole | Throw; default: Prohibit When traffic matches this rule, the action specified in this field will be executed. This field is visible only when 'Matched Traffic Action' is set to Routing Action.

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

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_routing&oldid=73667"