mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julian Blake Kongslie <jblake@omgwallhack.org>
To: linux-kernel@vger.kernel.org
Subject: IPSEC problems with GRE.
Date: 16 Jun 2003 00:01:11 -0700	[thread overview]
Message-ID: <1055746871.2305.7.camel@festa.omgwallhack.org> (raw)

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

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.

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-06-16  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16  7:01 Julian Blake Kongslie [this message]
2003-06-17  9:20 ` James Morris
2003-06-17 11:28 ` James Morris
2003-06-17 20:01   ` IPSEC problems with GRE. [RESOLVED] Julian Blake Kongslie

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=1055746871.2305.7.camel@festa.omgwallhack.org \
    --to=jblake@omgwallhack.org \
    --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

all inboxes | Powered by JetHome®