Check_item still wraps at 4gb
Good Day. Hopying I can get some help. I have been trying for years now too simply cap users based on data transferred above 4gb. It has only been now that I discovered , where the problem lies. I can log data over 4gb no issue, nas sends gigawords to radius and gets inserted into db no probs. However, my data counter fails to authenticate customers properly is any accounts are set to above 4Gb. And I found why. It seems that the "check_item" still wraps at 4gb! How can I solve this? Regards
Marcel Grandemange wrote:
I have been trying for years now too simply cap users based on data transferred above 4gb.
It has only been now that I discovered , where the problem lies.
RADIUS supports 32-bit integers. Not 64-bit integers.
How can I solve this?
Patch the code to use 64-bit counters. Alan DeKok.
Marcel Grandemange wrote: I have been trying for years now too simply cap users based on data transferred above 4gb.
It has only been now that I discovered , where the problem lies.
RADIUS supports 32-bit integers. Not 64-bit integers.
How can I solve this?
Patch the code to use 64-bit counters. I know it is expected to be a programmer to use open source software, but unfortunately I am not one. :/ I do find it strange that only parts of freeradius seems compatible with the 4gb figures.
I have since employed a work around that now uses gigs as check item and not bytes, however this blows my reply item out the water. Thank You for info, I am at least glad I have finally found the problem. Any advise on what ISP's use as a radius solution?
Alan DeKok.
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4515 (20091016) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
I have been trying for years now too simply cap users based on data transferred above 4gb.
It has only been now that I discovered , where the problem lies.
RADIUS supports 32-bit integers. Not 64-bit integers.
How can I solve this?
Patch the code to use 64-bit counters. I know it is expected to be a programmer to use open source software, but unfortunately I am not one. :/ I do find it strange that only parts of freeradius seems compatible with the 4gb figures.
I have since employed a work around that now uses gigs as check item and not bytes, however this blows my reply item out the water.
Ok, so counter module can't handle returning two attributes in the reply (gigawords and octets). But perl can. Counting can be done by the sql module (to avoid overhead for connecting to the database in perl) and result (counted gigawords and octets) passed to perl for some very basic calculations. You will need more knowledge to construct counter queries oin sql than for programming in perl.
Any advise on what ISP's use as a radius solution?
Freeradius. Ivan Kalik Kalik Informatika ISP
participants (3)
-
Alan DeKok -
Ivan Kalik -
Marcel Grandemange