If there are seven TCP connections, they are identifiable via properties of the connection itself (source/destination IP/port). You'd create seven table entries which match these unique properties of the connections, and these entries would have the proper enqueue actions. From your description, I don't understand why an ID is required.
-- Murphy On Oct 27, 2013, at 3:37 AM, Sayed Qaiser Ali Shah Shah <[email protected]> wrote: > What I am doing is explained below. > Lets suppose we have 7 flows of same traffic like http. What I want to do is > pass 4 flows via queue-1 and 3 flows from queue-2. That's why I need flow ID > so that I can identify flow by flow ID and forward that flows accordingly. > > > On Sun, Oct 27, 2013 at 9:17 AM, Murphy McCauley <[email protected]> > wrote: > Usually they're identified by their match criteria. Maybe it would help if > you explained further exactly what you're trying to accomplish. > > -- Murphy > > On Oct 26, 2013, at 2:17 PM, Sayed Qaiser Ali Shah Shah > <[email protected]> wrote: > >> Thanks Murphy McCauley for your response. >> Is there any other way with the help of which we can identify flow? >> >> >> On Sat, Oct 26, 2013 at 11:14 PM, Murphy McCauley >> <[email protected]> wrote: >> As far as I can tell, the OpenFlow 1.0 specification doesn't contain any >> reference to a "flow id", so I'm not sure what to tell you. >> >> -- Murphy >> >> On Oct 26, 2013, at 6:36 AM, Sayed Qaiser Ali Shah Shah >> <[email protected]> wrote: >> >>> As Flow Tables contain flow entries and as far as I know flow entry is >>> identified by flow id in flow table what I want to do is, using POX >>> controller I want to get flow ID from flow table. How can I do this? Is it >>> possible? >>> >>> -- >>> Regards >>> >>> Sayed Qaiser Ali Shah >>> MSIT-12 >>> NUST (SEECS) >> >> >> >> >> -- >> Regards >> >> Sayed Qaiser Ali Shah >> MSIT-12 >> NUST (SEECS) > > > > > -- > Regards > > Sayed Qaiser Ali Shah > MSIT-12 > NUST (SEECS)
