| To: | yoshfuji@xxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: 2.6.8.1 IPv6 Routing Problem |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 21 Sep 2004 19:57:52 -0700 |
| Cc: | pekkas@xxxxxxxxxx, laforge@xxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi-users@xxxxxxxxxxxxxx |
| In-reply-to: | <20040920.152012.114156249.yoshfuji@linux-ipv6.org> |
| References: | <20040919074605.GJ6005@sunbeam.de.gnumonks.org> <Pine.LNX.4.44.0409200806460.22679-100000@netcore.fi> <20040920.152012.114156249.yoshfuji@linux-ipv6.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
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? It is kind of silly to force this device up ordering upon people anyways. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Improve behaviour of Netlink Sockets, jamal |
|---|---|
| Next by Date: | Re: [PATCH] Improve behaviour of Netlink Sockets, David S. Miller |
| Previous by Thread: | Re: 2.6.8.1 IPv6 Routing Problem, YOSHIFUJI Hideaki / 吉藤英明 |
| Next by Thread: | Re: 2.6.8.1 IPv6 Routing Problem, YOSHIFUJI Hideaki / 吉藤英明 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |