no, personally i suspected you were under the impression it was current as someone else dragged it up. Just wouldn't want to you waste your time... feel free to keep discussing this issue if you wish to.

if you read the vpnc manpage...
standard "RTFM" response. Unnecessary and condescending.

not sure why you'd bother with watch for that, but...
Translation: If you were half as smart as I, you wouldn't be doing things so foolishly.

Perhaps he prefers watch because when he runs a disconnect script it is easier to kill a single watch command than it is to remove a job from the cron configuration. Why not post an example of how the almighty acid_kewpie would do things, and point out advantages and disadvantages of both methods?

Yeah... Three year old thread folks...
I mean, like, c'mon, this comment is soooooo 2006, gosh.

acid_kewpie is your typical Comic Book Guy of linux help. People like him discourage casual PC users from requesting help and adopting Linux, and they perpetuate the idea that linux is only for the geekiest of IT guys. You goddamned linux snobs shoot your own OS right in the foot. You know this right?

1 members found this post helpful.

As long as we're bringing up an ancient thread...

I chose watch over cron because this was on a laptop, and I couldn't count on always being connected to the internet, or to the VPN. Having something I could start manually seemed like a cleaner solution.

I recently found that ping has it's own interval parameter (-i) that eliminates the need for watch. However, the solution provided by barry_nay bunchipe looks like the best solution (I never had a chance to try it myself).

Thanx!

I tried the proposed solution some months ago... it is working perfectly and of course it is the cleaner one...

Thanks to bunchipe

I know this is an old thread....

Kvpnc->Manage Connections
Profile->Network->General

Check Ping hostname/IP address with something less than your timeout. I selected a server on my network that's always up.

In my case kVpnc started misbehaving after a Lucid->Natty upgrade (or untangle 8->9 not sure which atm).

Regards

FYI, I've found that my vpnc connection seems to be dropping under Ubuntu 12.
I do have the "DPD idle timeout (our side) 0" in my default.conf file, so I'm wondering if something has changed.

... but bunchipe's post still helped me solve my issue:

DPD idle timeout (our side) 0

in the vpnc.conf fixed my problem.

I found it helpful another 3 years later. Thanks.

1 members found this post helpful.

well that's certainly great, but your reply will not help others, just confuse them.

I see nothing at all confusing about joecam1673's post saying the thread helped him, and nothing at all inappropriate about acknowledging the contributions everyone has made to the thread over the past six years. If you want to throw out comments like "Yeah, three year old thread, folks" then expect some discussion about that.

Looks like bunchipe -- whose post actually solved my problem -- never came back to LQ, or at least, he never came back and posted again. I wonder if that had anything to do with a condescending moderator's attitude towards him.

So, aren't you allowed to thank people here then?

Still valid, Bunchipe's post helped me out.

CG: Many thanks 'bunchipe' ... your solution fixed this irritating VPNC session timeout very nicely for me.

This NAT keepalive option has fixed my problem. I didn't realise this VPN was setup like a NAT regardless it worked.