[squid-users] Bug in the squid snmp

[Amos Jeffries]

On 6/09/2015 11:34 p.m., Amos Jeffries wrote:
> On 6/09/2015 8:20 p.m., FredT wrote:
>> Hi Amos,
>>
>> So what ?
>> I noticed it's a  32 bit integer <https://en.wikipedia.org/wiki/32-bit>  
>> with a "4,294,967,295" limit in unsigned but it cannot be an excuse to
>> provide a wrong number...
>> The squidclient displays the right value but as the same value from the snmp
>> is an unsigned so here it's allowed to truncate the value ? does not make
>> sense...
> 
> The mgr report is not limited to 32-bit gauge semantics. So its showing
> the true underlying value.
> 
>>
>> What's the right way: respect the unsigned int limit or display the right
>> value ?
>> From my side I suppose the right way is to display the right value, so I
>> think you should fix the snmp with the right types to provide the reality 
>>
>> Does it make sense for you too ?


The spec is:
"
The Gauge32 type represents a non-negative integer, which may increase
or decrease, but shall never exceed a maximum value. The maximum value
can not be greater than 2^32-1 (4294967295 decimal). The value of a
Gauge has its maximum value whenever the information being modeled is
greater or equal to that maximum value; if the information being modeled
subsequently decreases below the maximum value, the Gauge also decreases.
"


I have just looked it up again and re-configrmed there seems to still be
no usable Gauge64 or equivalent type in SNMP.


Amos