Files
strongswan-ext/testing/tests/ikev2/per-cpu-sas-encap/description.txt
T
Tobias Brunner 3b2f8cf282 testing: Add ikev2/per-cpu-sas-encap scenario
Basically the same as the one without UDP encapsulation, but here the
outbound SAs use random source ports.
2025-05-28 16:35:27 +02:00

14 lines
738 B
Plaintext
Executable File

The two gateways <b>moon</b> and <b>sun</b> are configured to use per-CPU
CHILD_SAs in order to improve performance. Using the <b>taskset</b> utility
pings are sent from different CPUs triggering the creation of additional SA
via the installed trap policy. The first ping triggers the creation of a
fallback SA that's used while per-CPU SAs are created for later packets. Note
that responses sent from the peer may create per-CPU SAs that are not triggered
by local acquires.
<p>
UDP encapsulation is forced and the special value <b>encap</b> is used when
enabling per-CPU SAs to force random source ports for the outbound SAs.
<p>
The updown script automatically inserts iptables-based firewall rules
that let pass the tunneled traffic.