Re: SNMPD ended up in an endless loop processing GETNEXT

[Raymond P. <ray...@in...>]

The problem was indeed with the 2 error messages, init_vacm_vars() was not
called in init_mib_modules; probably to reduce the size of the customized
agent.
Including init_vacm_vars() in init_mib_modules() and setting up the correct
rocommunity and rwcommunity name works.

Thanks Dave.

My next task now is to setup v3 user authentication.

   Encryption support not enabled.

Should I start worrying about the above message now?

Raymond Pau

----- Original Message -----
From: "Dave Shield" <D.T...@cs...>
To: <ray...@in...>
Cc: <net...@li...>
Sent: Tuesday, July 17, 2007 4:42 PM
Subject: Re: SNMPD ended up in an endless loop processing GETNEXT


> On 17/07/07, Raymond Pau <ray...@in...> wrote:
>> rwcommunity  p
>> rocommunity  p
>
> Please do not include both "rwcommunity" and "rocommunity" directives
> with the same community string.
>
> Granting "read-write" access includes read, so granting "read-only" as
> well is unncessary.  And it's unclear whether this allows SET requests
> or not.
>
> If you want to allow SET requests, then use
>
>     rwcommunity    p
>
> If you do not want to allow SET requests, then use
>
>     rocommunity    p
>
> But don't use both.
>
>
>
>
>> # ./snmpd -f -Le
>> Encryption support not enabled.
>> /usr/local/etc/snmp/snmpd.conf: line 1: Warning: Unknown token:
>> rwcommunity.
>> /usr/local/etc/snmp/snmpd.conf: line 2: Warning: Unknown token:
>> rocommunity.
>
> That's why you can't query the agent.
> It's not picking up the access control settings.
>
> How was this agent originally compiled?
> It looks as if it was stripped down to less than the bare minimum.
> I'd say that it's probably not useable in this configuration.
> I suspect you will need to re-compile it.
>
> Dave
>
>