On 19 May 2010 02:22, Weiwei Zhang <[email protected]> wrote:
> In the configure file, the version is set v3.
One of the questions in the configure script is to set the *default* version.
This is what will be used when you don't specify a '-v' option (or equivalent)
to the command line tools.
It really only affects the client tools - not the agent.
> So after building and running
> the agent can accept v1/v2c/v3 messages.
As long as the access control is configured appropriately, the agent
will be able to accept v1, v2c and v3 SNMP requests, yes.
> when the agent is running, say in linux as a process snmpd, can the user
> send some message to the snmpd saying that "please just accept v1 message.."
Two options:
- edit the snmpd.conf file to have the required access control,
and then signal the agent (via HUP or versionUpdateConfig)
to re-read the config file.
This would give you full control of updating access control settings.
- SET requests on the various VACM tables
You could certainly use this to set up new SNMPv3 access config.
You *might* be able to use this approach to disable an existing
SNMPv1 or SNMPv2c access config (though you might run into
problems with "permanent" entries)
It's not possible to configure new SNMPv1 (or v2c) access config
via SET requests.
Dave
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
