From: "Alessandro Suardi" <alessandro.suardi@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: rdreier@cisco.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6.21-git2] sk_buff changes break Cisco VPN client
Date: Sun, 29 Apr 2007 09:14:35 +0200 [thread overview]
Message-ID: <5a4c581d0704290014p1ee107a7jb4c6737f51ef8bb8@mail.gmail.com> (raw)
In-Reply-To: <20070428.202405.14973612.davem@davemloft.net>
On 4/29/07, David Miller <davem@davemloft.net> wrote:
> From: Roland Dreier <rdreier@cisco.com>
> Date: Sat, 28 Apr 2007 14:05:27 -0700
>
> > However I can suggest vpnc (http://www.unix-ag.uni-kl.de/~massar/vpnc/)
> > as an alternative. I'm not forced to use Cisco VPN access any more,
> > but when I tried it, vpnc was tons better than the Cisco product.
>
> Also, and I know this might be a COMPLETE SHOCK to some people, but we
> do have a full in-kernel IPSEC stack and using it with openswan to
> connect to VPNs works perfectly fine.
>
> I use it every day.
>
> It's quite amusing that people use a userland IPSEC implementation
> via VPNC, in spite of this.
>
Have a look here
https://lists.dulug.duke.edu/pipermail/dulug/2007-March/010792.html
where someone seems to be in my same boat. No, openswan/IPSEC
does not work in all configurations with Cisco VPN concentrators -
and by Murphy's law, I'm in the non-working configuration.
Hope this clarifies the reason I asked. And if anyone out there
is in doubt about it, I absolutely hate having to rebuild an out
of kernel module every time I build a kernel, crossing fingers
it doesn't break (again). I would use *anything* else.
--alessandro
"Did you get married but forgot to get divorced ?"
(Danny and Dusty, 'The Good Old Days')
next prev parent reply other threads:[~2007-04-29 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 20:38 Alessandro Suardi
2007-04-28 20:49 ` Phil Oester
2007-04-28 21:05 ` Roland Dreier
2007-04-28 21:19 ` Alessandro Suardi
2007-04-29 3:24 ` David Miller
2007-04-29 7:14 ` Alessandro Suardi [this message]
2007-04-28 21:26 ` Alan Cox
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=5a4c581d0704290014p1ee107a7jb4c6737f51ef8bb8@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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
all inboxes | Powered by JetHome®