After suspend&resume, my vpnc tunnel stays dead.
It should either do like pppd (detect when the connection doesn't work any more
and restart) or at least provide down+up scripts that hook into /etc/pm.

Hi Stefan,

it's been two years since you filed this bug, and vpnc has had a change
of maintainer, still I'm sorry for not looking into this in time for
wheezy.

I agree that that would be nice to have, but vpnc currently lacks
support for doing this either automatically or triggered by a signal. I
haven't looked at the code in much detail, but I don't think vpnc
remembers things such as the password it prompted the user for, so it
doesn't necessarily have all the data to restart the vpn connection
automatically. And as upstream development has slowed to a crawl, I
don't see a point in forwarding a feature request without at least a
rough patch...

What we can do in Debian, though, is to hook into suspend and kill the
vpn connection. It is unlikely to be alive after more than a very short
suspend, so it may be better for everybody if we clean up after
ourselves and restore routing etc. If the vpn is still needed after
resume, the user will have to restart it manually, though.

Does that make sense? Would adding such a feature be helpful?

Florian

[...]

I don't use vpnc any more, but yes, down&up scripts that are triggered
by suspend&resume would be helpful.


        Stefan

[...]

I don't use vpnc any more, but yes, down&up scripts that are triggered
by suspend&resume would be helpful.


        Stefan