From: "David S. Miller" <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: jmorris@redhat.com, kaber@trash.net, yoshfuji@linux-ipv6.org,
netdev@oss.sgi.com
Subject: Re: [net-2.6.13 0/3] [IPSEC] Allow PMTU discovery to be turned off
Date: Mon, 20 Jun 2005 13:24:01 -0700 (PDT) [thread overview]
Message-ID: <20050620.132401.21595297.davem@davemloft.net> (raw)
In-Reply-To: <20050613073353.GA21454@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Mon, 13 Jun 2005 17:33:53 +1000
> One of the problems that's been plaguing our IPsec stack is ICMP
> blackholes. ICMP blackholes are particularly bad for tunnels because
> the most common remediy -- MSS clamping has no effect when applied
> outside the tunnel. It is often impractical to apply it inside
> the tunnel since the point where the clamping is applied may be some
> way away from either IPsec endpoint.
>
> The best solution so far has been to disable PMTU discovery when a
> blackhole is detected. We already support that for IPIP/GRE tunnels.
> The following patchset adds support for a similar strategy to IPsec
> tunnels.
>
> It is by no means ideal but it's something that you need to survive
> on today's Internet.
All 3 patches applied, thanks Herbert.
One thing needs clarification in your description. When I first
read "blackhole is detected" I was under the wrong impression as
to _who_ does the detection. Your patches allow the administrator
to do this, whereas I thought you were going to add some code which
dynamically figured out the presence of ICMP black holes and would
thus set the bit.
prev parent reply other threads:[~2005-06-20 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050613073353.GA21454@gondor.apana.org.au>
2005-06-13 7:39 ` [net-2.6.13 3/3] [IPSEC] Add XFRM_STATE_NOPMTUDISC flag Herbert Xu
2005-06-20 20:24 ` David S. Miller [this message]
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=20050620.132401.21595297.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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