I have a student working in this and one reason you would need flow identifiers is just to track user specified input. However, since each flow is unique as explained by Murphy, we actually track flows by ID at the controller end. We only send "normalized" flows to the controller. It is also good to remember that switches aren't obliged to resolved rules in a particular order. Although, I wish it has a most specific to least specific rule like routers. Sent on the move.
Thanks Murphy for your great support always. I will try this. :) On Mon, Oct 28, 2013 at 12:42 AM, Murphy McCauley <[email protected]> wrote:
Regards Sayed Qaiser Ali Shah MSIT-12 NUST (SEECS) | ||
- [pox-dev] Getting flow ID from Flow Table Sayed Qaiser Ali Shah Shah
- Re: [pox-dev] Getting flow ID from Flow Ta... Murphy McCauley
- Re: [pox-dev] Getting flow ID from Flo... Sayed Qaiser Ali Shah Shah
- Re: [pox-dev] Getting flow ID from... Murphy McCauley
- Re: [pox-dev] Getting flow ID ... Sayed Qaiser Ali Shah Shah
- Re: [pox-dev] Getting flo... Murphy McCauley
- Re: [pox-dev] Getting... Sayed Qaiser Ali Shah Shah
- Re: [pox-dev] Get... wyu
