Netdev List
 help / color / mirror / Atom feed
From: David Madore <david+ml@madore.org>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: Linux Netdev Mailing-List <netdev@vger.kernel.org>
Subject: Re: possible routing table cache bug for mtu/advmss attributes in Linux 3.0.4
Date: Fri, 9 Sep 2011 23:28:15 +0200	[thread overview]
Message-ID: <20110909212815.GA5651@aldebaran.gro-tsen.net> (raw)
In-Reply-To: <CAAM7YA=t=s5EEVFte84oqWaKfqyoNhX_NsE5xWUKJ53u-+Es=g@mail.gmail.com>

On Thu, Sep 08, 2011 at 10:42:20PM +0800, Yan, Zheng  wrote:
> On Fri, Sep 2, 2011 at 5:46 AM, David Madore <david+ml@madore.org> wrote:
> > In a nutshell, the problem is this: my (manually entered) routing
> > tables specify an explicit MTU/MSS for certain IPv6 routes, and after
> > upgrading from 2.6.38.7 to 3.0.4, I found that this MTU/MSS setting is
> > sometimes ignored.  More precisely, it seems that connecting to a host
> > through the route in question causes a routing cache entry to be
> > created, and it is when this cache entry expires that the route
> > forgets the MTU/MSS setting.  (It may also be relevant that in my case
> > the route belongs to a routing table other than "main".)
> 
> Would you please try patch http://marc.info/?l=linux-netdev&m=131529445904858

Indeed, this appears to solve the problem I encountered.  Thanks!

-- 
     David A. Madore
   ( http://www.madore.org/~david/ )

      reply	other threads:[~2011-09-09 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 21:46 possible routing table cache bug for mtu/advmss attributes in Linux 3.0.4 David Madore
2011-09-08 14:42 ` Yan, Zheng 
2011-09-09 21:28   ` David Madore [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=20110909212815.GA5651@aldebaran.gro-tsen.net \
    --to=david+ml@madore.org \
    --cc=netdev@vger.kernel.org \
    --cc=yanzheng@21cn.com \
    /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