Your message dated Mon, 20 Apr 2009 10:08:16 +0200
with message-id <[email protected]>
and subject line resolved
has caused the Debian Bug report #519392,
regarding vpnc >=0.4 doesn't seem to like an ASA
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
519392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519392
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vpnc
Version: 0.5.1r334-1
Hi,
I've been connecting to a newer ASA VPN device, but the new vpnc from lenny
decided that it no longers wants to do that.
% sudo vpnc-connect myconfig
vpnc-connect: no response from target
% sudo cat /etc/vpnc/myconfig.conf
IPSec gateway vpn.fqdn
IPSec ID groupid
IPSec secret groupsecret
Xauth username myusername
Xauth password mypassword
This used to work with etch and vpnc version 0.3.3+SVN20051028-3, so it
looks like it's a problem with the newer version... A colleague bisected it
via snapshot.d.n and it looks like doesn't work since version 0.4.0.
What's the debugging information that we could provide, a log of from
a working connection with what debug level?
--
2. That which causes joy or happiness.
--- End Message ---
--- Begin Message ---
It has been tracked down to too small MTU (1200) on one of the Cisco
ASA interfaces.
Upon fixing that, vpnc 0.4.0 and above automagically started to work
just fine, same as older versions. Closing.
--
Opinions above are GNU-copylefted.
--- End Message ---
