Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 403661 - Can't set DPD timeout option
Can't set DPD timeout option
Product: Fedora
Classification: Fedora
Component: NetworkManager-vpnc (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-28 18:50 EST by Matthew Saltzman
Modified: 2008-11-17 09:01 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-17 09:01:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Saltzman 2007-11-28 18:50:27 EST
Description of problem:
There is an issue with recent vpnc releases (in particular, the one in Fedora 8)
where connections are dropped fairly regularly by the dead-peer detector.  See
bug #345281.

The workaround is a parameter in the config file for vpnc to adjust the DPD
timeout or turn it off, but there is no way to specify the option for a
connection in NM-vpnc.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Connect using NM-vpnc.
2. Wait.
Actual results:
No way to set options in VPN connection editor.
Connection drops.

Expected results:
Options for vpnc can be set in connection editor.
Connection persists until terminated.

Additional info:
Comment 1 Dan Williams 2008-06-26 17:36:50 EDT
I rolled disabling the DPD timeout into the recent rewrite of the vpnc plugin UI
bits.  Its in upstream trunk now and will hit Fedora with the next update.  I
don't have a way to reliably test this outside of just switching the value on
and off (our concentrators do OK with DPD) so if anyone can build from SVN and
see if it works, that would be great.
Comment 2 Dan Williams 2008-11-17 09:01:22 EST
Should be long-fixed; please re-open if it's not.

Note You need to log in before you can comment on or make changes to this bug.