Re: [ovs-discuss] Is a new field in flow.h necessary for matching on a custom v6 extension header?

Makes total sense. I started with PISCES and made some progress, however it feels like going into uncharted waters. I feared I might hit something above my pay grade, so I am back to modifying ovs instead. Best of luck on your P4 journey :) 2018-02-23 19:22 GMT+01:00 Ben Pfaff : >

Re: [ovs-discuss] Is a new field in flow.h necessary for matching on a custom v6 extension header?

Ultimately, I expect a P4-based solution, in which the controller supplies a P4 program that extracts the fields that it is interested in. This is my big project for OVS 2.10. (I don't know how successful I'll be yet.) On Fri, Feb 23, 2018 at 12:37:40AM +0100, Alan Kayahan wrote: > I understand

Re: [ovs-discuss] Is a new field in flow.h necessary for matching on a custom v6 extension header?

I understand that there must be a construct in the struct flow, and introducing a new be32 will save the day for me. However looking at this from a broader perspective, say matching on the fields of any v6 extension header made into the OF specification, neither adding individual fields nor adding

[ovs-discuss] Is a new field in flow.h necessary for matching on a custom v6 extension header?

Hello, I have a custom v6 extension header, in which I would like to perform an LPM match on only one 32bit field. Since an extension header is technically not a new field, do I still need to introduce anything in the struct flow? In miniflow_extract(), what I did was to add a case in