Subject: IPSEC problems with GRE.
From: Julian Blake Kongslie <jblake@omgwallhack.org>
To: linux-kernel@vger.kernel.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0vHIMrTl5rCR2/k75JK5"
Message-Id: <1055746871.2305.7.camel@festa.omgwallhack.org>
Mime-Version: 1.0
Date: 16 Jun 2003 00:01:11 -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1578
Lines: 52


--=-0vHIMrTl5rCR2/k75JK5
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi there.

I've been playing around with IPSec, and I came across a problem with
encrypting data sent directly by the kernel.

Specifically, attempts to encrypt a GRE or IPIP tunnel with ipsec in
transport mode result in one of:
	1) No data sent.
	2) Data sent, ignored by peer.
	3) Kernel panic, with no SysRq.

Numbers 1 and 2 might be configuration problems on my part, but I have
other ipsec setups running fine, and can't see anything different for
these. Number 3 is a big problem.

This is on 2.5.70. No third-party modules or other tainting. I can
provide .configs on request.

I don't have the panic copied down, but I can reproduce it and get a
copy if required.

I know I could certainly accomplish what I want with ipsec tunnel mode,
but I'm just playing around, and it's a kernel bug in any case.

Thanks.

--=20
Julian Blake Kongslie <jblake@omgwallhack.org>

--=-0vHIMrTl5rCR2/k75JK5
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+7Ws3+6o3+Z/zOlURAjuJAJoDefpMe9jMIzgflHBrMG/2W3GDiwCg2ymU
SwF4UvBg3nSaK20/+Ymu6aE=
=KNBT
-----END PGP SIGNATURE-----

--=-0vHIMrTl5rCR2/k75JK5--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/