On 11/8/07, Darren Reed <[EMAIL PROTECTED]> wrote: > Jason, > > How do you envisage arranging the back end libraries/plugins > that implement the protocols?
I'm thinking just statically compiled .o files for each protocol. I doubt there are going to be a lot of new protocols, so I'm not sure there's any benefit to providing a run-time plugin facility. > > Configuration: how do you plan to make the configuration options > persist across reboots? Still thinking about this. I'm not sure about trying to store all the information in smf or using a config file that it updates. There is some optional information that can be advertisied that would need to be manually specified by an admin (such as serial number, or asset tag), so probably need a way to specify that as well. > > Security - you should say what privileges your daemon will need, > ie does it need PRIV_NET_RAWACCESS? Yes, though I need to go through all the current privileges to make sure that aren't any others are needed. > > SNMP - you want to implement an agent. If you go this path, > will running the link discovery protocol require snmp to be > enabled? On the positive side, if you did then you could > possibly share some information (such as location) with it. I don't believe so -- the current net-snmp process (if I've understood the docs correctly) allows for a runtime .so plugin to be specified. A plugin could be written that uses the LLD client library to query the current values for a link in response to an SNMP request. The downside is that I'm not sure how I could funnel any SNMP configured values (such as location) back to the daemon. Perhaps a private API call if the plugin can obtain the information (either way, probably needs more thought). > > Darren > > _______________________________________________ networking-discuss mailing list [email protected]
