From: "David S. Miller" <davem@redhat.com>
To: rddunlap@osdl.org
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: confuzed bit flags
Date: Thu, 08 May 2003 15:41:43 -0700 (PDT) [thread overview]
Message-ID: <20030508.154143.88024940.davem@redhat.com> (raw)
In-Reply-To: <20030508153032.06e7c98a.rddunlap@osdl.org>
From: "Randy.Dunlap" <rddunlap@osdl.org>
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 parent reply other threads:[~2003-05-08 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 22:30 confuzed bit flags Randy.Dunlap
2003-05-08 22:41 ` David S. Miller [this message]
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=20030508.154143.88024940.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.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).