Bug #3781
closedstrongswan dpdtimeout value not generated correctly
100%
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.
Updated by Matthew Smith over 10 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.
Updated by Matthew Smith over 10 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 9280a998704d182bc3a559163126e290edafbb26.
Updated by Chris Buechler about 10 years ago
- Status changed from Feedback to Resolved