Files
strongswan-ext/testing/tests/ikev2/per-cpu-sas/pretest.dat
T
Tobias Brunner 1454bd7bcf testing: Make per-CPU SAs scenarios more predictable by pinning IRQs to vCPUs
This ensures that packets on sun are processed on a particular CPU and
not randomly on one, which causes expected SAs not to get created or
other weird things.
2025-12-03 11:42:54 +01:00

14 lines
603 B
Plaintext
Executable File

# make sure forwarded responses trigger IRQ on the right CPU
sun::set-cpu-affinity eth1 0
sun::iptables-restore < /etc/iptables.rules
moon::iptables-restore < /etc/iptables.rules
sun::systemctl start strongswan
moon::systemctl start strongswan
sun::expect-connection gw-gw
moon::expect-connection gw-gw
# triggering packet apparently goes via lo
moon::iptables -A OUTPUT -o lo -d 10.2.0.0/16 -j ACCEPT
# trigger the creation of the fallback SA, use -I so no UDP socket is used to
# determine the source address and trigger the acqurie (this packet is lost)
moon::ping -c 1 -W 1 -I PH_IP_MOON1 PH_IP_BOB