linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Sightler <ttsig@tuxyturvy.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Poor IPSec performance with 2.6 kernels
Date: 27 Aug 2003 22:38:24 -0400	[thread overview]
Message-ID: <1062038303.2947.11.camel@iso-8590-lx.zeusinc.com> (raw)

Hi all.

I'm looking for suggestions as to why my IPSec performance is so bad
when using the built in 2.6 IPSec implementation.

My setup is pretty simple, a tunnel with a Watchguard Firebox on one end
and an AMD K6/333 on the other end running Redhat 9.  I've used two
different IPsec implementations on the Linux system, one is
SuperFreeS/WAN with a patched Redhat kernel using the available SRPMS
and the other is the built-in 2.6 IPSec code with racoon.

My Internet connection is a DSL circuit that typically delivers about
150KB/s.  When I connect with SuperFreeS/WAN my VPN throughput is quite
good, averaging about 125KB/s (this seems about reasonable with
overhead) but when making the identical connection with racoon and the
2.6 kernel I can only achieve 50KB/s.  I've been unable to come up with
any reason why this would be the case.

Any hints would be appreciated.

Later,
Tom





             reply	other threads:[~2003-08-28  2:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28  2:38 Tom Sightler [this message]
2003-08-28  2:56 ` Poor IPSec performance with 2.6 kernels James Morris
2003-08-28 10:16 Adam J. Richter
2003-08-28 13:09 ` Tom Sightler
2003-08-28 13:40   ` James Morris
2003-08-28 18:56 kartikey bhatt
2003-08-29  1:37 ` James Morris
2003-08-30 17:13 kartikey bhatt
2003-09-01 17:25 kartikey bhatt

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=1062038303.2947.11.camel@iso-8590-lx.zeusinc.com \
    --to=ttsig@tuxyturvy.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).