This is the match structure embedded in the pcap. It is 48 bytes long.
I've added spaces and line numbers to allow for commentary:
1. 0001 002b
2. 8806 fa163ed9fbfd
3. 8a02 0800
4. 80001401 06
5. 80001908 ff00
6. 1504 014d
7. 00
Line 1
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_SR
Hi Ben
The below extension were used.
#define NXM_OF_TCP_SRCNXM_HEADER (0x, 9, 2)
#define NXM_OF_TCP_DSTNXM_HEADER (0x, 10, 2)
#define NXM_OF_UDP_SRCNXM_HEADER (0x, 11, 2)
#define NXM_OF_UDP_DSTNXM_HEADER (0x, 12, 2)
It was working in OVS 2.4(not the latest).
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?
Hi,
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.
Th