Hi Sergio, if you don't care to send out the buffered packet that triggered the packet_in (or if, for example, you just want to install a flow proactively) using buffer_id=-1 I think should work.
On Fri, Jan 13, 2012 at 8:09 AM, Sergio Jiménez Feijóo <jjji...@gmail.com>wrote: > Hi Guys, > > I'm having trouble trying to add several flowmods to my OpenFlow switches. > My application collects information from the network topology and > calculates a (layer 2) route for every flow. Then it performs flow-mods in > all the switches of the selected route in order to send the flow to its > destination. I'm using as an example the "coreapps/switch" flowmod code. > When my controller sends the flow-mod packets to the switches they respond > with an error message (Specified buffer does not exist). > > My app worked nicely on a testbed of 6 Linksys WRT54GL with an OpenFlow > capable firmware and NOX Zaku without FlowVisor. Now I'm using 5 NEC > IP8800/S3640-24T2XW with NOX Destiny and FlowVisor and I'm experiencing > this problem. Is the buffer_id really necessary? Can I add a flowmod > without specifying any buffer_id? How can I avoid this error? > > I don't care about the packets that arrived before the flowmod being > dropped. I just need to run a flowmod in several switches matching one > single packet (the same one). I want all the switches to learn how to treat > that type of packet all at the same time (I run a for loop in my code). > > Thank you for your help. > ______________________________**_________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/**listinfo/nox-dev<http://noxrepo.org/mailman/listinfo/nox-dev> >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
