Thanks! Your help was enough! :) I now understand for what all those structs are there.
They lean the reader into the wrong direction, because it got me the idea that there where structs within structs, when in fact there wasn't (instructions example). On 3 September 2013 16:54, Eder Leão Fernandes <ederleaofernan...@gmail.com>wrote: > Hi Carlos, > > The structs on the OpenFlow spec are just to show the format of the > messages (fields order, size, padding) , i.e how it should be sent through > the connection between the controller and the switch. > > The commented instruction field in the ofp_flow_mod struct are just an > indication that after the match elements (match header and OXM tlvs), an > instruction set should follow. > > The instructions set can contain one instruction of the type > OFPIT_WRITE_ACTIONS. If the packet matches the flow, the > OFPIT_WRITE_ACTIONS instruction will write actions to an actions set that > will be executed in the end of the OpenFlow pipeline (The figure on the > page 13 of the spec can give you a good overview of how it happens). > > I hope it helps. > Regards, > Eder > > On 3 September 2013 08:29, Carlos Ferreira <carlosmf...@gmail.com> wrote: > >> Hello! >> >> I have been reading the Openflow 1.3.2 specs in order to understand the >> inners of the protocol. The document is a bit confuse, mixing procedures >> and data structures without any concise diagrams, which makes it a bit >> difficult to understand. >> >> I'm having trouble with the OFPT_FLOW_MOD message, more specifically, >> knowing where the ofp_match structure relates with a set of actions to >> take, when the match is successful. >> >> Also, the ofp_instruction field in the ofp_flow_mod struct is commented. >> Can someone explain to me, where the connection between a match and a set >> of actions to take, is defined/established? >> >> Thanks in advance, for any information! >> >> -- >> >> Carlos Miguel Ferreira >> Researcher at Telecommunications Institute >> Aveiro - Portugal >> Work E-mail - c...@av.it.pt >> MSN Contact -> carlosmf...@gmail.com >> Skype & GTalk -> carlosmf...@gmail.com >> LinkedIn -> http://www.linkedin.com/in/carlosmferreira >> >> _______________________________________________ >> openflow-discuss mailing list >> openflow-discuss@lists.stanford.edu >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> >> > > > -- > Eder Leão Fernandes > > Bacharelado em Ciências de Computação > Instituto de Ciências Matemáticas e de Computação > Universidade de São Paulo > -- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - c...@av.it.pt MSN Contact -> carlosmf...@gmail.com Skype & GTalk -> carlosmf...@gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
