Template:Networking rutos manual routing: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
Line 350: Line 350:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns BGP protocol usage on or off.</td>
       <td>Turns BGP protocol usage on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable vty</td>
       <td>Enable vty</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns vty access on or off.</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
Line 379: Line 379:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns the BGP instance on or off.</td>
       <td>Turns the BGP instance on or off.</td>
     </tr>
     </tr>
Line 399: Line 399:
     <tr>
     <tr>
         <td>Redistribution options</td>
         <td>Redistribution options</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>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} 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>
     <tr>
     <tr>
         <td>Deterministic MED</td>
         <td>Deterministic MED</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Compares MEDs between same AS, while ignoring their age.</td>
         <td>Compares MEDs between same AS, while ignoring their age.</td>
     </tr>
     </tr>
Line 441: Line 441:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns turns this BGP peer on or off.</td>
       <td>Turns turns this BGP peer on or off.</td>
     </tr>
     </tr>
Line 452: Line 452:
The full BGP Peer configuration page should look similar to this:
The full BGP Peer configuration page should look similar to this:


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


<table class="nd-mantable">
<table class="nd-mantable">
Line 462: Line 462:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns this BGP peer on or off.</td>
       <td>Turns this BGP peer on or off.</td>
     </tr>
     </tr>
Line 484: Line 484:
         <td>integer; default: <b>none</b></td>
         <td>integer; default: <b>none</b></td>
         <td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
         <td>Time to Live value for packets associated with this remote BGP Neighbor.</td>
    </tr>
    <tr>
    <td>Keepalive timer</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>Frequency (in seconds) of keep alive messages.</td>
    </tr>
    <tr>
    <td>Holdtime</td>
        <td>integer [0..65535]; default: <b>none</b></td>
        <td>Max wait time (in seconds) for a response from this neighbor before considering the peer unreachable.</td>
    </tr>
    <tr>
    <td>Connect timer</td>
        <td>integer [1..65535]; default: <b>none</b></td>
        <td>Max time (in seconds) to make a connection to this peer. If a connection cannot be made in this time, connection to this peer is considered unsuccessful.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Default originate</td>
         <td>Default originate</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Announces default routes to this peer.</td>
         <td>Announces default routes to this peer.</td>
     </tr>
     </tr>
Line 545: Line 560:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns the BGP Peer Group configuration on or off.</td>
       <td>Turns the BGP Peer Group configuration on or off.</td>
     </tr>
     </tr>
Line 565: Line 580:
     <tr>
     <tr>
         <td>Neighbor configuration</td>
         <td>Neighbor configuration</td>
         <td>None <nowiki>|</nowiki> Route Reflector client <nowiki>|</nowiki> Route Server client; default: <b>None</b></td>
         <td>None {{!}} Route Reflector client {{!}} Route Server client; default: <b>None</b></td>
         <td>Defines the role of a BGP Neighbor.
         <td>Defines the role of a BGP Neighbor.
             <ul>
             <ul>
Line 575: Line 590:
     <tr>
     <tr>
         <td>Disable next hop calculation</td>
         <td>Disable next hop calculation</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} <span style="color: blue;"><b>on</b></span>; default: <b>off</b></td>
         <td>Turns next hop calculation for this BGP Peer Group on or off.</td>
         <td>Turns next hop calculation for this BGP Peer Group on or off.</td>
    </tr>
    <tr>
        <td><span style="color: blue;">Disable next hop calculation:</span> Apply also to ibgp-learned routes</td>
        <td>off {{!}} on; default: <b>off</b></td>
        <td>When acting as a route reflector, applies to ibgp-learned routes as well. This field becomes visible when 'Disable next hop calculation' is turned on.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Inbound soft-reconfiguration</td>
         <td>Inbound soft-reconfiguration</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Turns inbound soft-reconfiguration for this Neighbor on or off.</td>
         <td>Turns inbound soft-reconfiguration for this Neighbor on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Disable connected check</td>
         <td>Disable connected check</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>When turned on, Disable connected check enables a directly connected eBGP Neighbor to peer using a loopback address without adjusting the default TTL of 1.</td>
         <td>When turned on, Disable connected check enables a directly connected eBGP Neighbor to peer using a loopback address without adjusting the default TTL of 1.</td>
     </tr>
     </tr>
Line 613: Line 633:
     <tr>
     <tr>
     <td>Action</td>
     <td>Action</td>
         <td>Permit <nowiki>|</nowiki> Deny; default: <b>Permit</b></td>
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
         <td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
         <td>When BGP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Network</td>
         <td>ip/netmask <nowiki>|</nowiki> Any; default: <b>Any</b></td>
         <td>ip/netmask {{!}} Any; default: <b>Any</b></td>
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Direction</td>
     <td>Direction</td>
         <td>Inbound <nowiki>|</nowiki> Outbound; default: <b>Inbound</b></td>
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns an Access filter on or off.</td>
       <td>Turns an Access filter on or off.</td>
     </tr>
     </tr>
Line 651: Line 671:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns RIP Protocol usage on or off.</td>
       <td>Turns RIP Protocol usage on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable vty</td>
       <td>Enable vty</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns vty access on or off.</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
Line 666: Line 686:
     <tr>
     <tr>
     <td>Version</td>
     <td>Version</td>
         <td>2 <nowiki>|</nowiki> 1; default: <b>2</b></td>
         <td>2 {{!}} 1; default: <b>2</b></td>
         <td>Specifies the used version of the RIP protocol.</td>
         <td>Specifies the used version of the RIP protocol.</td>
     </tr>
     </tr>
Line 698: Line 718:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns a RIP Interface on or off.</td>
       <td>Turns a RIP Interface on or off.</td>
     </tr>
     </tr>
Line 708: Line 728:
     <tr>
     <tr>
     <td>Passive interface</td>
     <td>Passive interface</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
         <td>Sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and <b>ripd</b> does not send either multicast or unicast RIP packets.</td>
     </tr>
     </tr>
Line 740: Line 760:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns an Access filter on or off.</td>
       <td>Turns an Access filter on or off.</td>
     </tr>
     </tr>
Line 750: Line 770:
     <tr>
     <tr>
     <td>Action</td>
     <td>Action</td>
         <td>Permit <nowiki>|</nowiki> Deny; default: <b>Permit</b></td>
         <td>Permit {{!}} Deny; default: <b>Permit</b></td>
         <td>When RIP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
         <td>When RIP traffic matches this rule, the device will take the action specified in this field, which is to either allow or block traffic.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Network</td>
     <td>Network</td>
         <td>ip/netmask <nowiki>|</nowiki> Any; default: <b>Any</b></td>
         <td>ip/netmask {{!}} Any; default: <b>Any</b></td>
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
         <td>Matches traffic destined or originating from (depends on 'Direction' selection) to the network specified in this field.</td>
     </tr>
     </tr>
     <tr>
     <tr>
     <td>Direction</td>
     <td>Direction</td>
         <td>Inbound <nowiki>|</nowiki> Outbound; default: <b>Inbound</b></td>
         <td>Inbound {{!}} Outbound; default: <b>Inbound</b></td>
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
         <td>Matches network traffic direction, which can either be traffic destined to this device (Inbound) or traffic originating from this device (Outbound).</td>
     </tr>
     </tr>
Line 783: Line 803:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns OSPF Protocol usage on or off.</td>
       <td>Turns OSPF Protocol usage on or off.</td>
     </tr>
     </tr>
     <tr>
     <tr>
       <td>Enable vty</td>
       <td>Enable vty</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns vty access on or off.</td>
       <td>Turns vty access on or off.</td>
     </tr>
     </tr>
Line 842: Line 862:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns an OSPF Interface on or off.</td>
       <td>Turns an OSPF Interface on or off.</td>
     </tr>
     </tr>
Line 863: Line 883:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns the OSPF area on or off.</td>
       <td>Turns the OSPF area on or off.</td>
     </tr>
     </tr>
Line 893: Line 913:
     <tr>
     <tr>
         <td>Type</td>
         <td>Type</td>
         <td>Broadcast <nowiki>|</nowiki> Nonbroadcast <nowiki>|</nowiki> Point-to-point <nowiki>|</nowiki> Point-to-multipointl default: <b>none</b></td>
         <td>Broadcast {{!}} Nonbroadcast {{!}} Point-to-point {{!}} Point-to-multipointl default: <b>none</b></td>
         <td>OSPF interface configuration type.</td>
         <td>OSPF interface configuration type.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Authentication</td>
         <td>Authentication</td>
         <td>None <nowiki>|</nowiki> Password <nowiki>|</nowiki> MD5 HMAC; default: <b>None</b></td>
         <td>None {{!}} Password {{!}} MD5 HMAC; default: <b>None</b></td>
         <td>Specifies the Authentication method.</td>
         <td>Specifies the Authentication method.</td>
     </tr>
     </tr>
Line 935: Line 955:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns an OSPF Area on or off.</td>
       <td>Turns an OSPF Area on or off.</td>
     </tr>
     </tr>
Line 979: Line 999:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns the usage of this network (in OSPF) on or off.</td>
       <td>Turns the usage of this network (in OSPF) on or off.</td>
     </tr>
     </tr>
Line 1,002: Line 1,022:
     <tr>
     <tr>
       <td>Enable</td>
       <td>Enable</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns EIGRP protocol usage 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 {{!}} on; default: <b>off</b></td>
         <td>Turns logging of EIGRP traffic on or off.</td>
         <td>Turns logging of EIGRP traffic on or off.</td>
     </tr>
     </tr>
Line 1,027: Line 1,047:
     <tr>
     <tr>
         <td>Redistribution options</td>
         <td>Redistribution options</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>Connected routes {{!}} Kernel added routes {{!}} NHRP routes {{!}} OSPF routes {{!}} Static routes {{!}} 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 1,055: Line 1,075:
     <tr>
     <tr>
       <td>Enable service</td>
       <td>Enable service</td>
       <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
       <td>off {{!}} on; default: <b>off</b></td>
       <td>Turns NHRP protocol usage 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 {{!}} on; default: <b>off</b></td>
       <td>Turns NHRP traffic logging on or off.</td>
       <td>Turns NHRP traffic logging on or off.</td>
     </tr></table>
     </tr></table>
Line 1,094: Line 1,114:
     <tr>
     <tr>
         <td>Enabled</td>
         <td>Enabled</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Turns the NHRP Interface on or off.</td>
         <td>Turns the NHRP Interface on or off.</td>
     </tr>
     </tr>
Line 1,114: Line 1,134:
     <tr>
     <tr>
         <td>NHS</td>
         <td>NHS</td>
         <td>Dynamic <nowiki>|</nowiki> custom(ip4); default: <b>none</b></td>
         <td>Dynamic {{!}} custom(ip4); default: <b>none</b></td>
         <td>IP address of a Next-Hop server.</td>
         <td>IP address of a Next-Hop server.</td>
     </tr>
     </tr>
Line 1,129: Line 1,149:
     <tr>
     <tr>
         <td>IPsec support</td>
         <td>IPsec support</td>
         <td>off <nowiki>|</nowiki> <span style="color: red;">on</span>; default: <b>off</b></td>
         <td>off {{!}} <span style="color: red;">on</span>; default: <b>off</b></td>
         <td>Turns usage of NHRP over IPsec for this Interface on or off.</td>
         <td>Turns usage of NHRP over IPsec for this Interface on or off.</td>
     </tr>
     </tr>
Line 1,157: Line 1,177:
     <tr>
     <tr>
         <td>Enabled</td>
         <td>Enabled</td>
         <td>off <nowiki>|</nowiki> on; default: <b>off</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td>Turns this mapping configuration on or off.</td>
         <td>Turns this mapping configuration on or off.</td>
     </tr>
     </tr>

Revision as of 10:19, 24 November 2022

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
Name of Table string; default: none A custom name for the table. A table can be invoked by the both its ID or name.
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.

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=99315"