From: Yura Pakhuchiy <pakhuchiy@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Per route MTU settings are broken in linux kernel 3.2
Date: Mon, 24 Jun 2013 15:44:03 +0700 [thread overview]
Message-ID: <1372063443.32157.10.camel@linux> (raw)
Hello Ben,
Looks like setting per route MTU (as described in [1]) is broken in
Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
looks like problem is fixed there. I filled Ubuntu bug report [2] with
more details and sample script which illustrates problem. But since this
problem is probably also present in stock kernel (not just in Ubuntu),
is it possible to backport fixes to stable 3.2 series?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507
--
Best regards,
Yura
next reply other threads:[~2013-06-24 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 8:44 Yura Pakhuchiy [this message]
2013-06-24 12:45 ` Per route MTU settings are broken in linux kernel 3.2 Ben Hutchings
2013-06-24 13:08 ` Yura Pakhuchiy
2013-06-26 1:12 ` Ben Hutchings
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=1372063443.32157.10.camel@linux \
--to=pakhuchiy@gmail.com \
--cc=ben@decadent.org.uk \
--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 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).