automatically? Do I need to
use csum_tcpudp_magic? Or roll out my own function (which I’d like to avoid).
Thanks in advance.
Yann Bourdeau, M.Ing.
Senior Software Developer
438-499-4607
yann.bourd...@noviflow.com
___
dev mailing list
d...@openvswitch.org
https
> Le 11 oct. 2017 à 14:00, Ben Pfaff a écrit :
>>
>> I was successful to add the flow with my new type.
>>
>> However, I needed to comment some code in the following function because my
>> OXM is not mapped.
>
> Oh, I forgot that the variable-length fields we have already
Hi Ben,
> Le 11 oct. 2017 à 13:09, Ben Pfaff <b...@ovn.org> a écrit :
>
> On Wed, Oct 11, 2017 at 12:35:05PM -0400, yann bourdeau wrote:
>> Hi Ben,
>>
>> I was able to add successfully an experimenter flow to OVS(It is
>> missing the matchi
ement the
> fields.
>
> On Wed, Oct 04, 2017 at 05:54:52PM -0400, yann bourdeau wrote:
>> Hi Ben,
>>
>> I have looked at the python code to do it in build-aux. However what I
>> want to add is an OXM that match on UDP payload not on an existing field.
>>
x/extract-ofp-actions.
>
> On Wed, Oct 04, 2017 at 12:45:46PM -0400, yann bourdeau wrote:
>> Hi Ben,
>>
>> Thanks for the commit revision. It will help. However, do you have the
>> same for match field and action? Otherwise I will just dig in and try to
>>
2:13:03PM -0400, yann bourdeau wrote:
>> Hi all,
>>
>> I was wondering if there was a good tutorial on how to add
>> experimenters message, match fields and actions to OVS. I have found a
>> little bit of info at the end of the page there
#development
<https://github.com/openvswitch/ovs/blob/7169d4fdc8e564331c7a5ad910bc1d99cb413712/FAQ.rst#development>.
It is quite brief.
I have used OVS in the past but never developed for it.
Thanks in advance.
Yann Bourdeau, M.Ing.
Senior Software Developer
438-499-4607
yann