netdev
[Top] [All Lists]

Re: 2.6.8.1 IPv6 Routing Problem

To: davem@xxxxxxxxxxxxx
Subject: Re: 2.6.8.1 IPv6 Routing Problem
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Wed, 22 Sep 2004 12:06:30 +0900 (JST)
Cc: pekkas@xxxxxxxxxx, laforge@xxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi-users@xxxxxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx
In-reply-to: <20040921195752.015e3d1d.davem@davemloft.net>
Organization: USAGI Project
References: <Pine.LNX.4.44.0409200806460.22679-100000@netcore.fi> <20040920.152012.114156249.yoshfuji@linux-ipv6.org> <20040921195752.015e3d1d.davem@davemloft.net>
Sender: netdev-bounce@xxxxxxxxxxx
In article <20040921195752.015e3d1d.davem@xxxxxxxxxxxxx> (at Tue, 21 Sep 2004 
19:57:52 -0700), "David S. Miller" <davem@xxxxxxxxxxxxx> says:

> On Mon, 20 Sep 2004 15:20:12 +0900 (JST)
> YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> wrote:
> 
> > This behavior lives for years (AFAIK),
> > and we haven't got so many reports 
> > because people usually bring loopback device first.
> > 
> > I think the following message will help people, anyway.
> 
> If ipv6 has a dependency upon this, why doesn't it just
> bring the device up itself at this moment if necessary?

Okay, I'll make a patch for this.

--yoshfuji

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