On 2017/07/27 14:01, Gerhard Roth wrote:
> could you please try the updated patch below. I guess the non-repeater
> parameters was completely ignored before.
Nearly there :)
> - msg->sm_maxrepetitions);
> + (msg->sm_i
On Thu, 27 Jul 2017 12:46:23 +0100 Stuart Henderson
wrote:
> On 2017/07/27 10:58, Gerhard Roth wrote:
> > Hi,
> >
> > snmpd uses the same storage for sm_error and sm_nonrepeaters. Same applies
> > to sm_errorindex and sm_maxrepetitions. If we produce a response PDU to
> > a getbulk request, sm_e
On 2017/07/27 10:58, Gerhard Roth wrote:
> Hi,
>
> snmpd uses the same storage for sm_error and sm_nonrepeaters. Same applies
> to sm_errorindex and sm_maxrepetitions. If we produce a response PDU to
> a getbulk request, sm_error will carry the number of non-repeaters from
> the request and sm_err
Hi,
snmpd uses the same storage for sm_error and sm_nonrepeaters. Same applies
to sm_errorindex and sm_maxrepetitions. If we produce a response PDU to
a getbulk request, sm_error will carry the number of non-repeaters from
the request and sm_errorindex the max. number of repetitions. This is
wrong
