If the fields you are adding are for a tunnel, and flow extraction will
look beyond the tunnel header into the encapsulated packet, then I
recommend adding your fields to struct flow_tnl--it will make the
remaining changes easier. Otherwise, they probably should not be in
flow_tnl.
On Wed, Nov 05
Hi Ben,
Thanks. Looking at struct flow I see the structure flow_tnl. Should
matching fields of the GTP header be declared in here or directly as
members of the flow struct?
Cheers
Daniel
On Tue, Nov 4, 2014 at 6:50 PM, Ben Pfaff wrote:
> On Tue, Nov 04, 2014 at 07:42:36PM +0100, Dani Camps wro
On Tue, Nov 04, 2014 at 07:42:36PM +0100, Dani Camps wrote:
> I would appreciate if anyone can give me a high level orientation on
> the best design approach to accomplish the above. For example should I
> define the new header parameters in the ofp11_match structure and try
> to replicate the code
Dear all,
I am interested in extending Openvswitch to be able to match on GTP-U
fields, typically used in mobile telecom networks. At a high level
what I would like to do is:
1) Have an openflow controller install rules in OVS where the match
portion of the rules includes fields of the GTP-U head
