From: Philipp Matthias Hahn <pmhahn@pmhahn.de>
To: Mariusz Smykula <mariuszs@gmail.com>
Cc: Fabio Comolli <fabio.comolli@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.29+ broke Cisco VPN Client
Date: Wed, 11 Nov 2009 07:25:37 +0100 [thread overview]
Message-ID: <20091111062537.GA13282@pmhahn.de> (raw)
In-Reply-To: <3642a3130911100149t7452a6f3k188e0fe972783521@mail.gmail.com>
Hello,
On Tue, Nov 10, 2009 at 10:49:48AM +0100, Mariusz Smykula wrote:
> On Tue, Nov 10, 2009 at 8:48 AM, Fabio Comolli <fabio.comolli@gmail.com> wrote:
> > Please have a look at:
> >
> > http://forum.tuxx-home.at/viewtopic.php?f=15&t=790#p5227
> >
> > There is a patch there that can be used to make CiscoVPN work with the
> > latest stable kernels. For me it worked fine (over a wifi connection)
> > until I lost interest as now I'm able to use vpnc, thanks to the
> > people on the vpnc support forum.
>
> I have no problem to compile and connect using CiscoVPN + 2.6.31, but
> this is unstable solution. After some time (seconds or minutes) whole
> computer is freezing dead.
>
> vpnc is no option, because he lacks supports of certs auth.
You might want to give http://www.shrew.net/software a try. I'd be
interested if this works for you.
BYtE
Philipp
--
/ / (_)__ __ ____ __ Philipp Hahn
/ /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de
prev parent reply other threads:[~2009-11-11 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 17:08 Kernel 2.6.29+ broke Cisco VPN Client Mariusz Smykula
2009-11-09 17:57 ` Alan Cox
[not found] ` <3642a3130911092236p11ef0502se12788800c8d2084@mail.gmail.com>
2009-11-10 7:04 ` Mariusz Smykula
2009-11-10 7:48 ` Fabio Comolli
2009-11-10 9:49 ` Mariusz Smykula
2009-11-11 6:25 ` Philipp Matthias Hahn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091111062537.GA13282@pmhahn.de \
--to=pmhahn@pmhahn.de \
--cc=fabio.comolli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mariuszs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox