From: "Egerváry Gergely" <gergely@egervary.hu>
To: Florian Westphal <fw@strlen.de>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
stable@kernel.org
Subject: Re: 3.4.92 MTU issues
Date: Wed, 11 Jun 2014 12:33:24 +0200 [thread overview]
Message-ID: <53983074.6010800@egervary.hu> (raw)
In-Reply-To: <20140610213722.GE1970@breakpoint.cc>
> -stable lacks commit 895162b1101b3ea5db08ca6822ae9672717efec0, so
> netfilter never sets ->local_df. Thus all defragmented packets
> that go over the mtu are refused to be forwarded.
Thank you for your quick response. Should we expect a 3.4.93 release
with this issue fixed in a few days?
--
Gergely EGERVARY
Network Administrator
prev parent reply other threads:[~2014-06-11 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53975FF9.5070803@egervary.hu>
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 [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=53983074.6010800@egervary.hu \
--to=gergely@egervary.hu \
--cc=alexei.starovoitov@gmail.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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).