Proxy forwarder configuration help

[Jochen Katz]

Hi,

> 20010419.09:35:10: 21351: (6)DEBUG  : ProxyForwarder: matching
> (MPModel)(match)(secModel)(match)(secLevel)(match): (1), (1), (2),
> (1), (1), (1).
  ^^^                                                           ^^^
the proxy entry is for v1, but the request uses v2c, so the proxy entry
does not match. Either use snmpv1 or modify the proxy entry or (better)
add an additional entry for v2c.

> Do I need to add any Vacm entries for this to work ? The only group
> that I created is group "v1v2group" (like in example atm_mib)

If you copied the calls to create access entries and views, this is
sufficient.

> Do I need to add views to the new community that I defined for the
> proxy ? if so what is the format to do it ?

If you want to be able to access the proxy with v1/v2c and community
new_com you will have to add an entry to the SecurityToGroupTable (maybe
the method should be renamed to addNewGroupEntry for the next release):
        vacm->addNewGroup(SecurityModel_v2, "new_com", 
                         "v1v2group", storageType_nonVolatile);
        vacm->addNewGroup(SecurityModel_v1, "new_com", 
                         "v1v2group", storageType_nonVolatile);

> Is there a way to use proxy to forward requests based on oid value ?
> so for example if the object oid is not part of my private tree oids
> to forward the request to another agent.

This is possible for v1/v2c with the MibProxy class if only single
objects or complete sub trees need to be forwarded:
 * The MibProxy class represents a sub-tree within an agents MIB whose
 * nodes and their values are proxied (forwarded) from another 
 * SNMPv1/v2c agent.

Best regards,
  Jochen