Difference between revisions of "Manual:IP/Fasttrack"

From MikroTik Wiki
Jump to: navigation, search
(Created page with "=== IPv4 FastTrack handler=== IPv4 FastTrack handler is automatically used for marked connections. Use firewall action "fasttrack-connection" to mark connections for fasttrac...")
 
 
(40 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=== IPv4 FastTrack handler===
+
{{Versions|v6.29 +}}
  
IPv4 FastTrack handler is automatically used for marked connections. Use firewall action "fasttrack-connection" to mark connections for fasttrack. Currently only TCP and UDP connections can be actually fasttracked (even though any connection can be marked for fasttrack). IPv4 FastTrack handler supports NAT (SNAT, DNAT or both). FastTrack is supported on the specific [[M:Fast_Path#List_of_devices_with_FastPath_support | boards]].
+
__TOC__
  
Note that not all packets in a connection can be fasttracked, so it is likely to see some packets going through slow path even though connection is marked for fasttrack. Fasttracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, <del>ip traffic-flow</del>(restriction removed in 6.33), ip accounting, ipsec, hotspot universal client, vrf assignment, so it is up to administrator to make sure fasttrack does not interfere with other configuration;
+
=== Description ===
 +
IPv4 FastTrack handler is automatically used for marked connections. Use firewall action "fasttrack-connection" to mark connections for FastTrack. Currently only TCP and UDP connections can be actually FastTracked (even though any connection can be marked for FastTrack). IPv4 FastTrack handler supports NAT (SNAT, DNAT or both).  
  
 +
Note that not all packets in a connection can be FastTracked, so it is likely to see some packets going through slow path even though connection is marked for FastTrack. This is the reason why fasttrack-connection is usually followed by identical action=accept rule. FastTracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, <del>ip traffic-flow</del>(restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure FastTrack does not interfere with other configuration;
 +
 +
=== Requirements ===
 
IPv4 FastTrack is active if following conditions are met:
 
IPv4 FastTrack is active if following conditions are met:
  
Line 12: Line 16:
 
* /tool mac-scan is not actively used;
 
* /tool mac-scan is not actively used;
 
* /tool ip-scan is not actively used;
 
* /tool ip-scan is not actively used;
 +
* FastPath and Route cache is enabled under IP/Settings
 +
 +
=== Supported hardware ===
 +
FastTrack is supported on the listed devices.
 +
 +
<table class="styled_table">
 +
<tr>
 +
  <th width="100">RouterBoard</th>
 +
  <th width="300">Interfaces</th>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB6xx series</b></td>
 +
  <td >ether1,2</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB7xx series</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB800</b></td>
 +
  <td >ether1,2</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB9xx series</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB1000</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB1100, RB1000AHx2</b></td>
 +
  <td >ether1-11</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB1000AHx2</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB2011 series</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB3011 series</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>RB4011 series</b></td>
 +
  <td >all ports</td>
 +
</tr>
 +
<tr>
 +
  <td ><b>CRS series routers</b></td>
 +
  <td >all ports except management interface (if the device has one) </td>
 +
</tr>
 +
<tr>
 +
  <td ><b>CCR series routers</b></td>
 +
  <td >all ports except management interface (if the device has one) </td>
 +
</tr>
 +
<tr>
 +
  <td ><b>All devices</b></td>
 +
  <td >wireless interfaces, if wireless-fp, wireless-cm2, wireless-rep or wireless (starting from 6.37) package used</td>
 +
</tr>
 +
</table>
  
For example, in home routers with factory default configuration, you could Fasttrack all LAN traffic with this one rule placed at the top of the Firewall Filter. The same configuration accept rule is required:
+
=== Examples ===
 +
==== Initial configuration ====
 +
For example, in home routers with factory default configuration, you could FastTrack all LAN traffic with this one rule placed at the top of the Firewall Filter. The same configuration accept rule is required:
  
 
  /ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related
 
  /ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related
 
  /ip firewall filter add chain=forward action=accept connection-state=established,related
 
  /ip firewall filter add chain=forward action=accept connection-state=established,related
  
Note, that this will break any filtering and Queues you apply for LAN traffic, you will have to mark traffic first, if you want to only fasttrack specific traffic.
+
View of simple FastTrack rules in the firewall, it is important to have other filter or mangle rules to get the advantage of the FastTrack:
 +
* /ip firewall filter
 +
[[File:Fasttrack1_example.png|center|frame]]
 +
* /ip firewall mangle
 +
[[File:Screenshot 2015-11-27 09.40.09.png|center|frame]]
 +
{{ Warning | <b> Queues (except Queue Trees parented to interfaces), firewall filter and mangle rules will not be applied for FastTracked traffic.</b>}}
 +
* Connection is FastTracked until connection is closed, timed-out or router is rebooted.
 +
* Dummy rules will dissapear only after FastTrack firewall rules will be deleted/disabled and router rebooted.
  
This is how a default configuration looks with fastpath rule added on top (and auto-added dummy rule above it):
+
==== FastTrack on RB2011 ====
 +
FastTrack is enabled on RB2011 at chain=forward with the rule from previous example. Bandwidth test with single TCP stream is sent,
 +
[[File:Fasttrackon2011.png|center|frame]]
  
[[File:fasttrack.png]]
+
[[Category:Manual|Firewall|Fasttrack]]

Latest revision as of 10:18, 10 December 2018

Version.png

Applies to RouterOS: v6.29 +

Description

IPv4 FastTrack handler is automatically used for marked connections. Use firewall action "fasttrack-connection" to mark connections for FastTrack. Currently only TCP and UDP connections can be actually FastTracked (even though any connection can be marked for FastTrack). IPv4 FastTrack handler supports NAT (SNAT, DNAT or both).

Note that not all packets in a connection can be FastTracked, so it is likely to see some packets going through slow path even though connection is marked for FastTrack. This is the reason why fasttrack-connection is usually followed by identical action=accept rule. FastTracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, ip traffic-flow(restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure FastTrack does not interfere with other configuration;

Requirements

IPv4 FastTrack is active if following conditions are met:

  • no mesh, metarouter interface configuration;
  • sniffer, torch and traffic generator is not running;
  • no active mac-ping, mac-telnet or mac-winbox sessions restriction removed in 6.33;
  • /tool mac-scan is not actively used;
  • /tool ip-scan is not actively used;
  • FastPath and Route cache is enabled under IP/Settings

Supported hardware

FastTrack is supported on the listed devices.

RouterBoard Interfaces
RB6xx series ether1,2
RB7xx series all ports
RB800 ether1,2
RB9xx series all ports
RB1000 all ports
RB1100, RB1000AHx2 ether1-11
RB1000AHx2 all ports
RB2011 series all ports
RB3011 series all ports
RB4011 series all ports
CRS series routers all ports except management interface (if the device has one)
CCR series routers all ports except management interface (if the device has one)
All devices wireless interfaces, if wireless-fp, wireless-cm2, wireless-rep or wireless (starting from 6.37) package used

Examples

Initial configuration

For example, in home routers with factory default configuration, you could FastTrack all LAN traffic with this one rule placed at the top of the Firewall Filter. The same configuration accept rule is required:

/ip firewall filter add chain=forward action=fasttrack-connection connection-state=established,related
/ip firewall filter add chain=forward action=accept connection-state=established,related

View of simple FastTrack rules in the firewall, it is important to have other filter or mangle rules to get the advantage of the FastTrack:

  • /ip firewall filter
Fasttrack1 example.png
  • /ip firewall mangle
Screenshot 2015-11-27 09.40.09.png
Icon-warn.png

Warning: Queues (except Queue Trees parented to interfaces), firewall filter and mangle rules will not be applied for FastTracked traffic.


  • Connection is FastTracked until connection is closed, timed-out or router is rebooted.
  • Dummy rules will dissapear only after FastTrack firewall rules will be deleted/disabled and router rebooted.

FastTrack on RB2011

FastTrack is enabled on RB2011 at chain=forward with the rule from previous example. Bandwidth test with single TCP stream is sent,

Fasttrackon2011.png