[DPDK/ethdev Bug 1266] net/mlx5: cannot create rte_flow rule matching ethernet multicast with jump action on bond mode 4
bugzilla at dpdk.org
bugzilla at dpdk.org
Mon Oct 27 15:07:17 CET 2025
http://bugs.dpdk.org/show_bug.cgi?id=1266
mkashani at nvidia.com (mkashani at nvidia.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
CC| |mkashani at nvidia.com
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from mkashani at nvidia.com (mkashani at nvidia.com) ---
Hi,
Sorry for the late response,
**Root Cause**: MLX5 hardware/firmware steering on root table (group 0) has
limited support for jump actions combined with partial MAC address masks. The
bonding PMD directly passes the flow to slave ports without adaptation.
## Immediate Workarounds
### Workaround 1: Use Group 1 (Recommended)
Instead of group 0, use group 1:
```bash
flow create 2 group 1 priority 0 ingress pattern eth dst spec 01:00:00:00:00:00
dst mask 01:00:00:00:00:00 / end actions jump group 2 / end
```
First, create a catch-all rule in group 0 to reach group 1:
```bash
flow create 2 group 0 priority 1 ingress pattern eth / end actions jump group 1
/ end
```
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the dev
mailing list