I've noticed that dlpi_walk(3dlpi) will include etherstub devices in it's iteration of network devices which seems reasonable enough. If you then try to a dlpi_info(3dlpi), it appears that the mactype is showing up as DL_ETHER. However, either a dlpi_bind or dlpi_enabmulti fail (I haven't had a chance to narrow it down yet) on etherstub devices (again seems reasonable). So how can one distinguish (programmatically) between etherstubs (as I'd prefer to just ignore them), and links (I don't need to distinguish between vnics and regular links)?
Also, I noticed that even if I create a vnic, assign it to an exclusive-ip zone, and then try a dlpi_walk within that zone, that the interface does not show up, but still shows up and can be accessed (dlpi_bind, etc.) from the global zone. Should that be the case (this is all on SXCE b105)? If one wants to see a more concrete example, this is from testing the lld (link layer discovery) prototype I've been working on -- ssh://[email protected]/hg/lld/lld-proto2 or http://src.opensolaris.org/source/xref/lld/lld-proto2/ if you just want to browse. _______________________________________________ networking-discuss mailing list [email protected]
