Project

General

Profile

Actions

Bug #8629

closed

Routed IPsec P1 - not coming up after pressing "disconnect" button

Added by Vladimir Lind over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
Start date:
07/10/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
Affected Architecture:

Description

A simple routed IPsec setup with one single /32 route across VTI interface. It works - P1 is UP, P2 routes listed, connectivity between remote hosts confirmed with icmp test.
But when forcing P1 disconnect with "disconnect" button under Status -> IPsec, P1 never comes back up until I reload IPsec daemon on one of the endpoints. When I try to force tunnel to come up by pressing "connect" button or initiating interesting for ipsec traffic I see this in log on either site:

Jul 10 06:18:00 charon 12[CFG] no IKE_SA named 'con1' found
Jul 10 06:18:01 charon 07[CFG] vici client 31 connected
Jul 10 06:18:01 charon 13[CFG] vici client 31 registered for: list-sa
Jul 10 06:18:01 charon 13[CFG] vici client 31 requests: list-sas
Jul 10 06:18:01 charon 10[CFG] vici client 31 disconnected
Jul 10 06:18:01 charon 07[CFG] received stroke: initiate 'con1'
Jul 10 06:18:01 charon 07[CFG] no config named 'con1'

2.4.4 factory - Mon Jul 09 16:05:36 EDT 2018 - both machines.

Actions

Also available in: Atom PDF