aboutsummaryrefslogtreecommitdiffstats
path: root/tests/vpp/perf/crypto/10ge2p1x710-ethip4ipsec1tnlsw-ip4base-int-aes256gcm-reassembly-ndrpdr.robot
AgeCommit message (Collapse)AuthorFilesLines
2024-04-17style(ipsec): Do not import ipsec.robot to suitesVratko Polak1-2/+1
It is already available via default.robot import. Change-Id: I52c8f5d62f641edfbbc4b750e40274a75b169a22 Signed-off-by: Vratko Polak <vrpolak@cisco.com>
2023-10-26feat(trex): cleanup t-rex profilespmikus1-1/+1
Signed-off-by: pmikus <peter.mikus@protonmail.ch> Change-Id: Ib93dc1552945fe91ab5346b9b759d56c7468debf
2023-05-24feat(reassembly): add few suites for ip reassemblyVratko Polak1-0/+171
In tunneling scenarios, VPP needs to reassembly packet fragments before decapsulation. Conveniently, VPP also fragments the packets after encapsulation (at least for some encapsulation protocols) if they do not fit into MTU. So this change adds few suites, adapted from existing 3-node ones which additionally lower MTU on DUT1-DUT2 link. The intended packet size is 1518B. 64B packets will fit, and most of IMIX packets will also fit without fragmentation. VPP refuses to reassembly 9000B packets as they have too many fragments. + Add a keyword so suites need only one additional line of code. + Add new test tag REASSEMBLY for the added suites. + Tell autogen the one soak test case for reaseembly should be 1518B. - It is possible to increase fragment limit for 9000B, not done yet. - Ipsec policy suites are added but they should not be used. - VPP does fragmentation twice (before and after encapsulation). - VPP does not perform reassembly (only last fragment is decrypted). - TRex does not realize the packet from VPP is only a fragment. - The result is false pass with unfairly good performance. + Suites still included, to simplify verifying VPP fixes for the above. Change-Id: If33c60d767fea161d9e4ffabb8ded3d81c8f39ed Signed-off-by: Vratko Polak <vrpolak@cisco.com>