Package: vpnc
Version: 0.4.0-3
Followup-For: Bug #416180
With the sync of SVN revision 174, disabling dead peer detection
seems to fix the problems people were having, but the option has to be
fed to either vpnc or vpnc-connect manually, which is unexpected for a
lot of people most likely when 0.3.3 just worked.
I'm not sure if forcing dpd to 0 by default would be acceptable.
I would say it is acceptable if more people are having problems than not
with the inclusion of this feature.
Anyway, for people like Tobias who are still having problems,
issuing:
vpnc-connect --dpd-idle 0 yourconfig.conf
should revert 0.4.0 back to the behavior of 0.3.3, more or less.
It's just something people will have to be aware of about vpnc
from now on if the default behavior is going to be to keep dpd enabled.
But obviously there are plenty of Cisco boxes in the wild which are
reporting dpd capability and, unless it's a bug in vpnc itself, don't
seem to implement the functionality correctly.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.21.3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages vpnc depends on:
ii libc6 2.5-10 GNU C Library: Shared libraries
ii libgcrypt11 1.2.4-2 LGPL Crypto library - runtime libr
vpnc recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
