RE: access control

> From: Masoud Fatollahy [mailto:[email protected]] 
> Sent: Tuesday, February 19, 2008 1:09 PM


>> From: [email protected]
>> [mailto:[email protected]] On 
>> Behalf Of Mike Ayers
>> Sent: den 19 februari 2008 21:37

>> > From: [email protected] 
>> > [mailto:[email protected]] On 
>> > Behalf Of Masoud Fatollahy
>> > Sent: Friday, February 15, 2008 2:14 PM

>> > Now when we are 
>> > trying to use
>> > snmpv3 context, we have problem with access control 
>> > configuration files.
>> 
>> 	What problem?  Specifics, please.
> [m] the problem is when we are using a mib-browser to fetch data from
> snmp-agent with username without any password or with defined 
> password we
> never get it work.
> and we don't really know which snmpd.conf is used, when we 
> are not doing
> make install. Or where we should put our snmpd.conf 

	A couple of issues:

	(1)  Please explain "snmpv3 context" - are you trying to use a non-default context?

	(2)  If possible, please use net-snmp's snmpgetnext command as opposed to a MIB browser or other tool when bringing up the agent.  This way you are not trying to solve browser issues by changing the agent configuration.  Also, you can post the command and its output here and we will have a good chance of spooting the problem.

> [m] we are planning to include the configuration of snmp to 
> our cli, and
> from there can generate a config file for snmp. Is it the 
> right way to go?

	Right? <shrug>  It's not a bad idea, though, and you should be able to get it to do pretty much what you want.

>> > If so, 
>> > where can we set
>> > the path to our snmpd.conf and snmp.conf.
>> 
>> 	By default, $sysconfdir ($prefix/etc), but you can use 
>> -C/-c flags
>> to access them anywhere.  Don't forget 
>> $localstatedir/snmpd.conf, which is
>> where you would put your createUser statements.
> 
> [m] we have used -C and -c flags and just put a user nothing 
> more, but we
> found out that net-snmp is using two two different files in 
> two different
> locations, one is used to define the users and another to put 
> the password
> and etc. is this currect? why?

	This is correct.  There is a read-only snmpd.conf, in which most of the configuration directives will be put, and a "persistent", or writable, snmpd.conf, in which you will put the user creation directives, which will disappear and be replaced by similar looking lines which contain the generated key.  This allows you to do keychanges, since the user is stored ina writable file.

> [m] yes, I understand, but it is very nice to have a working 
> example which
> everyone can use test their implementation of mibs and mibs 
> access, in this
> way we can understand the concept. Do have any working 
> example for this? 

	None that I know of.  I'll try to get something posted if/when I can, but my current project is trying to get a fully working config on cygwin, and I'm getting my butt handed to me in the perl department.


	HTH,

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users