diff options
| author | Leon Romanovsky <leonro@nvidia.com> | 2023-09-20 10:07:13 +0300 |
|---|---|---|
| committer | Saeed Mahameed <saeedm@nvidia.com> | 2023-12-04 22:11:51 -0800 |
| commit | 3d42c8cc67a8fcbff0181f9ed6d03d353edcee07 (patch) | |
| tree | 1e3779b7fbb3a891c90fc7599ebd6f3ca9e71470 /tools/perf/scripts/python | |
| parent | a5e400a985df8041ed4659ed1462aa9134318130 (diff) | |
net/mlx5e: Ensure that IPsec sequence packet number starts from 1
According to RFC4303, section "3.3.3. Sequence Number Generation",
the first packet sent using a given SA will contain a sequence
number of 1.
However if user didn't set seq/oseq, the HW used zero as first sequence
packet number. Such misconfiguration causes to drop of first packet
if replay window protection was enabled in SA.
To fix it, set sequence number to be at least 1.
Fixes: 7db21ef4566e ("net/mlx5e: Set IPsec replay sequence numbers")
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions