From: Bernhard Schmidt <berni@birkenwald.de>
To: Jarek Poplawski <jarkao2@o2.pl>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [IPv6] PROBLEM? Network unreachable despite correct route
Date: Thu, 11 Jan 2007 14:08:16 +0100 [thread overview]
Message-ID: <45A636C0.6050507@birkenwald.de> (raw)
In-Reply-To: <20070111125343.GB3561@ff.dom.local>
Jarek Poplawski wrote:
>> ip -6 route:
>> 2001:4ca0:0:f000::/64 dev eth0 proto kernel metric 256 expires 86322sec mtu 1500 advmss 1440 fragtimeout 4294967295
>> fe80::/64 dev eth0 metric 256 expires 21225804sec mtu 1500 advmss 1440 fragtimeout 4294967295
>> ff00::/8 dev eth0 metric 256 expires 21225804sec mtu 1500 advmss 1440 fragtimeout 4294967295
>> default via fe80::2d0:4ff:fe12:2400 dev eth0 proto kernel metric 1024 expires 1717sec mtu 1500 advmss 1440 fragtimeout 64
>> unreachable default dev lo proto none metric -1 error -101 fragtimeout 255
> Did you analyze this dev lo warning?
That one is default. Recent kernels (since 2.6.12 or so, I think when
the default on-link assumption was killed) have a default route pointing
to "unreachable default lo" on bootup. Routes learned from RA or added
statically are installed with a better metric and are preferred that way.
I think the use is to have a Network unreachable returned immediately if
no IPv6 router is present.
Regards,
Bernhard
next prev parent reply other threads:[~2007-01-11 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 19:36 [IPv6] PROBLEM? Network unreachable despite correct route Bernhard Schmidt
2007-01-10 0:23 ` Bernhard Schmidt
2007-01-11 12:53 ` Jarek Poplawski
2007-01-11 13:08 ` Bernhard Schmidt [this message]
2007-01-17 8:14 ` Jarek Poplawski
2007-01-17 8:46 ` Jarek Poplawski
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=45A636C0.6050507@birkenwald.de \
--to=berni@birkenwald.de \
--cc=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--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).