From: Patrick McHardy <kaber@trash.net>
To: Linux Netdev List <netdev@vger.kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Subject: IPsec PMTUD problem
Date: Mon, 02 Apr 2007 16:10:25 +0200 [thread overview]
Message-ID: <46110ED1.9070209@trash.net> (raw)
I noticed a problem with PMTUD between two IPsec tunnel endpoints.
When sending a packet larger than the PMTU with IP_DF from one
tunnel endpoint to the other, xfrm4_output sends an ICMP frag.
required with the IPsec MTU. Since the addresses match the tunnel
endpoints, this updates the MTU for the XFRM route with the value
that was calculated for the entire bundle, which in turn causes
a decrease for the bundle, resulting in further ICMP frag. required
messages until the minimum is reached.
For example with an IPsec tunnel 10.0.0.1 <-> 10.0.0.2:
uml:~# ping 10.0.0.1 -M do -s 1500 -c 20
PING 10.0.0.1 (10.0.0.1) 1500(1528) bytes of data.
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1428)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1356)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1284)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1212)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1140)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 1068)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 996)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 924)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 852)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 780)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 708)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 636)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 564)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 552)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 492)
>From 10.0.0.2 icmp_seq=1 Frag needed and DF set (mtu = 492)
...
I can't come up with a way to fix this, so I'm hoping someone else
has an idea.
next reply other threads:[~2007-04-02 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:10 Patrick McHardy [this message]
2007-04-03 9:55 ` IPsec PMTUD problem Herbert Xu
2007-04-03 16:32 ` Patrick McHardy
2007-04-05 12:04 ` Herbert Xu
2007-04-05 12:09 ` Patrick McHardy
2007-04-05 12:12 ` Herbert Xu
2007-04-05 12:16 ` Patrick McHardy
2007-04-05 12:17 ` Herbert Xu
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=46110ED1.9070209@trash.net \
--to=kaber@trash.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;
as well as URLs for NNTP newsgroup(s).