netdev
[Top] [All Lists]

Re: [PATCH] Prefix List patch against 2.5.70

To: krkumar@xxxxxxxxxx
Subject: Re: [PATCH] Prefix List patch against 2.5.70
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Wed, 18 Jun 2003 05:59:59 +0900 (JST)
Cc: davem@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <3EEF7E09.8080608@us.ibm.com>
Organization: USAGI Project
References: <20030531.110249.12960077.yoshfuji@linux-ipv6.org> <20030530.233257.21920899.davem@redhat.com> <3EEF7E09.8080608@us.ibm.com>
Sender: netdev-bounce@xxxxxxxxxxx
In article <3EEF7E09.8080608@xxxxxxxxxx> (at Tue, 17 Jun 2003 13:46:01 -0700), 
Krishna Kumar <krkumar@xxxxxxxxxx> says:

> I have a question about the following, which seems to be the
> approach both of you prefer. I thought we need a new routing
> message type called RTM_GETPLIST which will return full prefix
> list. If you use RTA_RA6INFO, then should that trigger only
> when the prefix list has changed (add or delete) ? Should I
> have both interfaces, one for returning entire list (RTM) and
> one for changes in prefix list (RTA) ?
> 
> Please let me know if my understanding is correct.

Well, I think the problem is to set RTF_ADDRCONF flag to all prefix routes.
I beleive this should be for autoconf (RA) routes only as comments says;
dad_starts and multicast add routes with such flag, but this should be wrong.
After we fix this, we can get prefix information filtering routes by 
RTF_ADDRCONF flag; of course, we can get the routes using RTM_GETROUTE.

-- 
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@xxxxxxxxxxxxxx>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF  80D8 4807 F894 E062 0EEA

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