I'm on the fence about using Counter64 based objects (which won't work with V1) vs separate high/low objects. But working code trumps nit-picking, so +1 from me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm on the fence about using Counter64 based objects (which won't work with V1) vs separate high/low objects. But working code trumps nit-picking, so +1 from me.
high/low objects are such a pain for the manager; why cater to SNMPv1 in 2015?
Here is a minor update of the patch, to fix the reference to the HCNUM definitions.
Now applied for 5-7-patches and master.