Manual:Fast Path: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
==List of RouterBoards with FastPath support== | ==List of RouterBoards with FastPath support== | ||
<table class="styled_table"> | |||
<tr> | |||
<th width="100">RouterBoard</th> | |||
<th width="300">Interfaces</th> | |||
</tr> | |||
<tr> | |||
<td ><b>RB3xx series</b></td> | |||
<td >ether1,2</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB6xx series</b></td> | |||
<td >ether1,2</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB7xx series</b></td> | |||
<td >all ethernets</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB8xx series</b></td> | |||
<td >ether1,2</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB9xx series</b></td> | |||
<td >all ethernets</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB1000</b></td> | |||
<td >all ethernets</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB1100 series</b></td> | |||
<td >ether1-10,13</td> | |||
</tr> | |||
<tr> | |||
<td ><b>RB2011 series</b></td> | |||
<td >all ethernets and sfp</td> | |||
</tr> | |||
<tr> | |||
<td ><b>CCR series routers</b></td> | |||
<td >all ethernets and sfps</td> | |||
</tr> | |||
</table> | |||
==FastPath Handlers== | ==FastPath Handlers== | ||
Revision as of 11:50, 8 October 2012
Applies to RouterOS: v6+
Summary
List of RouterBoards with FastPath support
| RouterBoard | Interfaces |
|---|---|
| RB3xx series | ether1,2 |
| RB6xx series | ether1,2 |
| RB7xx series | all ethernets |
| RB8xx series | ether1,2 |
| RB9xx series | all ethernets |
| RB1000 | all ethernets |
| RB1100 series | ether1-10,13 |
| RB2011 series | all ethernets and sfp |
| CCR series routers | all ethernets and sfps |
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 ]