Project

General

Profile

Actions
Copy link

Bug #5934

closed

When two distinct Phase 1 are configured, only the first one connects ar startup

Added by Luiz Fernando Cavalcanti about 8 years ago. Updated almost 8 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
02/26/2016
Due date:
% Done:

0%

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

Description

As the attached files will illustrate if you have two distinct phase 1 entries with equally distinct and respective Phase 2 entries, only the first Phase 1(and it's phase 2) are initialized and connected when the system starts up.

If I go to STATUS > IPSEC and click in the "Connect" button for the respective Phase 1 it connects fine, no problem, no warning. I also tested if generating any traffic towards the remote subnet triggers the Phase 1 to connect, no success.

I confirmed the problem in both 2.2.5 and 2.2.6, I haven't simulated this scenario in the 2.3 snapshots yet.

Files

Download all files
ipsec.xml (3.16 KB) ipsec.xml Example XML config Luiz Fernando Cavalcanti, 02/26/2016 12:12 PM
example_diagram.png (18 KB) example_diagram.png Example Diagram Luiz Fernando Cavalcanti, 02/26/2016 12:12 PM
Actions
Copy link

Also available in: Atom PDF