#517 endOfMibView RFC compliance

[Erik Änggĺrd]

If you set a limited view and then do an snmpwalk the
last entry (i.e. the endOfMibView) of the reply will
sometimes have an object ID that is outside the view.
E.g. if you set a view that only contains
.1.3.6.1.2.1.1.6.0 and then do an snmpwalk the
endOfMibView reply will get the object ID
.1.3.6.1.2.1.7.5.

RFC3416 (section 4.2.2.) says:
(2) If the requested variable binding's name
does not
lexicographically precede the name of any
variable
accessible by this request, i.e., there is
no lexicographic
successor, then the corresponding variable
binding produced
in the Response-PDU has its value field set to
"endOfMibView", and its name field set to
the variable
binding's name in the request.

So the net-snmp behaviour is not always compliant with
this. This patch fixes this (although I'm not sure the
method used in this patch is the best method).

[Erik Änggĺrd]

endOfMibView RFC compliance

[Thomas Anders]

Logged In: YES
user_id=848638

Is this problem still happening with latest CVS (5.3.dev)?

[Robert Story]

Logged In: YES
user_id=76148

I'm pretty sure it is.. bumping the priority and hoping Wes
will tackle this one..

[Dave Shield]

Logged In: YES
user_id=88893

Seems to work OK. Applied to main CVS branch.
We should probably consider back-porting this
to earlier lines.

[Wes Hardaker]

Logged In: YES
user_id=76242

Applied to the 5.2 and 5.3 branches too. Thanks!