All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Egerváry Gergely" <gergely@egervary.hu>
To: linux-kernel@vger.kernel.org
Subject: 3.4.92 MTU issues
Date: Tue, 10 Jun 2014 21:43:53 +0200	[thread overview]
Message-ID: <53975FF9.5070803@egervary.hu> (raw)

Hi,

we have just upgraded our systems from 3.4.91 (longterm) to 3.4.92.
Since then we are experiencing dozens of MTU-related network timeout
issues. Reverting back to 3.4.91 fixes all of these problems.

Both kernel versions are built from vanilla sources with the same
.config. These can be highly reproduced over VPN tunnels or even over
simple ethernet connections when using DNAT. (TCP port forward) It
looks like MTU path discovery is somehow affected.

ICMP is not filtered in our network. (For testing, we flushed all
iptables rules, set all policies to ACCEPT, and problem still exists.)
We do not use any special sysctl settings. Was there any changes
related to packet forwarding or MTU discovery?

Thank you in advance,
-- 
Gergely EGERVARY
Network Administrator

             reply	other threads:[~2014-06-10 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 19:43 Egerváry Gergely [this message]
2014-06-10 21:16 ` 3.4.92 MTU issues Alexei Starovoitov
2014-06-10 21:37   ` Florian Westphal
2014-06-11 10:33     ` Egerváry Gergely

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=53975FF9.5070803@egervary.hu \
    --to=gergely@egervary.hu \
    --cc=linux-kernel@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.