Manual:OpenFlow: Difference between revisions
| (5 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
This page contains information on OpenFlow switch support in RouterOS. | This page contains information on OpenFlow switch support in RouterOS. | ||
For information about OpenFlow see https://www.opennetworking.org/ | For information about OpenFlow see https://www.opennetworking.org/ | ||
Currently RouterOS implements OpenFlow version 1.0.0 required features. Support for newer versions, optional features and switching hardware acceleration are to be added. Current implementation should be considered experimental - <b>NOT production ready</b> and is available for evaluation purposes. | Currently RouterOS implements OpenFlow version 1.0.0 required features. Support for newer versions, optional features and switching hardware acceleration are to be added. Current implementation should be considered experimental - <b>NOT production ready</b> and is available for evaluation purposes. | ||
If you have any feature requests or bug reports please contact support. | |||
OpenFlow support is available as standalone openflow package. | OpenFlow support is available as standalone openflow package. | ||
| Line 13: | Line 15: | ||
OpenFlow feature overrides regular packet processing functionality - packets that are received on interfaces that are OpenFlow switch ports, will not pass through the regular networking stack unless OpenFlow controller sets up flows that enable this. Due to this care must be taken to not disable access to the device when configuring OpenFlow. | OpenFlow feature overrides regular packet processing functionality - packets that are received on interfaces that are OpenFlow switch ports, will not pass through the regular networking stack unless OpenFlow controller sets up flows that enable this. Due to this care must be taken to not disable access to the device when configuring OpenFlow. | ||
Currently only unencrypted TCP is available as communications channel between RouterOS OpenFlow switch and controller. | Currently only unencrypted TCP is available as the communications channel between RouterOS OpenFlow switch and controller. | ||
{{Warning | Actions to set network layer src and dst are not supported (<b>OFPAT_SET_NW_SRC, OFPAT_SET_NW_DST</b>)}} | |||
== Configuration == | == Configuration == | ||
| Line 26: | Line 32: | ||
<pre> | <pre> | ||
[admin@MikroTik] > /openflow port add switch=ofswitch1 interface=ether2 | [admin@MikroTik] > /openflow port add switch=ofswitch1 interface=ether2 | ||
[admin@MikroTik] > /openflow port add switch=ofswitch1 interface= | [admin@MikroTik] > /openflow port add switch=ofswitch1 interface=ether3 | ||
</pre> | </pre> | ||
Latest revision as of 11:54, 12 February 2018
Overview
This page contains information on OpenFlow switch support in RouterOS.
For information about OpenFlow see https://www.opennetworking.org/
Currently RouterOS implements OpenFlow version 1.0.0 required features. Support for newer versions, optional features and switching hardware acceleration are to be added. Current implementation should be considered experimental - NOT production ready and is available for evaluation purposes.
If you have any feature requests or bug reports please contact support.
OpenFlow support is available as standalone openflow package.
OpenFlow feature overrides regular packet processing functionality - packets that are received on interfaces that are OpenFlow switch ports, will not pass through the regular networking stack unless OpenFlow controller sets up flows that enable this. Due to this care must be taken to not disable access to the device when configuring OpenFlow.
Currently only unencrypted TCP is available as the communications channel between RouterOS OpenFlow switch and controller.
Warning: Actions to set network layer src and dst are not supported (OFPAT_SET_NW_SRC, OFPAT_SET_NW_DST)
Configuration
RouterOS supports multiple OpenFlow switch instances, each of which can have separate controller(s) and sets of ports.
Switch instance can be added using command:
[admin@MikroTik] > /openflow add name=ofswitch1 controllers=10.0.0.18
Switch ports can be added using command:
[admin@MikroTik] > /openflow port add switch=ofswitch1 interface=ether2 [admin@MikroTik] > /openflow port add switch=ofswitch1 interface=ether3