Peter Memishian writes:
> 
>  > > There are more offenses here than that.  There's no way that
>  > > IFF_POINTOPOINT can be in ipif_flags.  It has to be an ill_flags or
>  > > (better still) phyint_flags value because it's a property of the
>  > > underlying interface itself, not a per-logical-interface matter.
>  > 
>  > Yes, if we change it so IFF_POINTOPOINT, IFF_BROADCAST are only set 
>  > based on the dl_info_ack then it makes sense to move those flags from 
>  > the ipif to the ill.
> 
> Why not the phyint?  BTW, this chane will allow for minor simplifications
> to a number of functions -- e.g., with Clearview IPMP, the kernel has to
> iterate over all of the ipifs on an ill to see if IPIF_POINTOPOINT is set
> (and fail the operation if so) when adding an ill to a group.  I look
> forward to just checking a single flag :-)

I don't see how the same underlying interface could be broadcast-type
as far as IPv4 is concerned, but point-to-point for IPv6, or
vice-versa, so putting it on the phyint makes more sense to me.

(I was just pointing out that having it on the ipif doesn't make sense
-- except perhaps in terms of the old hack.)

-- 
James Carlson, Solaris Networking              <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to