[ovs-dev] How to implement openflow vendor extensions
Rafael Duarte Vencioneck
rafael.vencioneck at gmail.com
Wed Jan 22 11:10:22 UTC 2014
Thank you Ben, this might help.
Rafael Duarte Vencioneck
2014/1/21 Ben Pfaff <blp at nicira.com>
> On Sun, Jan 19, 2014 at 03:39:24PM -0200, Rafael Duarte Vencioneck wrote:
> > I'm interested in implement a new openflow 1.0 vendor extension message.
> > Can somebody kindly help me telling what do I have to modify on
> openvswitch?
> > I'm using the 1.9.3 version.
> > I would like to document this process too, since the current
> documentation is
> > scarce.
>
> Q: How do I implement a new OpenFlow message?
>
> A: Add your new message to "enum ofpraw" and "enum ofptype" in
> lib/ofp-msgs.h, following the existing pattern, then recompile and
> fix all of the new warnings. (If you configure with
> --enable-Werror, as described in INSTALL, then it is impossible to
> miss any warnings.)
>
> If you need to add an OpenFlow vendor extension message for a
> vendor that doesn't yet have any extension messages, then you will
> also need to edit build-aux/extract-ofp-msgs.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20140122/dc36d6c9/attachment-0003.html>
More information about the dev
mailing list