public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Question regarding IPsec N2N throughput with and without IPS
Date: Wed, 22 Jan 2020 16:24:00 +0000	[thread overview]
Message-ID: <c9ef30fe-d3ce-ace5-2cd4-0a4d446c689c@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]

Hello Stefan, hello list (CC'ed),

are you aware of any IPS bottlenecks regarding IPsec N2N throughput?

I finally (!) managed to get an IPsec connection between OpenBSD 6.6 (OpenIKED)
and IPFire 2.23 Core Update 139 working. During throughput tests, where
I downloaded a 1 GByte test file from the machine via the IPsec tunnel,
a rather large throughput difference with and without IPS enabled on RED
has come to my attention:

With IPS enabled on RED, the download starts at ~ 2.5 MByte/sec. and
continually decreases to ~ 580 kByte/sec. - 800 kByte/sec., which is
even lower than OpenVPN performance. Without IPS enabled on RED, throughput
is 4.0 MByte/sek. on average - running the IPS on other interfaces does
not change this behaviour, neither does enabling monitoring mode.

This suspiciously sounds like the issue we have had with Suricata last
year - as far as I am concerned that was fully fixed. Are you aware of
any other similar issue that could cause this massive throughput loss?

Anyway, thank you in advance for any help and hints. :-)

Kernel and CPU information of the OpenBSD machine:
> openbsd# uname -a
> OpenBSD openbsd 6.6 GENERIC.MP#4 amd64
> openbsd# sysctl hw.model hw.machine hw.ncpu
> hw.model=Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
> hw.machine=amd64
> hw.ncpu=2

Content of /etc/iked.conf on the OpenBSD machine:
> set fragmentation
> 
> ikev2 "[REDACTED]" active esp \
>    from 10.xxx.xxx.2/24 to 10.xxx.xxx.0/24 \
>    local [REDACTED] peer [REDACTED] \
>    ikesa auth hmac-sha2-512 enc aes-256 prf hmac-sha2-512 group curve25519 \
>    childsa enc aes-256-gcm group curve25519 \
>    srcid [REDACTED] dstid [REDACTED] \
>    ikelifetime 3h \
>    lifetime 1h

Kernel and CPU information of the IPFire machine:
> [root(a)maverick ~]# uname -a
> Linux maverick 4.14.154-ipfire #1 SMP Fri Nov 15 07:27:41 GMT 2019 x86_64 Intel(R) Celeron(R) CPU N3150 @ 1.60GHz GenuineIntel GNU/Linux

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2020-01-22 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 16:24 Peter Müller [this message]
2020-01-23 22:44 ` Michael Tremer
2020-01-24 14:32   ` Peter Müller
2020-01-24 16:49     ` Michael Tremer
2020-01-24 17:35       ` Peter Müller
2020-01-28 17:18         ` Michael Tremer

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=c9ef30fe-d3ce-ace5-2cd4-0a4d446c689c@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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