Difference between revisions of "Manual:Fast Path"

From MikroTik Wiki
Jump to: navigation, search
m (Added information about unsupported interfaces)
Line 10: Line 10:
  
 
==List of devices with FastPath support==
 
==List of devices with FastPath support==
 +
 +
Interface FastPath support can be checked by doing "/interface print detail" and seeing fast-path property value.
  
  
Line 50: Line 52:
 
</tr>
 
</tr>
 
<tr>
 
<tr>
   <td ><b>All RouterBOARD devices</b></td>
+
   <td ><b>All devices</b></td>
   <td >wireless interfaces, if wireless-fp package used</td>
+
   <td >wireless interfaces, if wireless-fp or wireless-cm2 package used</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
   <td ><b>x86</b></td>
+
   <td ></td>
   <td >wireless interfaces, if wireless-fp package used</td>
+
   <td >bridge interfaces (since 6.29)</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 75: Line 77:
 
IPv4 fast path is automatically used if following conditions are met:
 
IPv4 fast path is automatically used if following conditions are met:
  
* [[M:IP/Firewall | firewal rules]] are not configured,
+
* [[M:IP/Firewall | firewal rules]] are not configured;
* Traffic flow is disabled <code>/ip traffic-flow enabled=no</code>
+
* Traffic flow is disabled <code>/ip traffic-flow enabled=no</code>;
* Simple and [[Manual:Queue| queue]] trees with parent=global are not configured.
+
* Simple and [[Manual:Queue| queue]] trees with parent=global are not configured;
* source interface is not [[M:Interface/Bridge | bridge]] port or [[M:Interface/Bonding | bonding]] slave
+
* destination interface queue is set to [[Manual:Queue#Queue_Types | only-hw-queue]] and no queue tree entries with parent="dst interface";
* destination interface queue is set to [[Manual:Queue#Queue_Types | only-hw-queue]] and no queue tree entries with parent="dst interface"
+
* no [[M:Interface/HWMPplus | mesh]], [[M:Metarouter | metarouter]] interface configuration;
* no [[M:Interface/HWMPplus | mesh]], [[M:Metarouter | metarouter]] interface configuration,
+
* [[M:Tools/Packet_Sniffer | sniffer]], [[M:Troubleshooting_tools#Torch_.28.2Ftool_torch.29 | torch]] and [[M:Tools/Traffic_Generator | traffic generator]] is not running;
* [[M:Tools/Packet_Sniffer | sniffer]], [[M:Troubleshooting_tools#Torch_.28.2Ftool_torch.29 | torch]] and [[M:Tools/Traffic_Generator | traffic generator]] is not running
+
* connection tracking is not active;
* connection tracking is not active
 
 
* ip accounting is disabled (/ip accounting enabled=no);
 
* ip accounting is disabled (/ip accounting enabled=no);
 
* VRFs are not set (/ip route vrf is empty);
 
* VRFs are not set (/ip route vrf is empty);
 
* Hotspot is not used (/ip hostspot has no interfaces);
 
* Hotspot is not used (/ip hostspot has no interfaces);
* IpSec policies are not configured (ROS v6.8)
+
* IpSec policies are not configured (ROS v6.8);
 +
* no active mac-ping, mac-telnet or mac-winbox sessions;
 +
* /tool mac-scan is not used;
 +
* /tool ip-scan is not used;
 +
* /tool wol is not used;
 +
* /interface mesh traceroute is not used;
 +
 
  
  

Revision as of 14:53, 4 June 2015

Version.png

Applies to RouterOS: v6.0rc2 +

Summary

Fast path allows to forward packets without additional processing in the Linux kernel. It improves forwarding speeds significantly.

For fast path to work, interface support and specific configuration conditions are required.

List of devices with FastPath support

Interface FastPath support can be checked by doing "/interface print detail" and seeing fast-path property value.


RouterBoard Interfaces
RB6xx series ether1,2
RB7xx series all ethernets
RB8xx series ether1,2
RB9xx series all ethernets
RB1000 all ethernets
RB1100 series ether1-10,11
RB2011 series all ethernets and sfp
CCR series routers all ethernets and sfps
All devices wireless interfaces, if wireless-fp or wireless-cm2 package used
bridge interfaces (since 6.29)

FastPath Handlers

Currently RouterOS has following fast path handlers:

  • ipv4
  • traffic generator
  • mpls
  • bridge
Icon-note.png

Note: Packet will be forwarded in fast path only if source and destination interfaces support fast path. See the list of supported interfaces.



IPv4 handler

IPv4 fast path is automatically used if following conditions are met:

  • firewal rules are not configured;
  • Traffic flow is disabled /ip traffic-flow enabled=no;
  • Simple and queue trees with parent=global are not configured;
  • destination interface queue is set to only-hw-queue and no queue tree entries with parent="dst interface";
  • no mesh, metarouter interface configuration;
  • sniffer, torch and traffic generator is not running;
  • connection tracking is not active;
  • ip accounting is disabled (/ip accounting enabled=no);
  • VRFs are not set (/ip route vrf is empty);
  • Hotspot is not used (/ip hostspot has no interfaces);
  • IpSec policies are not configured (ROS v6.8);
  • no active mac-ping, mac-telnet or mac-winbox sessions;
  • /tool mac-scan is not used;
  • /tool ip-scan is not used;
  • /tool wol is not used;
  • /interface mesh traceroute is not used;


/ip firewall connection tracking set enabled parameter has new auto value Which means that connection tracking is disabled by default until firewall rules are added.


Icon-note.png

Note: Starting from v6.1 added VRRP interface no longer disables fast path globally. Ipv4 and bridge fast path handlers will not work only if source interface is vrrp slave interface.



Traffic Generator handler

Traffic Generator fast path is automatically used for interfaces that support this feature.


MPLS handler

MPLS fast path is automatically used for interfaces that support this feature.

Currently MPLS fast-path applies only to MPLS switched traffic (frames that enter router as MPLS and must leave router as MPLS) - MPLS ingress and egress (including VPLS tunnel endpoints that do VPLS encap/decap) will operate as before.


Bridge handler

Bridge fast path is automatically used if following conditions are met:

  • no bridge firewall rules (/interface bridge filter, /interface bridge nat) are configured,
  • /interface bridge settings use-ip-firwall=no,
  • destination interface queue is set to only-hw-queue,
  • no mesh, metarouter interface configuration,
  • sniffer, torch and traffic generator is not running,
  • if wireless is configured, then wireless-fp or wireless-cm2 package must be used in order to use FastPath
Icon-note.png

Note: Currently VLAN, PPP and Bonding interfaces does not support FastPath


[ Top | Back to Content ]