On Dec 8, 2013, at 11:03 PM, Jayanth Silesh <jayanthsileshs.for...@gmail.com> wrote:
> 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? Yes, if you don't tell it to do something with the packet. You'll want to add a "resubmit" action to that first rule to have it reconsult the table. > If so, then drop is the default action. Is there any way to change the > default action for a particular table? In this case, it's not that the default action is a drop; it's that the packet matched a flow entry with no forwarding or resubmit action specified, which means nothing is done with the packet. If a flow entry cannot be found, it will be sent to the controller. You can put in a low priority rule with a default action, but that's not really the issue you're having. --Justin
