> ok, thanks, I will create some tests for the problematic cases and hopefully
> some fixes.
I'll push it once I've got a full test result.
Long term, should:
+#ifdef USE_XFRM_INTERFACE
+if (c->xfrmi != NULL && c->xfrmi->if_id != 0)
+if (!add_xfrm_interface(c, c->logger))
+
On Thu, 2 May 2024 at 05:02, Wolfgang Nothdurft via Swan-dev
wrote:
>
> Hi,
>
> I am currently trying to sort out a few cases where routes and rules are
> not handled correctly.
Some internals (i.e., in theory, I'm just including this for completeness)
Part of 5.0+'s overhaul was routing.[hc]
On Sat, 20 Apr 2024 at 19:40, Paul Wouters via Swan-dev
wrote:
>
> On Sat, 20 Apr 2024, Andrew Cagney via Swan-commit wrote:
>
> >libipsecconf: rename internal enum AUTOSTART_ONDEMAND -> AUTOSTART_ROUTE
>
> This is wrong. The libipsecconf names match the _keywords_ used by auto=
> and
On Wed, 20 Mar 2024 at 06:42, Armen Dilanyan wrote:
>
> The "discarding" and "dropping" log lines? These aren't really
> errors, or were you not seeing them before?
>
>
> Previously, when RemoteAccess_user1 connected, the event logs showed the ID
> of RemoteAccess_user1
>
> Feb 05 15:02:15
On Sat, 16 Mar 2024 at 05:03, Armen Dilanyan wrote:
>
> Hi all.
> Hi Andrew.
> Yes, you are right, I did not enable debugging. I use one IP address in the
> pool, since users must have a static IP address. Configurations are below in
> the letter.
The debug logs should be gone in mainline.
>
See https://github.com/libreswan/libreswan/issues/1653
On Fri, 15 Mar 2024 at 11:27, Andrew Cagney wrote:
>
> I assume you don't have debugging enabled (ya).
> It looks like liveness messages which aren't normally logged. Please
> file a bug and thanks for pointing this out.
>
> On Fri, 15 Mar
I assume you don't have debugging enabled (ya).
It looks like liveness messages which aren't normally logged. Please
file a bug and thanks for pointing this out.
On Fri, 15 Mar 2024 at 05:48, Armen Dilanyan via Swan-dev
wrote:
>
> Hi all.
> I have Debian 12.5 operating system installed.
> I
On Tue, 5 Mar 2024 at 10:23, Paul Wouters via Swan-dev
wrote:
>
> On Tue, 5 Mar 2024, Andrew Cagney via Swan-commit wrote:
>
> > Date: Mon Mar 4 20:15:11 2024 -0500
> >
> >ikev2: drop and NOT sending notify
> >
> >it's redundant and confusing vis:
> > "west-cuckold" #4: sent
On Tue, 27 Feb 2024 at 05:10, Brady Johnson wrote:
>
> We tried several changes to the client nmstate configuration. Setting "ipv4:
> dhcp: false" caused a configuration error in nmstate. We have created a bug
> for that and the nmstate team is working on it.
I didn't see it here
On Fri, 16 Feb 2024 at 10:18, Tuomo Soini via Swan-dev
wrote:
>
> On Fri, 16 Feb 2024 16:12:20 +0100
> Brady Johnson via Swan-dev wrote:
>
> > I included the configuration in the original email, and it did not
> > include "narrowing", nor "leftmodecfgclient". I'll check if either of
> > those
On Thu, 22 Feb 2024 at 13:43, Paul Wouters via Swan-dev
wrote:
>
> On Thu, 22 Feb 2024, Andrew Cagney via Swan-commit wrote:
>
> > New commits:
> > commit 8f2151aab6084561bdeb8c49206ee238b508eecc
> > Author: Andrew Cagney
> > Date: Thu Feb 22 10:58:13 2024 -0500
> >
> >ikev2: drop code
On Tue, 20 Feb 2024 at 21:16, Paul Wouters via Swan-dev
wrote:
>
>
> I see this commit:
>
> commit f198add4b08640d1b67aef19168998070b65b725
> Author: Andrew Cagney
> Date: Tue Feb 20 20:25:33 2024 -0500
>
> ikev2: when responding to labeled TS don't search for a connection
>
> only
> Feb 15 06:15:48 saledortvm2 pluto[70624]: "server01.cnf.com" #2: processing
> decrypted IKE_AUTH request: SK{IDi,CERT,AUTH,CP,SA,TSi,TSr}
notice how the client sent a CP payload in the request (CP_REQUEST to be exact).
but
> #2: missing v2CP reply, not attempting to setup child SA
> #1: IKE
13 matches
Mail list logo
