bulkwalk can omit OIDs that snmpwalk does show

[jjdmol]

Gosnmp's walker does not show as many OIDs as snmpwalk does in one of our devices. For example:

~/gosnmp$ snmpwalk -c public -v 2c 10.99.250.70 1.3.6.1.4.1.5961.5.6.2.1.2
iso.3.6.1.4.1.5961.5.6.2.1.2.0 = INTEGER: 1
iso.3.6.1.4.1.5961.5.6.2.1.2.1 = INTEGER: 2
iso.3.6.1.4.1.5961.5.6.2.1.2.2 = INTEGER: 3
iso.3.6.1.4.1.5961.5.6.2.1.2.3 = INTEGER: 4
~/gosnmp$ go run examples/walkexample/main.go 10.99.250.70 1.3.6.1.4.1.5961.5.6.2.1.2
.1.3.6.1.4.1.5961.5.6.2.1.2.0 = TYPE 2: 1
.1.3.6.1.4.1.5961.5.6.2.1.2.1 = TYPE 2: 2
.1.3.6.1.4.1.5961.5.6.2.1.2.2 = TYPE 2: 3

Yet gosnmp is able to retrieve the specific instances just fine, if explicitly asked to do so:

~/gosnmp$ go run examples/walkexample/main.go 10.99.250.70 1.3.6.1.4.1.5961.5.6.2.1.2.3
.1.3.6.1.4.1.5961.5.6.2.1.2.3.0 = TYPE 2: 4

Attached is the output of the same commands with debugging enabled:

• snmpwalk-debug-output.txt
• gosnmp-walk-debug-output.txt for the bulkwalk, with logging enabled
• gosnmp-get-debug-output.txt for getting the specific instance, with logging enabled

[TimRots]

Thanks for reporting.

After a look at the walk code I feel that line 157 in walk.go is responsible for this issue

oid = response.Variables[len(response.Variables)-1].Name

and needs to become

oid = response.Variables[len(response.Variables)].Name

Would it be possible for you to run a quick test with above modification ? I currently don't have the means available to test extensively.