On Wed, Feb 15, 2006 at 05:16:28PM +0000, Jasper Wallace wrote:
The patch is attached. I had problems with the mib[1] - it uses PhysAddress as the index to a couple of the tables, but since PhysAddress has no length associated with it the code generated by smidump breaks.
I worked around it by replacing PhysAddress with MacAddress from SNMPv2-TC, but if there's a way of saying to smidump that in this mib PhysAddresses are 6 bytes, that would be better.
Thanks for the patch. I would be interested to know why the usage of PhysAddress causes problems. The code generator should be able to deal with variable-length octet strings.
The code will leave some memory unfreed on exit - since wireless clients can come and go the number of entrys in the clients table will change, so keeping a simple mapping of table[i] <-> stats[i] for the monitor mode won't work, so i used a GHashTable instead.
Yes, scli currently lacks a cleanup hook for such things.
Early on i tried writing generic table display code, since the _attr[] stuff tells you all you need to know in order to render a table, but since the table structs have all the column names as variables you have to write table specific code.
By looking at the link, a nasty questions comes up:
Is it legal to include the MIB stubs in the scli distribution?
If I take the license agreement literally, then probably the answer is no. We seem to have this issue in general with vendor MIB modules and I am not sure how to deal with it. Any ideas/comments?
/js