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 <al...@nicira.com> --- utilities/ovs-ofctl.8.in | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/utilities/ovs-ofctl.8.in b/utilities/ovs-ofctl.8.in index 3f55a72..847b969 100644 --- a/utilities/ovs-ofctl.8.in +++ b/utilities/ovs-ofctl.8.in @@ -698,6 +698,13 @@ from a HTTP server). .IP When \fBdl_type\fR and \fBnw_proto\fR take other values, the values of these settings are ignored (see \fBFlow Syntax\fR above). +.IP +Note, \fBtcp_src\fR, \fBtcp_dst\fR, \fBudp_src\fR, \fBudp_dst\fR, +\fBsctp_src\fR, and \fBsctp_dst\fR are also valid keywords. By default, +\fBtp_src\fR and \fBtp_dst\fR are equivalent to \fBtcp_src\fR, +\fBtcp_dst\fR respectively. For \fBlearn\fR action where keywords like +\fBtcp\fR and \fBudp\fR are not allowed, please use these specific keywords +to avoid syntax parsing error. . .IP \fBtp_src=\fIport\fB/\fImask\fR .IQ \fBtp_dst=\fIport\fB/\fImask\fR @@ -760,6 +767,13 @@ ports. Like the exact-match forms of \fBtp_src\fR and \fBtp_dst\fR described above, the bitwise match forms apply only when \fBdl_type\fR and \fBnw_proto\fR specify TCP or UDP or SCTP. +.IP +Note, \fBtcp_src\fR, \fBtcp_dst\fR, \fBudp_src\fR, \fBudp_dst\fR, +\fBsctp_src\fR, and \fBsctp_dst\fR are also valid keywords. By default, +\fBtp_src\fR and \fBtp_dst\fR are equivalent to \fBtcp_src\fR, +\fBtcp_dst\fR respectively. For \fBlearn\fR action where keywords like +\fBtcp\fR and \fBudp\fR are not allowed, please use these specific keywords +to avoid syntax parsing error. . .IP \fBtcp_flags=\fIflags\fB/\fImask\fR .IQ \fBtcp_flags=\fR[\fB+\fIflag\fR...][\fB-\fIflag\fR...] -- 1.7.9.5 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
