[Swan-dev] unstable connection serial numbers

[Andrew Cagney]

The stray 'whack --listen' is coming from  wait-until-pluto-started,
for instance:

| whack: delete 'clear'
| whack: connection 'clear'
| whack: delete 'clear-or-private'
| whack: connection 'clear-or-private'
| from whack: got --esp=
| whack: delete 'private-or-clear'
| whack: connection 'private-or-clear'
| from whack: got --esp=
| whack: listen <------------- this is from wait-until-pluto-started
| whack: delete 'private'
| whack: connection 'private'
| from whack: got --esp=
| whack: delete 'block'
| whack: connection 'block'
| whack: listen <------ this is from addconn
| whack: route

which means, in addition to screwing around with addconn, it isn't
waiting for addconn to finish.

Thoughts on making this more robust?

On Tue, 29 Sep 2020 at 21:45, Andrew Cagney <andrew.cagney at gmail.com> wrote:
>
> I'm trying to understand this diff
> https://testing.libreswan.org/v3.30-1853-gc4b35c42cb-main/newoe-25-cat-2/OUTPUT/road.console.diff
>
> -000 "block":   newest ISAKMP SA: #0; newest IPsec SA: #0; conn serial: $9;
> +000 "block":   newest ISAKMP SA: #0; newest IPsec SA: #0; conn serial: $5;
>
> Pluto is receiving something like the following from whack:
>
> - add $1 clear
> - add $2 clear-or-private
> - add $3 private-or-clear
> - add $4 private
>
> but then it receives either:
>
> - add $5 block
> - listen -> triggers groups $6-$9
>
> or:
>
> - listen-> triggers groups $5-$8
> - add $9 block
>
> I'm guessing there are two whacks or something?