These have been supported all along, but the documentation neglected to mention the fact.
Signed-off-by: Joe Stringer <j...@ovn.org> --- utilities/ovs-ofctl.8.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/utilities/ovs-ofctl.8.in b/utilities/ovs-ofctl.8.in index 6e2613207979..8188b5352349 100644 --- a/utilities/ovs-ofctl.8.in +++ b/utilities/ovs-ofctl.8.in @@ -1725,12 +1725,12 @@ fields are accepted within the \fBexec\fR action, and these fields may only be modified with this option. For example: . .RS -.IP \fBset_field:\fIvalue\fR->ct_mark\fR +.IP \fBset_field:\fIvalue\fR[\fB/\fImask\fR]->ct_mark\fR Store a 32-bit metadata value with the connection. If the connection is committed, then subsequent lookups for packets in this connection will populate the \fBct_mark\fR flow field when the packet is sent to the connection tracker with the \fBtable\fR specified. -.IP \fBset_field:\fIvalue\fR->ct_label\fR +.IP \fBset_field:\fIvalue\fR[\fB/\fImask\fR]->ct_label\fR Store a 128-bit metadata value with the connection. If the connection is committed, then subsequent lookups for packets in this connection will populate the \fBct_label\fR flow field when the packet is sent to the -- 2.1.4 _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
