In plain OpenFlow 1.0, this isn't possible because l2_learning installs exact
matches, which have maximum priority. There are at least two ways to fix this:
1) Don't install exact matches for normal learning. This is pretty reasonable,
actually. l2_pairs, for example, installs rules that just match Ethernet
addresses. These matches can be at whatever priority you want.
2) If you're using a switch which has Nicira extensions (e.g., Open vSwitch),
you can take advantage of multiple tables. Have l2_learning install its
entries into table 1. Put a low priority wildcard entry into table 0 that just
resubmits to table 1. So normal traffic will hit that wildcard entry and go
to table 1 and then be processed as usual. Then put whatever exceptional
entries you want in table 0 too. They'll always be matched before the ones
installed into table 1.
-- Murphy
On Jun 28, 2015, at 5:59 PM, Talal Alharbi tal...@hotmail.com wrote:
I have already looked at it before and did not work because I need higher
priority than rules installed by l2_learning after ping.
From: sul...@gmail.com
Date: Sun, 28 Jun 2015 20:19:31 -0400
Subject: Re: [pox-dev] Set Priority on Flow Rules
To: tal...@hotmail.com
CC: pox-dev@lists.noxrepo.org
You can find some clues in the documentation here:
https://openflow.stanford.edu/display/ONL/POX+Wiki#POXWiki-OpenFlowMessages
Straight from the documentation:
priority (int) - the priority at which a rule will match, higher numbers
higher priority. Note: Exact matches will have highest priority.
On Sun, Jun 28, 2015 at 8:12 PM, Talal Alharbi tal...@hotmail.com wrote:
Dear All,
I need to a high priority to the rules I would like to preformed first. I
have tried different values but none of them work. Could you please advise me
?
Cheers,
Talal
