netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "bugme-daemon@kernel-bugs.osdl.org" <bugme-daemon@kernel-bugs.osdl.org>
Cc: netdev@vger.kernel.org, bugzilla@fire.lp0.eu
Subject: Re: [Bugme-new] [Bug 8754] New: Kernel addrconf modifies MTU of non-kernel routes
Date: Sat, 14 Jul 2007 15:09:08 -0700	[thread overview]
Message-ID: <20070714150908.093eefdb.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-8754-10286@http.bugzilla.kernel.org/>

On Sat, 14 Jul 2007 14:54:32 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8754
> 
>            Summary: Kernel addrconf modifies MTU of non-kernel routes
>            Product: Networking
>            Version: 2.5
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: IPV6
>         AssignedTo: yoshfuji@linux-ipv6.org
>         ReportedBy: bugzilla@fire.lp0.eu
> 
> 
> I have an MTU of 16110 set on eth0 on a network where the MTU is 1500 as set by
> RAs. One of the other hosts on the network has an MRU/MTU of 7200 so I have a
> specific route to it with this MTU.
> 
> If I add the route early (i.e. on startup) before address autoconfiguration
> takes place, when the first RA is received the kernel changes the MTU on my
> route - this should not happen.
> 

       reply	other threads:[~2007-07-14 22:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8754-10286@http.bugzilla.kernel.org/>
2007-07-14 22:09 ` Andrew Morton [this message]
2007-07-15  9:29   ` [Bugme-new] [Bug 8754] New: Kernel addrconf modifies MTU of non-kernel routes Simon Arlott
2007-07-31 20:32     ` Simon Arlott

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=20070714150908.093eefdb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@kernel-bugs.osdl.org \
    --cc=bugzilla@fire.lp0.eu \
    --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).