Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 May 2017 14:56:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 219356] Using AES-GCM with IPSEC with aesni module loaded panics FreeBSD 11 stable
Message-ID:  <bug-219356-8-cnazvJaEME@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219356-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-219356-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219356

Andrey V. Elsukov <ae@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ae@FreeBSD.org

--- Comment #1 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to lab from comment #0)
> Created attachment 182666 [details]
> Core text file from panic
>=20
> Using iperf to pass data between two hosts behind two FreeBSD gateways th=
at
> have an IPSec tunnel between them will panic gateway. The gateway that
> panics os the one doing most of the decryption (gateway in front of iperf
> running in server mode). I used iperf in UDP mode. Not sure if that is
> needed. If I use 11.0-RELEASE-p9 I do not see this issue.=20
>=20
> I used strongswan to create IPSec tunnel between gateways. If duplicating,
> make sure GCM option is turned on for strongswan.

What revision do you use to build FreeBSD 11.0-STABLE and what strongswan
version do you use? Does it panics immediately after starting iperf test or=
 it
needs some time?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219356-8-cnazvJaEME>