From: Fabio Comolli <fabio.comolli@gmail.com>
To: Mariusz Smykula <mariuszs@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.29+ broke Cisco VPN Client
Date: Tue, 10 Nov 2009 08:48:19 +0100 [thread overview]
Message-ID: <b637ec0b0911092348x29453bco7f7ca94f3772601@mail.gmail.com> (raw)
In-Reply-To: <3642a3130911092304x5c8fe8ddme1df39e6981cfe0a@mail.gmail.com>
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.
Hope this helps.
[BTW, CiscoPVN is OT on this list]
On Tue, Nov 10, 2009 at 8:04 AM, Mariusz Smykula <mariuszs@gmail.com> wrote:
> On Mon, Nov 9, 2009 at 6:57 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> I must have imagined openconnect. Failing that you need to talk to your
>> distro if they shipped the module or to cisco.
>
> OpenConnect supports the new Cisco "AnyConnect" SSL VPN, not the old
> IPsec-based VPN. Cisco ended support for this software and devices and
> is not interested in helping us. All we have is open sourced cisco vpn
> client which is broken since 2.6.29.
>
> --
> Mariusz Smykuła
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-11-10 7:48 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 [this message]
2009-11-10 9:49 ` Mariusz Smykula
2009-11-11 6:25 ` Philipp Matthias Hahn
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=b637ec0b0911092348x29453bco7f7ca94f3772601@mail.gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.