** Changed in: vpnc (Ubuntu)
Assignee: Michael Bienia (geser) = Anton (bogatyia)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93413
Title:
vpnc dead peer detection disconnects immediately
To
OK, What I suspected (and kind of confirmed) was that whatever is being
used as the address to ping when the connection status check is enabled
but the specific IP address is unchecked doesn't work in all cases.
To test my theory I turned the connection status check back on, also
checked the use
With Hardy (8.04) and KVPNC from the repository I was experiencing a
similar problem.
I could get connected with our Cisco VPN, but then after a few seconds
the connection would go down and shortly after that would not reconnect
until I Quit KVPNC.
I played around with some timing and in
Excuse me, i lost same thing:
A similar aproach, I used that work whit kvpnc is:
sudo mv /usr/sbin/vpnc /usr/sbin/vpnc2
sudo nano /usr/sbin/vpnc
Put this lines in file:
#!/bin/bash
/usr/sbin/vpnc2 --dpd-idle 0 $*
sudo chmod +x /usr/sbin/vpnc
It is a similar solution, but don't hang kvpnc.
A similar aproach, I used that work whit kvpnc is:
sudo mv /usr/sbin/vpnc /usr/sbin/vpnc2
sudo nano /usr/sbin/vpnc
Put this lines in file:
#!/bin/bash --dpd-idle 0 $*
sudo chmod +x /usr/sbin/vpnc
It is a similar solution, but don't hang kvpnc.
--
vpnc dead peer detection disconnects
a more logical aproach:
mv /usr/sbin/vpnc /usr/sbin/vpnc2
vi /usr/sbin/vpnc #new file with content:
#!/bin/bash
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
cat | /usr/sbin/vpnc2 --non-inter --no-detach --dpd-idle 0 -
chmod +x /usr/sbin/vpnc
--
vpnc dead peer
da isses nimm option 2.
am besten du speicherst ein kleines script in /usr/local/bin ab
etwa der art:
#!/bin/bash
sudo vpnc-disconnect
sudo vpnc-connect outside --dpd-idle 0
knarf schrieb:
For network-manager-vpnc you can either patch the program:
--- nm-vpnc-service.c.org 2008-05-01
For network-manager-vpnc you can either patch the program:
--- nm-vpnc-service.c.org 2008-05-01 21:40:38.0 +0200
+++ nm-vpnc-service.c 2008-05-01 20:58:24.0 +0200
@@ -379,6 +379,8 @@ static gint nm_vpnc_start_vpnc_binary (N
g_ptr_array_add (vpnc_argv, (gpointer)
how to do this with network-manager-vpnc?
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Try fooling with the value for --dpd-idle
--dpd-idle 0,10-86400
DPD idle timeout (our side) 0,10-86400
Send DPD packet after not receiving anything for idle seconds.
Use 0 to disable DPD completely (both ways).
Default: 300
i.e.
In your config file have the line:
DPD idle
** Changed in: vpnc (Debian)
Status: New = Fix Released
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I have the same problem with 0.4.0ubunutu1.1 . It connects fine and is alive
for sometime but disconnects suddenly without any notification. Here is the
debug output
---
length: 0014
d.doi: 0001 (ISAKMP_DOI_IPSEC)
I am so sorry for the report above. On a clean Feisty installation
(same computer, same server) I was able to connect using vpnc
0.4.0ubuntu1.1 to my Cisco VPN Server.
I can however garantee that the problem I had before (also with
feisty) was consistent: 0.4.0-1.1 didn't work but 0.3.3 did. I
I'm having this problem (disconnecting after 30s) with up-to-date feisty
with feisty-updates in use.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
It is fixed in version vpnc-0.4.0-2ubuntu1.1 (notice the .1 at the end)
Go to Synaptic and check what version is it that you have installed and
what version is available for install.
Also check your repositories list.
--
vpnc dead peer detection disconnects immediately
I guess that message was just intended for Lynoure, because I have the
problem with the 1.1 package as well (but not with the 0.3.3)
On 06/07/07, ih [EMAIL PROTECTED] wrote:
It is fixed in version vpnc-0.4.0-2ubuntu1.1 (notice the .1 at the end)
Go to Synaptic and check what version is it that
Hmm... Maybe it's a different problem or manifestation of said problem.
I definitely had the problem and it was definitely fixed for me with the
1.1 release (of 0.4). I am using it pretty much every day for extended
periods of time. I had only one case when conenctivity disappeared, but
network
I can second tanas's experience. Connection break-down after about 30
seconds with the lates vpnc, but not with 0.3.3
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Hate to say but I still get the no response from target message with
0.4.0ubuntu1.1 (yes I'm sure it's 1.1 and not 1).
Downgraded to 0.3.3 and it is working fine.
(then I upgraded back to 0.4.0-1.1 which failed again, and then back to 0.3.3
which worked fine)
(sorry, I'm a sort of newbie and
tanas: do you ever connect? If not, you are probably not facing this bug.
If you indeed connect and disconnect exactly after 30 seconds, you probably are
facing this bug - but that should not be possible, heh:-).
--
vpnc dead peer detection disconnects immediately
I was indeed connected with 0.3.3.
vpnc said I was connected;
During the connection I checked my IP, and it was no longer the one I had
before, but the IP from the VPN Server I was connected to;
I was able to connect to online services that depend on the vpn connection
(intranet for instance);
Are you trying from the command line? Do you ever get an IP from the VPN
server? (with current version)
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Yep, from the command line (sudo vpnc-connect)
I dont know if I get the VPN server IP.. just have 15 seconds to
check.. Is there any way to check that?
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a
well, the simplest probably is to open another gnome-terminal and
periodically run ifconfig - if you do not see something there, it is
unlikely you are dealing with this bug (open anoter bug, maybe try to go
upstream first - link to vpnc mailing list is somewhere above)
--
vpnc dead peer
Uhm, I am behind a firewall, so ifconfig just gives the usual 192.168...
I tried a more primitive method: connecting with vpnc during a download. The
download rate never decreased (which I guess it would if I were connected to
the vpn server).
So I guess it is indeed a new bug
--
vpnc dead
thanks anyway!
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
it does not matter if you are behind a firewall, vpn gives you a new IP
address anyway. a new interface called tun or tap is created usually.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of
Sorry, I meant behind a router.
I tried my primitive test (downloading while connecting) using 0.3.3
and the download was interrupted immediately after introducing the
login.
On 25/06/07, TomasHnyk [EMAIL PROTECTED] wrote:
it does not matter if you are behind a firewall, vpn gives you a new IP
I filed bug 119248 for the feisty-updates not enabled by default
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/119248
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which
I think I had to do the same think, though I do not remember since I
tweaked the sources.list by hand anyway.
Could you please fill this as another bug? Search if it has not been
reported before though. It might be by design but that would be strange
since that would mean we do not trust our own
I'm trying out the suggestion posted here:
https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/93413/comments/26
I must be missing a package. When I try this step:
sudo debian/rules binary
I get the following output:
dh_testdir
# Add here commands to compile the package.
/usr/bin/make
Alarik Myrin
Why don't you just use the updated package? It should be in feisty-updates by
now.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Ah yes, there it is, thank you.
Alarik
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Copied to feisty-updates.
** Changed in: vpnc (Ubuntu Feisty)
Status: Fix Committed = Fix Released
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Just another confirmation: works for me.
Kubuntu 7.04 amd64
vpnc 0.4.0-2ubuntu1.1
It has been the best version so far.
The previous version 0.4.0-2ubuntu1 disconnected in a minute.
vpnc in Dapper and Edgy disconnected in 10-15 minutes.
Current version does not disconnect - I have tested it for 40
** Changed in: vpnc (Debian)
Status: Fix Released = Unconfirmed
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
The fixed package works for me too.
The package has been available a week for testing and I count (including me) 5
works for me and no regressions. This should be enough to get the package
moved to feisty-updates.
Thanks for the testing.
** Tags added: verification-motu-done
** Tags removed:
** Changed in: vpnc (Debian)
Status: Unconfirmed = Fix Released
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I've unsubscribed ubuntu-universe-sponsors, as no further Ubuntu uploads
are currently required for this bug. If an alternate solution requires
sponsorship in the future, please resubscribe. Thank you.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
The new package is now available for testing from feisty-proposed.
Please comment if the proposed package works for you or not.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs,
Tested now with vpnc-0.4.0-2ubuntu1.1. The dead peer problem is fixed
but my connection has died twice after approx. 20 minutes. I will try to
revert to version 0.3.3+SVN to see if it is stable there.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You
Works for me in Feisty.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Problem solve for me.
Ubuntu feisty connect to a pix
Thanks
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
The problem with 20 minutes was not related, I had the same problem in
0.3.3+SVN. Fix is OK.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Tags added: verification-motu-needed
** Changed in: vpnc (Ubuntu Feisty)
Importance: Undecided = Medium
Assignee: (unassigned) = Michael Bienia
** Changed in: vpnc (Ubuntu)
Status: Fix Committed = Fix Released
--
vpnc dead peer detection disconnects immediately
Works for me, at least as much as I can say after 1,5 hour long testing.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I see the new version in Gutsy, but not in feisty-proposed. I'm hoping
this will automatically happen by setting the status to Fix Committed as
per https://wiki.ubuntu.com/MOTU/SRU.
** Changed in: vpnc (Ubuntu)
Status: Needs Info = Fix Committed
--
vpnc dead peer detection disconnects
** Changed in: vpnc (Ubuntu Feisty)
Status: Unconfirmed = Fix Committed
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Accepted into feisty-proposed. Please go ahead with testing and update
the bug tasks and their status for gutsy and feisty (See
https://wiki.ubuntu.com/MOTU/SRU).
** Changed in: vpnc (Ubuntu)
Status: In Progress = Needs Info
--
vpnc dead peer detection disconnects immediately
I think I should clarify my previous, probably too brief, comment.
I asked on #ubuntu-motu for guidance on how to proceed with this ticket.
It was agreed that 06_stolen_from_head.dpatch was too large to back out,
so the http://lists.unix-ag.uni-kl.de/pipermail/vpnc-
devel/2007-April/001498.html
hm, there is nothing (as of now) in proposed:
http://archive.ubuntu.com/ubuntu/dists/feisty-
proposed/universe/binary-i386/Packages.gz
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
great, so, will it get in Feisty, then? If any testing is needed, let me
know.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Thanks for the debdiff James.
I've removed the unrelated change to vpnc-script from the dpatch and
added a comment about the changed default value for --dpd-idle to the
changelog.
I've uploaded it then to feisty-proposed and gutsy. It should appear in
feisty-proposed in a few days. I'll announce
This https://wiki.ubuntu.com/MOTU/SRU documents the procedure to get an
bug-fix into a stable release. There are three possible conditions of
which at least one needs to be met in order to commit a bug-fix. For
this, Bugs which represent severe regressions from the previous release
of Ubuntu might
I consulted #ubuntu-motu and merged the upstream change referenced
above. The only change I made was to set the DPD idle timeout to 0 by
default, to disable DPD unless explicitly set by the user. This means
users don't get disconnected by DPD as the default behaviour.
** Attachment added: Patch
** Changed in: vpnc (Debian)
Status: Unknown = Unconfirmed
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
The vpnc patch pointed out by TomasHnyk (thanks for the pointers!) is
actually a better solution than I'd proposed -- allowing users to
configure the DPD timeout with a default value of 300 seconds, rather
than a hard-coded timeout. Setting the timeout to 0 disables DPD. Much
cleaner.
I wonder
@DevenPhillips
I only think that people with need to connect to universities connect
throw a pix, and to do that i think the solution in post 26 is the best,
or solve the problem that new patch create, because graphical is more
easy to new commers to ubuntu.
Just my 2 cents.
--
vpnc dead peer
Also, the broken code should be rather fixed upstream, disabling it
during compiling is only a workaround, not a solution. I would also call
for downgrading for the reasons mentioned above (plus the pacakge is
tested - however, we need to look if there were any bugs solved by
3.34.0 upgrade in
Panda_N_Shark said:
I only think that people with need to connect to universities
connect throw a pix,
I disagree. I know more people who connect to business networks through
PIX appliances than University networks. The technology is equally
applicable in either situation.
and to do that i
James,
I second that. On purpose, I left the description of the newly opened
network-manager-vpnc bug open as open can. I think this config stuff
should handled in a more general way by the UI part and its plugins, and
not by vpnc itself.
And yes, it might happen that certain config options are
** Bug watch added: Debian Bug tracker #416180
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416180
** Also affects: vpnc (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416180
Importance: Unknown
Status: Unknown
--
vpnc dead peer detection disconnects
This is also reported in Debian (I added the link)
As for the development, they know about it, from their website
(http://www.unix-ag.uni-kl.de/~massar/vpnc/) Known Bugs vpnc looses
connection with some targets, even before the rekey-timer expires most
probably due bugs with keepalive,
I would only add that in order to prevent Update manager from ranting
about upgrding vpnc after following advice in 26 , just dowload the deb
(it can be found in /var/cache/apt/archives after install or reinstall,
extract it using dpkg-deb -x int a Directory, extract its control files
by dpkg-deb
OK folks, how do we need to move forward on this?
- Firstly, should the patch I submitted be reversed so that DPD
disabled is the default behaviour and users can enable DPD by using an
Enable Dead Peer Detection config option?
- I guess whichever way it goes I'll need to edit documentation
I connect to a pix, in windows i need cisco vpn client, now in ubuntu
and the reverse thing (post 26) solve my connection problem
Now everything works great. I vote too go back :D
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug
I vote that we implement the patch to be able to disable DPD. The patch is
currently available in the repository for vpnc. I think this is the best
solution. Unfortunately, as mentioned in previous posts, this breaks
compatibility with the graphical tools. Personally, I think that going
forward is
Just realised that I was taling rubbish in my previous post!
To confirm: steps in comment 26 above fixes/works-around my dead peer
detection issue when connecting to a PIX 515E.
Bug: https://bugs.launchpad.net/ubuntu/+source/network-manager-
vpnc/+bug/92570 is totally unrelated and the new .deb
Hi,
Comment 26 fixes for me also- Ubuntu 7.04 2.6.20-15-generic.
FYI, I'm now using network-manager-vpnc and ran into this issue:
https://bugs.launchpad.net/ubuntu/+source/network-manager-
vpnc/+bug/92570. The new .deb supplied in comment 19 has both fixed
(worked-around) my dead-peer-detection
James,
I opened a new bug report (Bug #112406) on the second (UI) part.
However, fixing this will presumably take up some time.
This issue, though, should be fixed real soon now (tm), since it renders
network-manager-vpnc useless for many business (here, ma'am) users
useless.
I propose to raise
Comment 26 result to me.
If you will try don't forget to install dpatch if get an error when do
sudo debina/rules binary
Thanks m8
This should be fixed because now we have always update manager ask for
update...
Fix this please
--
vpnc dead peer detection disconnects immediately
I think there are two issues here -- the first, that DPD doesn't work in
some circumstances, can be worked around with the ability to disable DPD
in those circumstances. In fact perhaps it should be disabled by
default so that those with appliances with which DPD would cause
problems get the
I'm also affected by this bug.
But I'm not yet sure how to fix it.
Disabling the 06_stolen_from_head patch disables more changes than
necessary but should also work for network-manager-vpnc users.
Adding the option to disable dpd is the better fix but only useful for
those using vpnc-connect.
Downloaded the vpnc sources and removed the 06 line as stated. I got a
error trying to compile the Debian way, so I just removed the vpnc
packages then just make, make install and my vpnc is now working
perfectly again.
I think this is pretty serious big, and seems fairly simple to fix, at
least
As of yesterday, the configuration option to disable Dead Peer Detection
in vpnc is in the CVS repository for vpnc. Can we get an updated Ubuntu
package soon?
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you
If I understand DevenPhillips' last message correctly, this is no longer
required, but I'm attaching the corrected, tested patch to allow
disabling of Dead Peer Detection.
I have an AMD64 package available if others would like to test it.
If you wish to build your own package:
- place this
SOLUTION
https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/93413/comments/26
WORKS
even on x86_64 - just change
sudo dpkg -i vpnc_0.4.0-2ubuntu1_i386.deb
to
sudo dpkg -i vpnc_0.4.0-2ubuntu1_amd64.deb
* artt, you saved my life! :-) *
Yesterday, I upgraded from Ubuntu 6.10 to 7.04 and today I
I also concur with the results. artt's removal of the 06 patch fixes the
client for me.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
But doesn't removing the 06 patch completely disable DPD and some other
functionality even for those devices with which it works?
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs,
can't apt-get source vpnc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to find a source package for vpnc
bmy /etc/apt/source.list/b
deb http://us.archive.ubuntu.com/ubuntu feisty universe
deb http://wine.budgetdedicated.com/apt feisty
aoyoyo, I think you need to add universe to the deb-src line, thus:
deb-src http://th.archive.ubuntu.com/ubuntu/ feisty main restricted
universe
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member
Hi James,
You have something else. I got this error.
[EMAIL PROTECTED]:/usr/src$ sudo apt-get source vpnc
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Could not open file
I think you have to do an
apt-get update
before you can access the repository
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
functioning. thanks a lot artt.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm attaching above-mentioned patch for someone with greater knowledge
than me to test.
The patch is completely untested as I currently have no idea about
building and packaging in Ubuntu. I'm sure I'll get up to speed
eventually, but in the meantime if someone else is able to apply the
patch
Comment 26 by artt fixes problems for me as well. Connecting to a Cisco
here...
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Same problem, connecting to a PIX. Is there a smooth way around this
problem while this is fixed in Ubuntu?
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I've solved it by rebuilding without the patch:
cd /usr/src
sudo apt-get source vpnc
cd vpnc-0.4.0/debian/patches
sudo gedit 00list
remove the line 06_stolen_from_head
cd ../..
sudo debian/rules binary
cd ..
sudo apt-get remove vpnc
sudo dpkg -i vpnc_0.4.0-2ubuntu1_i386.deb
if you had
I'm working on a patch to allow a config option to disable RFC3706 Dead
Peer Detection. All being well should be available in the next day or
so.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member
I'm seeing this problem as well ... and would be willing to help
troubleshoot as much as needed. However, I'm at the same point as James
Tait (I'd need very specific instructions on what to do and what to look
for).
I'm connecting to a PIX 515...
--
vpnc dead peer detection disconnects
I have currently rolled back to 0.3.3 but I'm willing to help out with
fixing 0.4.0. While I can't offer unrestricted access to our production
PIX, I'm quite happy to supply debug output where it will help. Note
that I'm not really familiar with the Debian/Ubuntu build process, so
I'd need to
I have similar problems with the vpnc package.
Rolling back to 0.3.3 is not an option for me, because my environment
requires the 'vendor' option which is introduced in 0.4.0.
Compiling 0.4.0 from source solves the problem for me.
In my opinion the best solution is to remove the patch and
Hi,
it does not seem to be specific to pix asa. I got the same problem here
with a Cisco 1812 Router.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
No, the bug is not PIX specific. The problem appears to be with the Dead
Peer Detection code in vpnc. I have spoken with people on the vpnc
development team and they are looking for people to help in debugging
the problem. I would recommend rolling back to 0.3.3 for Feisty final
release though
With the feisty release only a week away what should we do to resolve
this bug?
The Debian bug report lists a fix to be removing the patch
06_stolen_from_head.dpatch
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416180)
Another option would be to revert back to VPNC 3.3
Luca, Can you
I have the same problem. vpnc disconnects in less than a minute in
feisty.
--
vpnc dead peer detection disconnects immediately
https://bugs.launchpad.net/bugs/93413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I'm having this same problem. Some code from /var/log/syslog (not too
much):
Apr 5 13:45:51 ltsp-2 vpnc[30422]: connection terminated by dead peer
detection
That's all that is relevant. I'm connecting to a Cisco 3060
Concentrator. Not PIX at all.
--
vpnc dead peer detection disconnects
I don't know how to install an older version except doing the way I just
did:
Added into /etc/apt/source.list:
deb http://se.archive.ubuntu.com/ubuntu/ edgy universe
deb-src http://se.archive.ubuntu.com/ubuntu/ edgy universe
Started Synaptics, searched for 'vpnc' and deinstalled my current
What devices are everyone connecting to. Could this problem be specific to
the PIX? Are any VPN concentrator users having this issue?
Deven Phillips, CISSP, CCNA
On 4/3/07, ThomasNovin [EMAIL PROTECTED] wrote:
I don't know how to install an older version except doing the way I just
did:
The one I was connecting to was a Cisco Pix 515. Which I know is very
old. Its been since swapped with a newer ASA, but I have yet to test to
see if I'm still having problems with the ASA. But after seeing someone
else having problems also with an older PIX, I've wondered myself if its
just a
1 - 100 of 113 matches
Mail list logo
