Hi all, we will submit pull requests of our 1.2 and 1.3 developments (https://github.com/CPqD/ofdissector). At some point in time we had some conversations on the best way forward but it got somehow lost, unfortunately. Sorry for that, the less the code base fractions the better.
We will update also the ToDo description on the missing decoding features. Off the top of my head 1.2 misses to dissect the body of the stats replies and in 1.3 there are some new protocol messages missing. Furthermore, we are in the final testing rounds of the 1.3 software switch (https://github.com/CPqD/ofsoftswitch13) which will be officially released in a matther of days. Next will be the NOXv1.3, and finally put together a v1.3 tool-kit (also available in a pre-configured VM) similar to the one released for v1.2 (https://github.com/CPqD/OpenFlow-1.2-Tutorial/wiki) Cheers, Christian On Thu, Nov 8, 2012 at 3:17 AM, Nicholas Bastin <[email protected]> wrote: > On Wed, Nov 7, 2012 at 9:38 PM, Bhandiwad, Mahesh <[email protected]> > wrote: >> I’m trying to integrate openflow dissector OF1.0(C implementation - >> https://bitbucket.org/barnstorm/of-dissector) and OF1.2(C++ implementation - >> https://bitbucket.org/barnstorm/ng-of-dissector). I just wanted to know is >> there anyone who has already worked on integrating both? > > I have done some very little work on integrating 1.0 support into the > ng-dissector - mostly this involves at least being able to tell 1.0 > frames from 1.1 and 1.2 frames (the ng-of-dissector actually is a 1.1 > dissector). There is a 1.2 port of this dissector as well from CPqD, > but they haven't submitted any patches back upstream. > > I would definitely encourage patches to add 1.0 support to the > ng-dissector, particularly if they resolved problems with the > reference 1.0 dissector (not pushing packet-in frame data into the > packet list view, choosing smarter values for search field options, > etc.). A pure integration of the existing 1.0 and 1.1 dissectors > wouldn't offer much in and of itself. > > -- > Nick > _______________________________________________ > openflow-discuss mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss -- Christian _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
