Hi, For exact matches, Openflow 1.0 sets the priority to highest value. For wildcard matches only, we can set the priority.
Thanks and Regards, Padma V On Thu, Oct 2, 2014 at 2:58 AM, JORDAN SA QUEIROZ <[email protected]> wrote: > Hi, folks. > I'm trying to set up a priority level on a flow rule, but the solution I > have tried didn't work. There is a piece of code where it is possible to > change the priority level (at least I think): > > > > > > *auto fm = > v1::ofp_flow_mod().match(flow).buffer_id(pi.buffer_id()) > .cookie(0).command(v1::ofp_flow_mod::OFPFC_ADD).idle_timeout(5) > .hard_timeout(v1::OFP_FLOW_PERMANENT) > .priority(LOW_PRIORITY); //v1::OFP_DEFAULT_PRIORITY > = 0x8000 auto ao = v1::ofp_action_output().port(out_port);* > > I'm trying to edit this field (the blue-marked one) because according with > I've searched, a priority level of a flow rule affects the order where the > match is done in the flowtable. > The problem is whenever I try to change the priority's level (by editing > this blue-marked-field), nothing happens (it is possible to realize it > using dpctl). According with NOX's documentation in doxygen ( > http://www.noxrepo.org/_/nox-doxygen/openflow-defs-1_80_8hh_source.html) > there is only DEFAULT_PRIORITY, which its value is set in hexadecimal. So I > have tried to set other values (lower values) in hexadecimal > (LOW_PRIORITY's value is 0x7000 and the DEFAULT_PRIORITY's value is > 0x8000), but whenever I check the priority's level in dpctl, it always > shows me priority's level in 65535 > > Does anyone have a solution to solve it?? > Thanks in advance. > > -- > Regards, > Jordan de Sá Queiroz > >
