On Fri, Jan 05, 2018 at 10:58:45AM -0800, Guru Shetty wrote: > On 4 January 2018 at 22:40, Ben Pfaff <b...@ovn.org> wrote: > > > In debugging issues with a controller that appears to send invalid > > OpenFlow messages, it can be difficult to actually see the important > > details of those messages, because OpenFlow message logging (in the vconn > > log module) will generally just print a generic decode error that doesn't > > allow a developer to see what failed to decode. This commit enhances the > > ofp-print code so that, if a message fails to decode, the full hex dump of > > the message is included in the output. > > > > Reported-by: Su Wang <suw...@vmware.com> > > Signed-off-by: Ben Pfaff <b...@ovn.org> > > > Acked-by: Gurucharan Shetty <g...@ovn.org>
Thanks, applied to master. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
