Re: How do I find out the list of active network objects?

[Steve Whitehouse <steve@gw.chygwyn.com>]

> 
> >> There's no NCP support (yet ;-)), but if you have any other suggestions
> >> on how I can find out this kind of information, that would be useful too
> >> ...
> >>
> >From the actual applications themselves, you can use getsockopt() to get
> >information on the state of the sockets. You can also use getsockname()
> >to get the local socket address, and getpeername() to get the remote
> >address.
> 
> Is there a way (without using /proc/net/decnet) to 'step through the
> list' of active DECnet sockets and query the object name that is being
> used? something like a 'getnextactivednsocket()' call ?
> 
No. If there was, it should probably be done by extending the rtnetlink
code I think. That provides an extensible, protocol independant
interface to various parts of the network code.

> In the meantime, I'll take a look at the 'netstat' code to find out how
> to add a new address family ... it does Netware IPX already, so I don't
> see why we shouldn't just add DECnet to the options on the 'netstat -A
> <family>' command.
>
Thats in the nettools package as I remember... there is already an
option to support DECnet in the hostname command, so its just a
question of a few #ifdefs and something to parse /proc/net/decnet.
Of course this maybe eaiser said than done, since its a while since
I've looked at the code....
The config and Makefile options required to make the package
use libdnet are already in there,

Steve.

-----------------------------------------------------------------------------
To unsubscribe from this list, send a mail to majordomo@dreamtime.org
containing the line "unsubscribe linux-decnet"
-----------------------------------------------------------------------------