On Tue, May 19, 2015 at 01:57:57PM -0500, David Evans wrote: > I¹d like to implement a custom match on my custom ether_type, custom layer > 2.5 value (not VLAN/MPLS etc.) > I understand that I need to modify at least: > * match.c with match_set* functions and add to the flow¹ struct my foomatch > variable. > * Meta-flow.c with all the behaviors I need to MFF_FOOMATCH_TYPE required > for my functions in match.c > * OXM_CLASSES needs a vendor to match my controller in the > extract-ofp-fields py script for translation functions > * in ofp-util.c I need a handler for OFPTFPT13_EXPERIMENTER, but what to add > I have no idea other than it should look something like parse_oxms. > > How do I connect up to openflow messaging to implement flow mod with an > experimenter match ?
Just follow the example set by another commit that adds support for a new experimenter match. The most recent example is commit ac6073e3cda (ofproto: Add NXM_NX_TUN_GBP_ID and NXM_NX_TUN_GBP_FLAGS). _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
