Marcus Goller writes:
> which describes a similar problem, though with real devices.
> I noticed now that my interfaces are living in /dev/net. Hacking the code of
> the application, I noticed it was looking for the "main" device ("router" not
> "router[1-3]") instead of the individual instance, I modified it to directly
> open the instances, which seems to work ok. At least it starts now, but I
> still have to do further tests.
The /dev/net entries are part of Clearview's "vanity naming" feature.
Applications that support vanity-named DLPI instances need to be
modified to look in /dev/net first before looking in /dev for the DLPI
node. For most applications, it's a very simple change.
Applications that don't support this must stick with the old
(pre-Clearview) names for interfaces. (If you have something that
appears only in /dev/net, then you're probably stuck unless you can
modify the application.)
> Is there any clean way to provide interface access via DLPI? Symlinks in /dev
> would only solve the first issue, but not the second one.
Yes; update the application to support Clearview's /dev/net.
--
James Carlson, Solaris Networking <james.d.carlson at sun.com>
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
