Setting the access control correctly did the trick.

I added the lines
rwcommunity public
view all-mibs included .1
access notConfigGroup "" any noauth exact all-mibs none none

to /etc/snmp/snmpd.conf and it works like a champ.  I know I should
probably make rwcommunity private, but this is just for a client demo.
 That can wait for later.  For right now, I'm just glad it works!

Thanks for your help Dave.

On Apr 6, 2005 8:51 AM, Dave Shield <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-04-06 at 13:28, John Pfaff wrote:
> > I hadn't thought of access control.
> >  I do remember that when doing an snmpwalk the
> > only things outside the system group that showed up were
> > in the host resources group
> 
> Then it's *definitely* access control settings.
> A common default config is "system+hrSystem" only
> 
> That's partly why I suggested you work through the
> checklist in the FAQ.  The fifth step in that list
> ("Is the module handler actually being called at all")
> should have revealed the problem.
> 
> Though I'll admit that the wording of that checklist
> probably needs some work to indicate what to try next.
> 
> Dave
> 
> 


-- 
John Pfaff
[EMAIL PROTECTED]


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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

Reply via email to