I think you're probably using l2_learning, which installs exact match table entries. In OpenFlow, exact matches always have maximum priority -- you can't override it.
Here are some options for getting around the problem: 1. Make the "exceptional" table entries you install *also* be at maximum priority, overriding the ones that l2_learning installed. 2. If you're using Open vSwitch, use the multiple table extension. Put your exceptional entries in table 0 and have l2_learning install into table 1. Have a lowest-priority match-all entry in table 0 just submit to table 1. 3. Don't install exact matches to begin with; do something more like l2_pairs. Good luck. -- Murphy On May 16, 2015, at 9:00 AM, Kostas Chartsias <kcharts...@yahoo.gr> wrote: > another question and thanks for the support,Murphy you rule !!! > > I modify the L2_switch and i install flow rules after an event > accurs.Everything works fine,but there is a problem. > When it behaves as normal switch it installs rules with maximum priority > 65535 even though i set msg.priotiry a low value .It seams as i can't change > the flows priority for the switch,so i have to wait until timeouts expire and > the new flows from my event will work.Have you experienced similare thing > with overlapping flow matches? > > p.s. i used dpctl and i saw the flow of the switch always 65535,and the > others with my lower priority > > (i only added priority in the openflow mod message which installs flows,above > default switch timeouts) > > Thanks in advance!!! >
