way to support matching on a field which doesn't have a corresponding
> ODP attribute.
>
>
>
> On 27/04/2016 06:18, "Ben Pfaff" wrote:
>
> >I'm not aware of bugs here, but there could easily be something new,
> >since this code path isn't exer
ed in the
flow translation. Daniele promised to take a stab at it."
On Sun, Apr 24, 2016 at 4:07 PM, Enas Ahmad wrote:
> According to Open vSwitch datapath developer documentation:
> https://www.kernel.org/doc/Documentation/networking/openvswitch.txt
>
> "If the
present" attribute, which makes perfect sense. However, this was not
taken any further and the flow entry is still cached at the kernel.
Is there any additional logic I need to add ?
On Tue, Mar 22, 2016 at 6:39 PM, Ben Pfaff wrote:
> Thanks, I've sent out a patch for the FAQ.
>
Hi,
I want to use HTB with mulit-levels, and the HTB configured by the
ovs-vsctl is single level only.
However, If I configure a HTB using tc, the queues won't be registered in
the OVS database (qos and queue tables stay empty), So my question is can I
still use them in the set_queue command ? an
e changes to OVS and they didn't work." The answer is that you need
> to debug your changes.
>
> On Thu, Mar 17, 2016 at 06:17:10PM +0300, Enas Ahmad wrote:
> > Hi,
> > I am still having a problem in successfully defining a new field. My
> field
> > name
packet arrives.
I made sure that the switch is running the OpenFlow15 version using the -O
command.
Is there something I am missing ?
On Sun, Mar 13, 2016 at 7:16 PM, Ben Pfaff wrote:
> On Sun, Mar 13, 2016 at 05:32:45PM +0300, Enas Ahmad wrote:
> > Thanks Ben for the useful
this method ?
flow.c does not import openvswitch/vlog.h, is there a reason for that ?
should I just add support for logging in flow.c or is there another way to
debug it ?
Thanks again,
Enas
On Wed, Jan 6, 2016 at 10:20 PM, Ben Pfaff wrote:
> On Wed, Jan 06, 2016 at 01:26:58PM +0300, Enas Ah
Hi,
I am designing a new protocol for IoT applications, and I would like to
know if I can extend Open Flow match fields to add a new header field
designed by my new protocol ?
Also, can I define a new field for the set-field action ?
Thank you very much,
Enas
--
--