Dave,
I have already tested how you suggested and it worked well too.
But i thought that i should not use "view" directive in the SNMPv1/v2c
agent.
Thats why i asked some more questions on the same.
Now i am clear from your recent response.
Thanks a ton !
-Pachi-
On 6/2/08, Dave Shield <[EMAIL PROTECTED]> wrote:
>
> 2008/6/2 Pachiappan D <[EMAIL PROTECTED]>:
>
> > View directive comes under SNMPV3.
>
>
> No.
> The view-based access control model was introduced
> as part of the SNMPv3 framework, but can be (and is)
> applied to all versions of the protocol.
>
>
>
> > With alone SNMPv1/v2c , rocommunity directive is the only
> > choice to restrict access for a subtree as below,
>
>
> No - it is not.
> That is the simplest approach, but it is also possible to use
> more complex views - either using "rocommunity ... -v {view}"
> or the full com2sec/group/view/access approach.
>
>
>
> > In SNMPv1/v2c , I want to achieve like
> > rocommunity cname default <subtree1> <subtree2>..
>
>
> And I have told you how to do that.
>
> > ( without using view directive )
>
> Then you're stuffed. The *only* way you can
> do what you are asking for is to use views.
>
>
> > Is the above possible ?
>
> Yes.
>
>
> > If yes , please pave me a way to do this.
>
>
> I have already given you a way to do this.
> If you're not prepared to follow my advice,
> then that is not my problem.
>
> Have you actually *tried* what I suggested?
> If not, why not?
>
>
> Dave
>
-------------------------------------------------------------------------
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-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
