Bug 814921 - FR: Add systemd unit file to vpnc
FR: Add systemd unit file to vpnc
Status: NEW
Product: Fedora
Classification: Fedora
Component: vpnc (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Christian Krause
Fedora Extras Quality Assurance
: FutureFeature, Reopened, Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-04-21 06:15 EDT by Pavel Alexeev
Modified: 2014-11-07 05:15 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 07:58:36 EST
Type: Bug
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 Pavel Alexeev 2012-04-21 06:15:40 EDT
vpnc tunnels works mostly well, but times to times go down and needs to be reestablished manually or by some sort of script.

It is annoying.
There present in package script which handle all connects and disconnects and may be easily may be grow to daemon with reconnect support.

I have found this good post https://mknowles.com.au/wordpress/2009/05/03/persistent-vpnc-connections/ . It is Debian specific and SysV oriented, but all concepts clear and may be easy adopted for Fedora. I'm ready help with it if needed.

Please provide vpnc systemd service capability.
Comment 1 Fedora End Of Life 2013-01-16 07:38:11 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 2 Fedora End Of Life 2013-02-13 07:58:38 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 3 Fedora End Of Life 2013-04-03 15:15:20 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
Comment 4 Felix Schwarz 2014-11-02 17:20:40 EST
just for the record: There is a systemd unit file from Gentoo: https://github.com/gentoo/vpnc/blob/2af29eb2c26a98d270645dc185a8a34e269abd2b/systemd/vpnc%40.service
Comment 5 Felix Schwarz 2014-11-07 05:14:06 EST
prevent future auto-closing as this is a new feature and thus not tied to a particular Fedora version.
Comment 6 Felix Schwarz 2014-11-07 05:15:14 EST
actually this should be "NEW" as far as I can see (assignment not done by assignee)

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