From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: yoshfuji@linux-ipv6.org, linkfanel@yahoo.fr,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8349] New: Manually set IPv6 default route ignored
Date: Tue, 17 Apr 2007 20:00:38 -0700 [thread overview]
Message-ID: <20070417200038.b85cdcb5.akpm@linux-foundation.org> (raw)
In-Reply-To: <200704180145.l3I1jCOo025906@fire-2.osdl.org>
On Tue, 17 Apr 2007 18:45:12 -0700 bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8349
>
> Summary: Manually set IPv6 default route ignored
> Kernel Version: 2.6.20.7
> Status: NEW
> Severity: normal
> Owner: yoshfuji@linux-ipv6.org
> Submitter: linkfanel@yahoo.fr
>
>
> Most recent kernel where this bug did *NOT* occur: 2.6.19.5
> Distribution: Debian sid
> Hardware Environment: x86 (Pentium 4/MMX)
> Software Environment: iproute2-ss060323, ifupdown 0.6.8
>
> Problem Description:
> Default routes added to the IPv6 routing table, which are not coming from
> autoconfiguration, seem to be ignored. Subsequently, IPv6 routing is disrupted,
> and for instance calls to connect() fail with an ENETUNREACH error.
>
> Steps to reproduce:
> 0. Find an IPv6-enabled box on an IPv6-free network. In the absence of any other
> configuration, the routing table contains the single line:
> fe80::/64 dev eth0 ...
> 1. Add a default route:
> ip -6 ro add default via fe80::1 dev eth0
> 2. Try to do IPv6, for instance:
> # ping6 2001:4978:1:110:0:ac:ce55:1b1e
> connect: Network is unreachable
> (returns instantly, no packet is sent)
>
> This bug is present in the last stable 2.6.20.7 kernel, and in 2.6.21-rc7. I
> actually came across this bug on a server on a network where IPv6 is routed and
> advertised, but with autoconfiguration disabled on this server. It *seems* to me
> that if the interface is brought up with accept_ra enabled, default routes,
> including the one got from RA and ones input by hand later will work, whereas if
> it is brought up with accept_ra disabled (or no RA is received), the problem
> will occur. Note that routes with a non-null prefix length, such as 3 or 1, work
> fine.
parent reply other threads:[~2007-04-18 3:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200704180145.l3I1jCOo025906@fire-2.osdl.org>]
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=20070417200038.b85cdcb5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linkfanel@yahoo.fr \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).