darren.r...@oracle.com wrote:
> Author: Darren Reed <darren.r...@oracle.com>
> Repository: /hg/onnv/onnv-gate
> Latest revision: 2794a0c9cce102961d08f075ee1f569073b99786
> Total changesets: 1
> Log message:
> 6965774 bound the interface index in IP to [1,65535]
> 
> Files:
>       update: usr/src/uts/common/inet/ip/ip_if.c
>       update: usr/src/uts/common/net/if.h

I suspect this change will have two serious effects:

  - SNMP is now potentially broken.  The interface IDs cannot be reused
without an engine reboot indication, and restricting to a 16 bit range
makes reuse very much more likely than before.

  - Systems with large numbers of virtual interfaces (tunnels and PPP
links, for example) may now run out of identifiers when this wasn't
previously possible.

Was any consideration given to fixing the applications that rely on
these old BSD interfaces?  That's what we had been doing since at least
2.6 -- making the applications aware that ifIndex numbers could be
ambiguous, and using other means to verify the data.  There are numerous
examples of this work in the source base.  Let me know if you need
pointers; I can google it for you.  ;-}

In general, having aliases in the ifIndex space seen by the old BSD
interfaces is "not a problem" for most applications, because getting
routing socket messages just means that it's time to use the ioctls to
get the real current information.  The routing socket messages
themselves contain too little data to make a fully functioning program
on Solaris anyway.

Or perhaps "fixing" these old interfaces with some new mechanism?

-- 
James Carlson         42.703N 71.076W         <carls...@workingcode.com>
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org

Reply via email to