[Swan-dev] ikev2-child-rekey-09-windows test confusion

Paul Wouters paul at nohats.ca
Tue May 5 00:26:25 UTC 2020


In ikev2-child-rekey-09-windows I see:

road #
  ../../pluto/bin/ping-once.sh --up -I 192.0.2.100 192.1.2.23
up
road #
  # only #3 and not #2 in trafficstatus output
road #
  ipsec whack --trafficstatus
006 #2: "road-east-x509-ipv4"[1] 192.1.2.23, type=ESP, add_time=1234567890, inBytes=84, outBytes=168, id='C=CA, ST=Ontario, L=Toronto, O=Libreswan, OU=Test Department, CN=ea
st.testing.libreswan.org, E=user-east at testing.libreswan.org', lease=192.0.2.100/32
road #



The comment expects #3 (the rekeyed state) but shows #2. This used to be
#3 but commit 743cb8de511a1c188f2b0bbd0113539a41006f3e changed that?

I think this is because the test was pushed but the windows rekey fix
itself was not yet pushed. However, the next part of the test:

  # output should be empty
road #
  grep "Notify Message Type: v2N_TS_UNACCEPTABLE" /tmp/pluto.log
road #

Then why is this not getting hit ?

I noticed this when cherry-picking the test to a branch that does
have te patch already.

Paul


More information about the Swan-dev mailing list