You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IPSec tunnels can't connect to remote host after restart of ipsec service.
Steps to reproduce
Make sure to have installed nethserver-ipsec-tunnels from NS 7.4 along with libreswan 3.20
Configure a tunnel and check the connection is working
Update to libreswan 3.23
Expected behaviour
Tunnels are up & running after the update.
Actual behaviour
Tunnels are inactive and journalct -u ipsec reports following error:
May 18 11:06:25 auenland pluto[1164]: "xyz_ipsec-tunnel/1x6": We cannot identify ourselves with either end of this connection. 6.7.8.9 or 0.0.0.0 are not usable
Workaround
db vpn setprop xyz_ipsec Custom_left <red_ip>
signal-event nethserver-ipsec-tunnels-save
IPSec tunnels can't connect to remote host after restart of
ipsec
service.Steps to reproduce
nethserver-ipsec-tunnels
from NS 7.4 along withlibreswan
3.20Expected behaviour
Tunnels are up & running after the update.
Actual behaviour
Tunnels are inactive and
journalct -u ipsec
reports following error:Workaround
Components
nethserver-ipsec-tunnels-1.1.1-1.ns7.noarch
libreswan-3.20
See also
https://community.nethserver.org/t/update-to-7-5-problem-s/9810/46
Thanks to DrDth
The text was updated successfully, but these errors were encountered: