On Wed, 2008-10-29 at 17:01 +0800, Yifan Xu wrote: > Sebastien Roy wrote: > > Pardon my interjection, but what does this have to do with router > > advertisements (Jim's original question)? You're describing the need to > > do proxy ND (static neighbor cache entries), which seems unrelated. > > > > Sorry I didn't state it clearly. As I understand, to send > RA messages, in.ndpd requires the source IP address to be > applied on the interface. While in non-accept mode and > non-owner mode this is not true, the IP won't be configured > on the interface. Thus the vrrpd needs to forge and send > RA messages. Please correct me if I were wrong.
I don't see anything above describing why vrrpd needs to be the thing that forges these RA messages. Any adequately privileged application is able to forge RA messages, and in.ndpd is well-positioned to do that since it consumes all of the required RA configuration that is contained in /etc/inet/ndpd.conf. In order for vrrpd to do anything useful, it would need to parse /etc/inet/ndpd.conf (just like in.ndpd), reply to router solicitations (just like in.ndpd), and all of that would be a lot of complex and duplicate code. I think more detail is needed in the design document describing exactly how the RS/RA handling actually works, along with a description of why the more natural alternate design choice of having in.ndpd do neighbor discovery wasn't chosen. -Seb _______________________________________________ networking-discuss mailing list [email protected]
