Netdev List
 help / color / mirror / Atom feed
From: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
To: netdev@vger.kernel.org
Cc: herbert@gondor.apana.org.au, davem@davemloft.net
Subject: ipsec: icmp fragmentation-needed from ipsec-gateway is not encrypted
Date: Tue, 18 Sep 2007 12:57:58 +0200	[thread overview]
Message-ID: <200709181257.58598.wolfgang.walter@studentenwerk.mhn.de> (raw)

Hello,

I have the following problem:

router A has two interfaces eth0 and eth1.

router B has two interfaces eth0 and eth1.

The networks on A:eth1 and B:eth1 are connected over an ipsec-tunnel.

the mtu on A:eth1 is 1400 (all others are 1500).

both run 2.6.22.6

If I now ping a host HA on A:eth1 from host HB on B:eth1 with packet size 
greater 1400 the ping fails.

tcpdump on A:eth0 shows

an esp-tunnel-packet from B comes in
icmp echo-request packet from HB to HA comes in
        (the decrypted esp-packet)
an unecrypted icmp fragmentation-needed packet to HB from A (ip of eth1) sent 
out

It seems to me that this fragementation-needed packet generated by B is not 
handled by ipsec, is sent out unencrypted instead and this is the reason it 
does not reach HB.

I should not see the unecrypted packet going out at all? Because if I ping 
A:eth1 from HB then I don't see the unencrypted echo-reply packet (which has 
the same source-address as the fragmentation needed) but only the outgoing 
esp-packet (and the echo-reply reaches HB, by the way).

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

                 reply	other threads:[~2007-09-18 10:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200709181257.58598.wolfgang.walter@studentenwerk.mhn.de \
    --to=wolfgang.walter@studentenwerk.mhn.de \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@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