NORMAL is optional, and as a result, isn't supported by a lot of switches. If you want to confirm this, try replacing actions=NORMAL with another action that forwards it out a different port and see if this works.
The capabilities message from the switch should tell you information like this - the wireshark plugin for openflow is very useful On Tue, Mar 26, 2013 at 8:00 PM, Senthil <[email protected]>wrote: > Hi > > I need your help to making this use case working. > > My requirement is: > > To install a simple flow that matches the given src_ip, dst_ip, > ip_proto, tcp_dst to take user defined actions > - either one of NORMAL, DROP or REDIRECT to other switch based on a few > conditions > > - I have started the pox with l2_learning - pox py forwarding.l2_learning, > my_app. > > - Sent an HTTP packets from VM attached to the switch with dst -port 8000. > The HTTP server in the remote VM responds this request. > Working so far. > > - Installed a flow from my_app that matches HTTP Packets with dst-port > =8000 originated from a VM attached to the given switch. > > The flow installed in the switch ( highlight in RED below): > > ~$ ovs-dump > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=155.214s, table=0, n_packets=4, n_bytes=168, > idle_timeout=60, hard_timeout=180, idle_age=28, > priority=65535,arp,in_port=4,vlan_tci=0x0000,dl_src=5a:32:3e:41:79:3b,dl_dst=08:00:27:d9:77:cd,arp_spa=192.167.20.253,arp_tpa=192.167.20.10,arp_op=1 > actions=output:2 > > cookie=0x0, duration=155.194s, table=0, n_packets=4, n_bytes=240, > idle_timeout=60, hard_timeout=180, idle_age=28, > priority=65535,arp,in_port=2,vlan_tci=0x0000,dl_src=08:00:27:d9:77:cd,dl_dst=5a:32:3e:41:79:3b,arp_spa=192.167.20.10,arp_tpa=192.167.20.253,arp_op=2 > actions=output:4 > > cookie=0x0, duration=155.201s, table=0, n_packets=6, n_bytes=252, > idle_timeout=60, hard_timeout=180, idle_age=28, > priority=65535,arp,in_port=3,vlan_tci=0x0000,dl_src=36:32:b4:86:89:a4,dl_dst=08:00:27:ef:2a:ef,arp_spa=192.167.10.253,arp_tpa=192.167.10.10,arp_op=2 > actions=output:1 > > cookie=0x0, duration=155.209s, table=0, n_packets=6, n_bytes=360, > idle_timeout=60, hard_timeout=180, idle_age=28, > priority=65535,arp,in_port=1,vlan_tci=0x0000,dl_src=08:00:27:ef:2a:ef,dl_dst=36:32:b4:86:89:a4,arp_spa=192.167.10.10,arp_tpa=192.167.10.253,arp_op=1 > actions=output:3 > > cookie=0x40, duration=175.959s, table=0, n_packets=114, n_bytes=8436, > idle_age=0, > priority=20000,tcp,nw_src=192.167.10.10,nw_dst=192.167.20.10,tp_dst=8000 > actions=NORMAL > > > My expectation is: > The installed flow with action NORMAL should switch the packets to > follow the normal switch forwarding. Since all the arp entries are there, > it should find the path using the normal forwarding... > > This use case makes the apps to install its own flow that redirects the > packets to meet its own requirements - thus making it as software defined > path... > > What happens after installing this flow : The HTTP packets are not > forwarded. > > > Please validate if my expectation in behavior is right. > > If not, how to acheive this use case.. I have to install my own flow and > use the normal switching to carry the packet. > With this simple flow with NORMAL action, I can stats specific to this > flow now. And later I can sleectively drop or redirct it. > > > > Thanks > =Senthil > > > But what happens after installing this flow: Th >
