Hi Maurizio, Il 27/07/2016 21:36, Maurizio Marrocco ha scritto: > Hi, RYU team. > > I'm Sorry for those questions, but I have a doubt about Match procedure in > Openflow. > > In the flow table, the matching is done on OpenFlow PDU (i.e. PACKET OUT) or > PDU transported by Openflow? > > For example in this statement "match = parser.OFPMatch(in_port=in_port, > eth_dst=dst)" the eth_dst field is matched on PDU (Data) transported by > Openflow for example ICMP req, ARP req ? or it is matched on PacketIn/Out?
If your controller sends a PacketOut to a switch, then it will forward the packet carried in the PacketOut accordingly with the action specified in the PacketOut itself. In other words, every packet carried by a PacketOut will never match any flow entries unless you specify a "OFFP_TABLE" in the PacketOut. This is what the specification says: The action field is an action list defining how the packet should be processed by the switch. It may include packet modification, group processing and an output port. The action list of an OFPT_PACKET_OUT message can also specify the OFPP_TABLE reserved port as an output action to process the packet through the existing flow entries, starting at the first flow table. If OFPP_TABLE is specified, the in_port field is used as the ingress port in the flow table lookup. In general, the match is performed against the header of the carried packet (in the case of PacketOut message), not against the OpenFlow one. > Another question: suppose that I have the following topology, h1--s1--s2--h2, > > -I ping host h2 from h1 > > to see LLDP packet with packetIn message from s2, Must I set MULTICAST eth > address: 01:80:c2:00:00:0e? I'm not sure to have completely understood what you mean... Gabriele > Thank you > > Maurizio. > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Ryu-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ryu-devel > ------------------------------------------------------------------------------ _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
