Paul Jakma writes:
> A better way to get an idea of link-state is to examine the interface
> flags: The IFF_RUNNING flag should (broadly) reflect link-state, for
> drivers that report link-state via DLPI (in theory that should be all
> NIC drivers..).
That's at the IP level. You can do it in a stable way across many
different drivers at the lower level via the committed (and
documented; see the ieee802.3(5) man page) 'link_up' kstat. See the
Kstat(3PERL) man page for details on the Perl interfaces for kstats.
As for ndd, it's a hack. Stay as far from it as you can manage. Note
that there's no documentation for the actual ndd values, and the man
page for ndd(1M) says:
NOTES
The parameters supported by each driver may change from
release to release. Like programs that read /dev/kmem, user
programs or shell scripts that execute ndd should be
prepared for parameter names to change.
In other words, "you're on your own."
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 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
networking-discuss@opensolaris.org
