From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: davem@redhat.com
Cc: krkumar@us.ibm.com, netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [PATCH] Prefix List against 2.5.70 (re-done)
Date: Sat, 28 Jun 2003 13:06:02 +0900 (JST) [thread overview]
Message-ID: <20030628.130602.63704890.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20030627.144752.78715628.davem@redhat.com>
In article <20030627.144752.78715628.davem@redhat.com> (at Fri, 27 Jun 2003 14:47:52 -0700 (PDT)), "David S. Miller" <davem@redhat.com> says:
> From: Krishna Kumar <krkumar@us.ibm.com>
> Date: Fri, 27 Jun 2003 08:45:19 -0700
>
> rtnetlink_rcv_msg() calls dumpit() (via netlink_dump_start) only
> for those messages for which the last two bits are binary '10'. So
> I had to use these values. All the other *GET* macros use the same
> semantics.
>
> Ok, please retransmit your two patches (2.4.x and 2.5.x) to me
> under seperate cover. I don't keep a copy around of patches
> I've decided not to apply.
Well...
1. is it okay to have another hook for garbbig prefix list?
Userspace application can get such information via
- routing table
- interface flag
2. is the "managed" flags etc, which is per interface variable,
really NEWROUTE information?
It is NOT L2 thing, but it is per-link information.
I think it is NEWLINK thing.
What I'm thinking is:
- fix "ADDRCONF" flag in route information
- manage / other flags via NEWLINK message
(- No new interface to get prefix itself.)
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2003-06-28 4:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 20:53 [PATCH] Prefix List against 2.5.70 (re-done) Krishna Kumar
2003-06-21 14:36 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-25 17:02 ` Krishna Kumar
2003-06-26 6:42 ` David S. Miller
2003-06-26 16:32 ` Krishna Kumar
2003-06-27 6:07 ` David S. Miller
2003-06-27 15:45 ` Krishna Kumar
2003-06-27 21:47 ` David S. Miller
2003-06-28 4:06 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2003-06-30 18:54 ` Krishna Kumar
2003-07-02 0:18 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 22:16 ` Krishna Kumar
2003-06-26 22:40 ` [PATCH] Prefix List against 2.4.21 Krishna Kumar
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=20030628.130602.63704890.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=krkumar@us.ibm.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.