mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Julian Blake Kongslie <jblake@omgwallhack.org>
Cc: linux-kernel@vger.kernel.org, <netdev@oss.sgi.com>,
	"David S. Miller" <davem@redhat.com>, <kuznet@ms2.inr.ac.ru>
Subject: Re: IPSEC problems with GRE.
Date: Tue, 17 Jun 2003 21:28:45 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0306172117310.14332-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <1055746871.2305.7.camel@festa.omgwallhack.org>

On 16 Jun 2003, Julian Blake Kongslie wrote:

> 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.

I've not been able to reproduce the panic, but there is a potential issue
with path mtu which could explain (1) and (2):  the transport mode SAs 
between the gateways are not aware of the gre tunnel.

You need to lower the mtu on the gre tunnel at each end to take the ipsec
overhead into account.  This will cause the gateways to generate
appropriate icmp pmtu messages.

This is handled automatically for tunnel mode ipsec configurations.


- James
-- 
James Morris
<jmorris@intercode.com.au>


  parent reply	other threads:[~2003-06-17 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16  7:01 Julian Blake Kongslie
2003-06-17  9:20 ` James Morris
2003-06-17 11:28 ` James Morris [this message]
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=Mutt.LNX.4.44.0306172117310.14332-100000@excalibur.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=davem@redhat.com \
    --cc=jblake@omgwallhack.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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®