netdev
[Top] [All Lists]

Re: 2.6.6: IPv6 initialisation bug

To: rmk+lkml@xxxxxxxxxxxxxxxx
Subject: Re: 2.6.6: IPv6 initialisation bug
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Tue, 29 Jun 2004 02:06:27 +0900 (JST)
Cc: linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx
In-reply-to: <20040628010200.A15067@flint.arm.linux.org.uk>
Organization: USAGI Project
References: <20040628010200.A15067@flint.arm.linux.org.uk>
Sender: netdev-bounce@xxxxxxxxxxx
In article <20040628010200.A15067@xxxxxxxxxxxxxxxxxxxxxx> (at Mon, 28 Jun 2004 
01:02:01 +0100), Russell King <rmk+lkml@xxxxxxxxxxxxxxxx> says:

> Ok, I've just tried 2.6.7 out on my root-NFS'd firewall with IPv6 built
> in, and it doesn't work because of the problem I described below.
:
> What's the solution?

Bring lo up before bring others up.
What does prevent you from doing this?
(Do we need some bits to do this automatically?)


> Is there a good reason why IPv6 uses the loopback device for local
> routes?

IPv6 creates kernel routes for local addresses on lo to receive
packets for local address.

Well, someone probably wants to have
static local routes on ethX + temprary (cache) local routes on lo
(as IPv4 does; correct me if I'm wrong.)

But this won't work because IPv6 does DAD when we make some interface up.
We need lo anyway.

--yoshfuji


<Prev in Thread] Current Thread [Next in Thread>