I am currently working on a project using DOCA Flow to define multiple pipes with different match rules on an NVIDIA BlueField DPU.
According to the documentation, struct doca_flow_match supports standard Ethernet, VLAN, IP, and L4 header fields, but does not expose any extended or custom IP fields.
I would like to match packets that contain an additional IP extension field (a CRC checksum) added after the IP header.
My question is:
Does DOCA Flow or the hardware parser support matching on such custom or extended IP fields?
If not directly supported, is there any workaround (e.g., using metadata, parser_meta API, or software pre-processing) to achieve similar behavior?