Difference between revisions of "Manual:IP/Fasttrack"
|Line 2:||Line 2:|
=== Description ===
=== Description ===
Revision as of 06:42, 27 November 2015
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 boards.
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,
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;
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 sessionsrestriction removed in 6.33;
- /tool mac-scan is not actively used;
- /tool ip-scan is not actively used;
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
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.
This is how a default configuration looks with fastpath rule added on top (and auto-added dummy rule above it):