All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: IPsec PMTUD problem
Date: Thu, 05 Apr 2007 14:09:20 +0200	[thread overview]
Message-ID: <4614E6F0.10905@trash.net> (raw)
In-Reply-To: <20070405120425.GC10972@gondor.apana.org.au>

Herbert Xu wrote:
> On Tue, Apr 03, 2007 at 06:32:07PM +0200, Patrick McHardy wrote:
> 
>>I'm not sure I understand how this would work, the ICMP message
>>looks the same in both cases. Or are you suggesting to
>>differentiate based on the source of the ICMP message?
> 
> 
> Actually you're right, this can't work in the general case.  Even
> if we had real devices for IPsec tunnels, there is still no way to
> reliably figure out which device we should attribute a given MTU
> event to if the same address appears on more than one device.
> 
> 
>>Yes, that would work as a workaround, but it still seems like
>>something worth fixing.
> 
> 
> One possible solution is to not send MTU errors to ourselves since
> we it wouldn't give us any new information.  We'd need to audit the
> users of icmp_send to make sure that there isn't a legitimate case
> where we'd want to do that.


One such case is delivery of errors to sockets. We'd need to make
sure the errors are delivered some other way.

  reply	other threads:[~2007-04-05 12:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 14:10 IPsec PMTUD problem Patrick McHardy
2007-04-03  9:55 ` Herbert Xu
2007-04-03 16:32   ` Patrick McHardy
2007-04-05 12:04     ` Herbert Xu
2007-04-05 12:09       ` Patrick McHardy [this message]
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=4614E6F0.10905@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.