[pox-dev] Modifying existing flows on a switch periodically
Murphy McCauley
murphy.mccauley at gmail.com
Sun Dec 15 22:29:59 PST 2013
Set your flow-mod's .command attribute to OFPFC_MODIFY (or OFPFC_MODIFY_STRICT). If you've imported libopenflow as "of" (the POX convention), it's something like:
fm = of.ofp_flow_mod()
...
fm.command = of.OFPFC_MODIFY_STRICT
...
connection.send(fm)
-- Murphy
On Dec 15, 2013, at 10:16 PM, Sadia Bashir <11msccssbashir at seecs.edu.pk> wrote:
> Thank you Junaid Khalid and Murphy!
>
> I just got this from pox.openflow.libopenflow_o1
>
> ofp_flow_mod_command_rev_map = {
> 'OFPFC_ADD' : 0,
> 'OFPFC_MODIFY' : 1,
> 'OFPFC_MODIFY_STRICT' : 2,
> 'OFPFC_DELETE' : 3,
> 'OFPFC_DELETE_STRICT' : 4,
> }
>
>
> I am not getting clear how do I use it in flow-mods. Please refer me to some example for it. Thank you for your guide and help. Thanks a lot!
>
> sadia
>
>
> On Mon, Dec 16, 2013 at 7:20 AM, Murphy McCauley <murphy.mccauley at gmail.com> wrote:
> On Dec 14, 2013, at 1:56 PM, Sadia Bashir <11msccssbashir at seecs.edu.pk> wrote:
>
> > Hi,
> >
> > I want to modify queue_id in installed flows on a switch periodically by sending a flow_mod message from controller(i.e., controller-to-switch message) I tried it using this way on pox-controller:
> >
> > def _timer_func ():
> > for connection in core.openflow._connections.values():
> > connection.send(of.ofp_action_nw_tos(port = 1, queue_id = 2))
>
> This isn’t a flow-mod. This is just an action! Construct flow mods for the flows you want to change and include the new action.
>
> > def launch():
> > from pox.lib.recoco import Timer
> > Timer(4, _timer_func, recurring=True)
> >
> > Please tell me if there is a way to modify a value in already existing flow entries on the switch.
> >
> > Thanks in advance for any hint or help.
> > --
> > sadia
>
> Hope that helps.
>
> — Murphy
>
>
>
> --
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noxrepo.org/pipermail/pox-dev-noxrepo.org/attachments/20131215/df05a324/attachment-0002.htm>
More information about the pox-dev
mailing list