On Tue, Jul 27, 2010 at 03:22:27PM -0400, James Carlson wrote: <mucho snippage deleted!>
> The only thing that's really affected by this problem is the old BSD > routing socket interface. In the case of adding a route, you can always > use the interface name instead of the ifIndex (sockaddr_dl supports > both), and that works fine. In the case of receiving a "surprising" > truncated rtm_index value, you can do the smart thing and validate all > potentially matching interface information you've got, as dhcpagent > already does by doing a comparison under a 0xffff mask. Someone mentioned IKE earlier in this thread. IKE _only_ uses the sockaddr_dl's index to create an appropriate listener for an IPv6 link-lock address. Someone did file a bug against IKE not to use the index, but we pushed it low because in practice very few use link-local IPv6 with IKE. IKEv2, BTW, doesn't have this problem, because it's not constricted by an old OEM protocol engine that needed per-address sockets to do the right thing. FYI, Dan _______________________________________________ networking-discuss mailing list networking-discuss@opensolaris.org
