TCP is stream oriented, so there is no fixed relationship between packets and OpenFlow messages. One OpenFlow message could be spread across multiple packets, or one packet could contain multiple OpenFlow messages. Your screenshot shows an example of the latter -- a flow mod and a barrier just happen to have been stuck into the same packet. They're entirely independent OpenFlow messages.
Hope that clarifies things. -- Murphy On Feb 23, 2014, at 12:11 AM, ramesh oswal <rameshos...@gmail.com> wrote: > ---------- Forwarded message ---------- > From: ramesh oswal <rameshos...@gmail.com> > Date: Sat, 22 Feb 2014 03:04:26 +0530 > Subject: barrier request msg > To: gslab_project_zppr <gslab_project_z...@googlegroups.com> > > Hi , > I am trying to study barrier request msg but am unable to understand it > properly it has two openflow header in same packet one flow_mod type and > other barrier req type .I dont know what exactly is flow mod header doing > here . I am also a bit confused about barrier msg working .Plz if anyone > can help do post it here > PFA screenshot packet of a barrier request msg > <barrier req msg.png>
