Manual:Fast Path: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 17: | Line 17: | ||
* mpls fast path | * mpls fast path | ||
{{ Note | Packet will be forwarded in fast path only if source and destination interfaces support fast path.}} | |||
'''IPv4 handler''' | |||
IPv4 fast path is automatically used if following conditions are met: | IPv4 fast path is automatically used if following conditions are met: | ||
* [[firewal rules]] are not configured, | * [[M:IP/Firewall | firewal rules]] are not configured, | ||
* [[simple queues]] are not configured | * [[simple queues]] are not configured | ||
* source interface is not [[bridge]] or [[bonding]] slave | * source interface is not [[M:Interface/Bridge | bridge]] or [[M:Interface/Bonding | bonding]] slave | ||
* destination interface have configured [[only-hw-queue]], | * destination interface have configured [[only-hw-queue]], | ||
* no [[vrrp]], [[mesh]], [[metarouter]] interface configuration, | * no [[M:Interface/VRRP | vrrp]], [[M:Interface/HWMP_plus | mesh]], [[M:Metarouter | metarouter]] interface configuration, | ||
* [[sniffer]], [[torch]] or [[traffic generator]] is not running | * [[sniffer]], [[torch]] or [[traffic generator]] is not running | ||
* connection tracking is disabled | * connection tracking is disabled | ||
| Line 31: | Line 36: | ||
'''Traffic Generator handler''' | |||
Traffic Generator fast path is automatically used for interfaces that support this feature. | |||
{{cont}} | {{cont}} | ||
Revision as of 11:32, 8 October 2012
Applies to RouterOS: v6+
Summary
List of RouterBoards with FastPath support
FastPath Handlers
Currently RouterOS has three fast path handlers
- ipv4 fast path
- traffic generator
- mpls fast path
Note: Packet will be forwarded in fast path only if source and destination interfaces support fast path.
IPv4 handler
IPv4 fast path is automatically used if following conditions are met:
- firewal rules are not configured,
- simple queues are not configured
- source interface is not bridge or bonding slave
- destination interface have configured only-hw-queue,
- no vrrp, mesh, metarouter interface configuration,
- sniffer, torch or traffic generator is not running
- connection tracking is disabled
/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.
Traffic Generator handler
Traffic Generator fast path is automatically used for interfaces that support this feature.
[ Top | Back to Content ]