| To: | rddunlap@xxxxxxxx |
|---|---|
| Subject: | Re: confuzed bit flags |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 08 May 2003 15:41:43 -0700 (PDT) |
| Cc: | linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20030508153032.06e7c98a.rddunlap@osdl.org> |
| References: | <20030508153032.06e7c98a.rddunlap@osdl.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: "Randy.Dunlap" <rddunlap@xxxxxxxx>
Date: Thu, 8 May 2003 15:30:32 -0700
I'm confused or the source code is or both.
net/ipv6/ndisc.c sets
rt->rt6i_flags = RTF_LOCAL;
Any time you see some absolutely strange handling inside of ipv6
routing, it usually indicates a place where ipv4 routing does things
one way and the ipv6 side cannot implement things in that way for one
reason or another. Yet, some ipv4'lets remain in the ipv6 code,
almost as a marker to be mindful of this difference.
This RTF_LOCAL thing is just such a case.
In many ways the ipv6 routing code is lacking in features that
ipv4 routing has. I'm in fact right now killing on of them,
rtnetlink route metrics are ignored by ipv6.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | confuzed bit flags, Randy.Dunlap |
|---|---|
| Next by Date: | Re: [PATCH 2.5.69] IPV4/6 inetsw using RCU, David S. Miller |
| Previous by Thread: | confuzed bit flags, Randy.Dunlap |
| Next by Thread: | [PATCH] switch x25_asy over to initcalls, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |