2009/3/2 Bell, Adam <[email protected]>:
> I have a working implementation that fixes the multi-index fixed length
> OCTET STRING decoding.
Could you please post a diff of your changes, rather than the whole mib.c file.
It's very difficult to work out exactly what you are proposing, since I'm not
sure what your starting point was.
> 1. in mib.c - minor algorithm mods (attached), if the index has only 1
> field, then it works as it did before and takes the entire OID.
How does it cope with a multi-indexed table, where the last
index is IMPLIED?
> 2. In the table helper creation, I set the each index variable with the
> expected OID length, that info is used in the mib.c fix.
More generally, how does it distinguish between the following two cases:
aTable ....
INDEX { IMPLIED varString }
and
bTable ....
INDEX { fixedString }
?
Dave
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
