From: Benjamin LaHaise <bcrl@kvack.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: jchapman@katalix.com, davem@davemloft.net, netdev@oss.sgi.com,
kleptog@svana.org, mostrows@styx.uwaterloo.ca
Subject: Re: PPP-over-L2TP kernel support, new patch for review
Date: Tue, 21 Sep 2004 21:14:21 -0400 [thread overview]
Message-ID: <20040922011421.GE19575@kvack.org> (raw)
In-Reply-To: <E1C9tj0-0003KE-00@gondolin.me.apana.org.au>
On Wed, Sep 22, 2004 at 09:07:06AM +1000, Herbert Xu wrote:
> Benjamin LaHaise <bcrl@kvack.org> wrote:
> >
> >> - Unlikely to integrate with the new native IPSEC stuff.
> >
> > L2TP over IPSEC? Are you insane? You'd not be able to terminate more than
> > a couple of dozen connections over it. =-)
>
> Why not? L2TP over IPsec is the only reason I'm looking at L2TP at all.
CPU load. The main reason I was forced to revisit L2TP (imo, it's a
horrible protocol that suffers from too many bad decisions) was in its
role for terminating DSL. In this case one expects to be able to have
tens of thousands of connections terminated by a single box, which
means pushing hundreds of megabits of traffic. The overhead of crypto
operations in such a scenario makes it a far too costly choice.
-ben
next prev parent reply other threads:[~2004-09-22 1:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 21:11 PPP-over-L2TP kernel support, new patch for review James Chapman
2004-09-20 21:17 ` David S. Miller
2004-09-21 9:55 ` James Chapman
2004-09-21 21:04 ` Benjamin LaHaise
2004-09-21 23:07 ` Herbert Xu
2004-09-22 0:00 ` Michael Richardson
2004-09-22 1:14 ` Benjamin LaHaise [this message]
2004-09-22 2:42 ` David S. Miller
2004-09-22 3:03 ` jamal
2004-09-22 9:58 ` James Chapman
2004-09-22 10:53 ` Herbert Xu
2004-09-22 21:28 ` James Chapman
2004-09-22 22:05 ` Herbert Xu
2004-09-23 18:34 ` Martijn van Oosterhout
2004-09-21 21:11 ` Benjamin LaHaise
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=20040922011421.GE19575@kvack.org \
--to=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jchapman@katalix.com \
--cc=kleptog@svana.org \
--cc=mostrows@styx.uwaterloo.ca \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).