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

[Andrew Cagney]

I found this and other tests weren't working as expected:

On Mon, 4 May 2020 at 20:26, Paul Wouters <paul at nohats.ca> wrote:

>
> 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 ?
>


"road-east-x509-ipv4"[1] 192.1.2.23 #3: dropping unexpected
ISAKMP_v2_CREATE_CHILD_SA message containing v2N_TS_UNACCEPTABLE
notification; message payloads: SK; encrypted payloads: N; missing
payloads: SA,Ni,TSi,TSr


> I noticed this when cherry-picking the test to a branch that does
> have te patch already.
>
> Paul
> _______________________________________________
> Swan-dev mailing list
> Swan-dev at lists.libreswan.org
> https://lists.libreswan.org/mailman/listinfo/swan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.libreswan.org/pipermail/swan-dev/attachments/20200504/d8410c04/attachment.html>