[ovs-discuss] TCP and UDP mask support in OVS
Aswin S
aswinsuryan at gmail.com
Tue Jul 26 12:00:15 UTC 2016
HI Ben,
I have attached the pcap. ( Sl No 3052 and 3053 is one such message).
Thanks
Aswin
On Mon, Jul 25, 2016 at 8:20 PM, Ben Pfaff <blp at ovn.org> wrote:
> Hmm, there's no change in this area since 2.4. Can you give an example
> of an OpenFlow message that provokes the error? A hexdump or pcap of
> the message would be ideal.
>
> On Mon, Jul 25, 2016 at 12:19:43PM +0530, Aswin S wrote:
> > Hi Ben
> >
> > The below extension were used.
> >
> > #define NXM_OF_TCP_SRC NXM_HEADER (0x0000, 9, 2)
> > #define NXM_OF_TCP_DST NXM_HEADER (0x0000, 10, 2)
> > #define NXM_OF_UDP_SRC NXM_HEADER (0x0000, 11, 2)
> > #define NXM_OF_UDP_DST NXM_HEADER (0x0000, 12, 2)
> >
> > It was working in OVS 2.4(not the latest). But now it seems to be
> throwing
> > an error BAD_LENGTH with latest 2.4 and 2.5
> >
> > Thanks
> > Aswin
> >
> > On Sun, Jul 24, 2016 at 11:30 PM, Ben Pfaff <blp at ovn.org> wrote:
> >
> > > On Sun, Jul 24, 2016 at 11:28:27AM +0530, Aswin S wrote:
> > > > In opendaylight we used Nicira Extention to support TCP and UDP
> mask. But
> > > > now I observe that in ovs it is a part of standard openflow
> > > implementation
> > > > and the nicira extension code we used is reporting error. Was there a
> > > > change in ovs? But openflow plugin spec is yet to support TCP/UDP
> mask.
> > >
> > > I don't know of a backward-incompatible change to OVS in this area.
> > > What Nicira extension were you using? What version of OVS worked, and
> > > what version of OVS does not?
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160726/1b17b1be/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tcp_mask.pcap
Type: application/vnd.tcpdump.pcap
Size: 2333249 bytes
Desc: not available
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160726/1b17b1be/attachment.bin>
More information about the discuss
mailing list