Project

General

Profile

Actions

Bug #3781

closed

strongswan dpdtimeout value not generated correctly

Added by Matthew Smith over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
IPsec
Target version:
Start date:
07/28/2014
Due date:
% Done:

100%

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

Description

When you enter a value in the retries field of the "Dead Peer Detection" row in the edit form on vpn_ipsec_phase1.php and save it, whatever value you enter gets put into /var/etc/ipsec/ipsec.conf as the value of dpdtimeout under the appropriate connection.

Racoon had a configuration parameter that was the maximum number of failures that mapped to the retries field, but strongswan has a total timeout value instead. The value that should be populated in the config file should be: (number of retries + 1) * dpd delay. Or the field in the GUI should be changed to reflect that it's a total timeout value instead of a number of retries.

Actions #1

Updated by Matthew Smith over 9 years ago

I'm going to go with the first approach of converting the value in the config.xml/GUI to (number of retries + 1) * DPD delay. Changing the GUI to assign a different meaning to that field would require the value in config.xml to be rewritten when upgrading from 2.1.x to 2.2.

Actions #2

Updated by Matthew Smith over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #3

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF