On Mon, May 04, 2020 at 09:09:25PM -0400, Paul Wouters wrote:
> On Mon, 4 May 2020, Andrew Cagney wrote:
>
> > I found this and other tests weren't working as expected:
>
> Yes, because the patch was not in and the test case assuming a patch was
> :)
>
> > # output should be empty
> >
On Mon, 4 May 2020, Andrew Cagney wrote:
If this test should work then the --async can be removed.
It's there because whack, which at the time was attached to both the old and
new child, was left hanging.
Once someone makes the decision which of the two patches to put in git
master, yes this
If this test should work then the --async can be removed.
It's there because whack, which at the time was attached to both the old
and new child, was left hanging.
On Mon, 4 May 2020 at 21:09, Paul Wouters wrote:
> On Mon, 4 May 2020, Andrew Cagney wrote:
>
> > I found this and other tests weren
On Mon, 4 May 2020, Andrew Cagney wrote:
I found this and other tests weren't working as expected:
Yes, because the patch was not in and the test case assuming a patch was
:)
# output should be empty
road #
grep "Notify Message Type: v2N_TS_UNACCEPTABLE" /tmp/pluto.log
I found this and other tests weren't working as expected:
On Mon, 4 May 2020 at 20:26, Paul Wouters 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 #
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, outByte
