With ODL of-1.3, i am not getting the packet-in messages

asked 2015-07-01 03:41:25 -0800

deepak660d gravatar image

updated 2015-07-01 03:42:14 -0800

Hi, I am trying to add the flows for dhcp priority=500,udp,inport=1,tpsrc=67,tpdst=68,actions=output:2,CONTROLLER:65535 priority=500,udp,inport=2,tpsrc=68,tpdst=67,actions=output:1,CONTROLLER:65535

There are some others hidden flows
-bash-3.2# ovs-appctl bridge/dump-flows br0 duration=3s, priority=500, npackets=0, nbytes=0, priority=500,udp,inport=1,tpsrc=67,tpdst=68,actions=output:2,CONTROLLER:65535 duration=3s, priority=500, npackets=0, nbytes=0, priority=500,udp,inport=2,tpsrc=68,tpdst=67,actions=output:1,CONTROLLER:65535 tableid=1, duration=16045s, priority=0, npackets=0, nbytes=0, priority=0,reg0=0x3,actions=drop tableid=1, duration=16045s, priority=0, npackets=5042, nbytes=592141, priority=0,reg0=0x1,actions=controller(reason=nomatch) tableid=1, duration=16045s, priority=0, npackets=0, nbytes=0, priority=0,reg0=0x2,actions=drop

Packets forwarding happening over OVS but not getting the packet-in .

This is only happening with OF-1.3 not OF-1.0 . Could anybody tell me the reason . Am i doing something wrong ? please help me out .

edit retag flag offensive close merge delete

Comments

Have you instructed the controller to work with openflow13 through the use of the flag -of13 when starting the controller ?

Nuno ( 2015-07-02 17:09:43 -0800 )edit

can you verify the switch is connected to the controller? if connected, what do the flows look like in the operational store of the controller?

jamoluhrsen ( 2015-07-06 16:07:29 -0800 )edit

Thanks for all of your comments . I was using old wireshark to see the of-1.3 . That's why i was not getting the packet-in packets

deepak660d ( 2015-07-10 10:15:22 -0800 )edit