[Swan-dev] ikev2-14-missing-ke test failure
Paul Wouters
paul at nohats.ca
Sat Jan 3 18:55:32 EET 2015
On Mon, 29 Dec 2014, D. Hugh Redelmeier wrote:
> In my recent run, west's console output doesn't match the reference
> output. Here's an extract:
>
> 133 "westnet-eastnet-ipv4-psk-ikev2" #1: STATE_PARENT_I1: sent v2I1, expected v2R1
> +002 "westnet-eastnet-ipv4-psk-ikev2" #1: supressing retransmit because IMPAIR_RETRANSMITS is set.
> 002 "westnet-eastnet-ipv4-psk-ikev2" #1: STATE_PARENT_I1: received unauthenticated v2N_INVALID_SYNTAX - ignored
> -002 "westnet-eastnet-ipv4-psk-ikev2" #1: supressing retransmit because IMPAIR_RETRANSMITS is set
> -031 "westnet-eastnet-ipv4-psk-ikev2" #1: max number of retransmissions (0) reached STATE_PARENT_I1. No response (or no acceptable response) to our first IKEv2 me!
> -002 "westnet-eastnet-ipv4-psk-ikev2" #1: deleting state #1 (STATE_PARENT_I1)
> -west #
> +^C#\[root at west ]# timedout send line: ipsec auto --up westnet-eastnet-ipv4-psk-ikev2
> echo done
> -done
>
> and from here on there is a serious divergence.
>
> Is this expected? Is this a bug that I've introduced?
It's testing for a crasher. It has --noretransmits set so that the test
does not time out. Is that missing from your branch?
> A similar failure occurs in:
> ikev2-major-version-initiator
> ikev2-major-version-responder
> ikev2-allow-narrow-02
> basic-pluto-15-no-retransmit
Those I would also expect to have the ipsec whack --debug-all
--noretransmit line to avoid the python timeouts. If those are
hanging, than perhaps the whack did not get released properly,
but I thought that had been fixed last month or so?
Paul
More information about the Swan-dev
mailing list