Project

General

Profile

Actions

Bug #12198

closed

Disabling an IPsec phase 1 entry does not disable related phase 2 entries

Added by Viktor Gurov about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
IPsec
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
22.01
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:

Description

How to reproduce:
1) Create IPsec PH1 with several PH2 VTI entries
2) Toggle "disable" button on the vpn_ipsec.php page
3) <phase1> has a <disable> entry in config.xml, but not <phase2>
4) If you try to make any changes to this PH1 disabled entry on the vpn_ipsec_phase1.php page, you'll get an error:

Cannot disable a Phase 1 which contains an active VTI Phase 2 with an interface assigned. Remove the interface assignment before deleting this P1.


Related issues

Related to Bug #11792: Cannot disable IPsec P1 when related P2s are in VTI mode and enabled ClosedViktor Gurov04/08/2021

Actions
Actions

Also available in: Atom PDF