Default action in OpenFlow 1.3

  • 1 Replies


  • Newbie
  • *
  • 1
    • View Profile
Default action in OpenFlow 1.3
« on: July 17, 2018, 05:39:53 AM »
The Zodiac FX doesn't have any default flows in OpenFlow 1.3, all flows need to be added by a controller. In OpenFlow 1.0 the default table miss action is to send the packet to the controller but even then it is not an installed flow it's a pipeline action.

Is there a reason why this is not the default action with OpenFlow 1.3? Caused me some confusion when my controller that worked with Open vSwitch did not work with the Zodiac Fx. The default configuration of the floodlight controller also expects that apparently.

Is this just a decision made for the Zodiac Fx or something due to the OpenFlow specification?


Paul Zanna

  • Moderator
  • Sr. Member
  • *****
  • 373
    • View Profile
    • Northbound Networks
Re: Default action in OpenFlow 1.3
« Reply #1 on: July 17, 2018, 06:35:25 AM »
The default action for non-matching packets is different based on the OpenFlow version. In the OpenFlow 1.0 specification it states "If no matching entry can be found for a packet, the packet is sent to the controller over the secure channel.", however in the OpenFlow 1.3 spec it is "If the table-miss flow entry does not exist, by default packets unmatched by flow entries are dropped". A table-miss entry is basically a match everything flow and a lot of OpenFlow applications will use this to sent unknown packets to the controller, similar to what 1.0 would do by default.