🚀 go-pugleaf

I have been able to get RFC 1158 to work correctly with the CMU snmp
implementation, except for OIDs that need "parameters" (probably not the 
right term) By that I mean, say for the AT table, the parameter would be the ip
address of the address resolution table entry you want.  Those OIDs
that need parameters do not work with our CMU snmpget/snmptest.

Examining the RFC itself, I cannot find any description of the need
for the parameter.  That is, examining the (SMI) entry
of the AT table OIDs in RFC 1158, one does not find a formal definition
of the need of a parameter.  The need for the parameter is defined in
a different RFC (1098,  which, of course, CMU never sees.)

So how does CMU know that an atTable mib needs a parameter?  When I try
to give it one, it gives a seg fault (in proc parse_subtree()) .

Does anyone out there know of a way to solve this problem?

Dan Lambright
dan@gordian.com