I wouldn't say there is such a thing as a default action. There are entries consisting of a match plus actions. When an entry matches, its actions are executed. I'd also say there is a "miss action" which is executed when no entry matches. In OpenFlow 1.0, this isn't adjustable -- it's always send-to-controller.
You can create your own "default action" using multiple tables, though: table 0: <Wildcard> : resubmit(table=1), flood() .. now the "default action" is to flood. The "real" entries should now be in table 1. If an entry in table 1 wants to avoid the default action, it needs to explicitly end with an exit action. -- Murphy On Dec 8, 2013, at 11:03 PM, Jayanth Silesh <jayanthsileshs.for...@gmail.com> wrote: > Hello, > > I have two flow entries in my table1: > > cookie=0x0, duration=66.042s, table=1, n_packets=62, n_bytes=2604, > idle_age=3, hard_age=62, in_port=1 actions=load:0x7->NXM_NX_REG5[] > cookie=0x0, duration=66.042s, table=1, n_packets=0, n_bytes=0, idle_age=66, > in_port=2, NXM_NX_REG5[]=0x7 actions=output:1 > > > So, when the packet is received, it will match will the flow entry1 but the > action is just to change the value of the register only. > So does the switch drop the packet after changing the register value? > If so, then drop is the default action. Is there any way to change the > default action for a particular table? > > > Thanks, > Jayanth
