Hello Paul, A colleague of mine went through the setup again and the last working version was 3.20, Attached are the log files and an example of the test.conf which we are currently using for the tests. As we did some other changes on our site as well, will I try to rule out any of that. One question I have is what is libreswan using to identify the IP's, when I do a normal IPsec status the interfaces have the correct IP's.
Kind Regards Rene Neumann <https://www.zpesystems.com/demo/> ________________________________ From: Paul Wouters <[email protected]> Sent: Tuesday 3 March 2020 03:48 To: Rene Neumann <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [Swan] Fw: Libreswan 3.27 left=%eth1 is not resolving local IP 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 0.0.0.0. > > 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. Paul
test.conf.log
Description: test.conf.log
ipsec_3_27_not_working.log
Description: ipsec_3_27_not_working.log
ipsec_3_20_working.log
Description: ipsec_3_20_working.log
status.log
Description: status.log
_______________________________________________ Swan mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan
