[AGENT++] Manager can access MIB without users are defined in Vacm
Frank Fock
fock at agentpp.com
Thu Nov 9 11:02:15 CET 2006
Hi Dario,
If you want to control SNMPv1/v2c communities through the
VACM, you need also to configure the SNMP-COMMUNITY-MIB
appropriately to map the communities to the SNMPv3 user
(security) names.
Otherwise, AGENT++ uses the community as security name
which might have caused the problems you described.
Best regards,
Frank
Dario maljur wrote:
> Hi, I have this situation:
>
> vacm->addNewGroup(secModel,OctetStr(securityName.c_str()),
> OctetStr(groupName.c_str()),storageType_volatile);
>
>
>
> and after that I define views (r/w/n) for that group.
>
>
>
> No users where define anywhere.
>
>
>
> But I can still use manager to access OIDs. Just for using securityName
> defined in addNewGroup. How come?
>
> Manager is using securityName as read community, _and_ read community. I
> can't change that.
>
> It seems that defining users in vacm does not help at all.
>
> How do I change write community in manager to differs from read comm?
>
> I'm allso using v1 of protocol and groups are defined with all 3
> sec_models.
>
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp
--
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com
More information about the AGENTPP
mailing list