Date: Wed, 6 Sep 2006 08:36:21 +0200 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Adrian Steinmann <ast@webgroup.ch> Cc: mr@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FAST_IPSEC + device padlock + device crypto + IKE broken? Message-ID: <20060906063621.GA23449@garage.freebsd.pl> In-Reply-To: <20060906062912.GA44900@webgroup.ch> References: <20060906062912.GA44900@webgroup.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 06, 2006 at 08:29:13AM +0200, Adrian Steinmann wrote: > In my kernel config, I have >=20 > options FAST_IPSEC > device padlock > device crypto >=20 > which enables the crypto acceleration in VIA C3 and C7 CPUs. IPSEC > with static rijndael-cbc keys of length 128, 192, and 256 makes use > of the acceleration when sysctl net.inet.ipsec.crypto_support=3D1; > - so far, so good. >=20 > Yet when I configure racoon from ipsec-tools, racoon2, or iked for > dynamic keying, I get a "PFKEYv2 UPDATE" (or similar) failure. When > I set net.inet.ipsec.crypto_support=3D0 these same dynamic ike key > configurations work, albeit without HW crypto accelleration. >=20 > Has anyone else observed this and know what the problem is? Is this after my recent padlock(4) update in RELENG_6? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFE/mxlForvXbEpPzQRAqRPAJ9ZW6vawaxe6oFspGfHrjQC2IlFEwCfbC5Z IkQqSPcXHrGhboO7M5+QEpE= =P+A7 -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060906063621.GA23449>