[Swan] Fw: Libreswan 3.27 left=%eth1 is not resolving local IP

Paul Wouters paul at nohats.ca
Tue Mar 3 03:48:57 UTC 2020

On Mon, 2 Mar 2020, Rene Neumann wrote:

> I recently upgraded to version 3.27 from 3.23. I have multiple connections on my system and my default gateway is on eth0 but I want my tunnel to come upon eth1 as this
> is my 2nd WAN connection via an LTE modem. This worked fine in the past by setting the value left=%eth1 but since the upgrade, this is not working anymore I always get
> the error that the connection could not identify with itself and set's the local value to
> Is this a known issue or did I miss a change in the configuration?

This is not a known issue.

Is it possible to send me the logs of a successfull and failing version
to get an idea of what's going wrong?

Please also file a bug on bugs.libreswan.org or
github.com/libreswan/libreswan so we won't forget this issue.


More information about the Swan mailing list