On Tue, Oct 07, 2014 at 04:37:31PM -0700, Alex Wang wrote:
> On Tue, Oct 7, 2014 at 1:30 PM, Ben Pfaff wrote:
>
> > I'm not sure what you mean for OXM/NXM here and what you propose for
> > it. Can you explain further?
>
> I'm thinking if we can create a generic OXM/NXM field for matching L4 lev
On Tue, Oct 7, 2014 at 1:30 PM, Ben Pfaff wrote:
> [adding the list back]
>
> I think that that is somewhat separate from the documentation. I
> think that the documentation should probably focus on the
> protocol-specific field names these days, and document tp_src and
> tp_dst as obsolete. I
[adding the list back]
I think that that is somewhat separate from the documentation. I
think that the documentation should probably focus on the
protocol-specific field names these days, and document tp_src and
tp_dst as obsolete. I sent out a patch:
http://openvswitch.org/pipermail/dev
Okay, let me check on the parsing of learn action,
On Thu, Oct 2, 2014 at 8:38 AM, Ben Pfaff wrote:
> On Wed, Oct 01, 2014 at 08:58:07PM -0700, Alex Wang wrote:
> > OVS implements specific keywords like udp_src/udp_dst
> > to match on L4 header port in OpenFlow flows. However,
> > these keyword
On Wed, Oct 01, 2014 at 08:58:07PM -0700, Alex Wang wrote:
> OVS implements specific keywords like udp_src/udp_dst
> to match on L4 header port in OpenFlow flows. However,
> these keywords are not documented in the ovs-ofctl
> manpage. This commit fixes it.
>
> VMware-BZ: #1333815
>
> Signed-of
OVS implements specific keywords like udp_src/udp_dst
to match on L4 header port in OpenFlow flows. However,
these keywords are not documented in the ovs-ofctl
manpage. This commit fixes it.
VMware-BZ: #1333815
Signed-off-by: Alex Wang
---
utilities/ovs-ofctl.8.in | 14 ++
1 fil
