netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next crap] net: icmp: work around bogus pmtu errors
Date: Tue, 14 Jul 2015 15:40:09 -0700 (PDT)	[thread overview]
Message-ID: <20150714.154009.1071789496366560900.davem@davemloft.net> (raw)
In-Reply-To: <1436572609-2097-1-git-send-email-fw@strlen.de>

From: Florian Westphal <fw@strlen.de>
Date: Sat, 11 Jul 2015 01:56:49 +0200

> sometimes tcp connections seem to hang.
> tcpdump shows broken path mtu reports.  This "fix" avoids hang and gives:
> 
> [633.327834] icmp: 192.0.0.2 reports mtu 1474 for packet size 1474 to host 204.236.132.12
> [635.586945] icmp: 192.0.0.2 reports mtu 1474 for packet size 1474 to host 54.219.255.254
> [647.106708] icmp: 192.0.0.2 reports mtu 1474 for packet size 1466 to host 204.236.132.12
> [663.084586] icmp: 192.0.0.2 reports mtu 1474 for packet size 1466 to host 54.219.255.254
> 
> sigh.
> 
> Signed-off-by: Florian Westphal <fw@strlen.de>
> ---
>  Might be caused by DS-LITE.  I either need the turd below or iptables TCPMSS
>  mangling rules to artificially lower received mss.
> 
>  I don't mind if this is rejected; I'm mostly wondering if anyone
>  else came across suprise like this.

I think the culprit should be identified and fixed ASAP, the last thing we want
is for every system add a hack like this.

      reply	other threads:[~2015-07-14 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10 23:56 [PATCH -next crap] net: icmp: work around bogus pmtu errors Florian Westphal
2015-07-14 22:40 ` David 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=20150714.154009.1071789496366560900.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fw@strlen.de \
    --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).