From: "fankaixi.li" <fankaixi...@bytedance.com>
In order to support openflow rule which setting nd_ext fields in openflow
tables,
we should remove setting nd_ext fields when constructing rule. The ofproto would
translate it into userspace actions when handling upcalls.
Signed-off-by: fankaixi.li <fankaixi...@bytedance.com>
---
ofproto/ofproto-dpif.c | 8 --------
1 file changed, 8 deletions(-)
diff --git a/ofproto/ofproto-dpif.c b/ofproto/ofproto-dpif.c
index 4f0638f23..f4c37f43d 100644
--- a/ofproto/ofproto-dpif.c
+++ b/ofproto/ofproto-dpif.c
@@ -4637,14 +4637,6 @@ check_actions(const struct ofproto_dpif *ofproto,
"ct original direction tuple");
return OFPERR_NXBAC_CT_DATAPATH_SUPPORT;
}
- } else if (!support->nd_ext && ofpact->type == OFPACT_SET_FIELD) {
- const struct mf_field *dst = ofpact_get_mf_dst(ofpact);
-
- if (dst->id == MFF_ND_RESERVED || dst->id == MFF_ND_OPTIONS_TYPE) {
- report_unsupported_act("set field",
- "setting IPv6 ND Extensions fields");
- return OFPERR_OFPBAC_BAD_SET_ARGUMENT;
- }
}
}
--
2.24.3 (Apple Git-128)
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
