Freeradius-Users Digest, Vol 140, Issue 40

[firing neurons]

   I used a Tmp-String-x and that also fixed it.

   About spliting the Tmp-Integer64 for sqlcounter reply name, where would
   I split this?

   Can I just put two reply attributes in sqlcounter? May be do the math
   there?

   or updating the reply list with the two attributes, calculating their
   value using expr in unlang is the only way?


   Message: 1
   Date: Tue, 20 Dec 2016 20:32:54 -0500
   From: Alan DeKok <aland at deployingradius.com>
   To: FreeRadius users mailing list
   <freeradius-users at lists.freeradius.org>
   Subject: Re: attribute overflow from sql query in unlang
   Message-ID: <BF8722F4-167C-48A7-BD00-53C729BECA4D at deployingradius.com>
   Content-Type: text/plain; charset=us-ascii
   On Dec 20, 2016, at 7:32 PM, firing neurons <firingneurons at mail.com>
   wrote:
   > Why is their an overflow in the first case? I am using radius3
   Because Tmp-Integer is a 32-bit integer.
   > The same query is used by the relevant sqlcounter module and it works
   > as expected and doesn't overflow.
   >
   > I am trying to send CoA disconnect to the NAS after the user exhuasts
   > their data with sql and unlang logic in accounting section.
   >
   > I also tried simply using the reply attribute Mikrotik-Total-Limit
   but
   > the the NAS also expected Mikrotik-Total-Limit-Gigawords.
   >
   > The sqlcounter I made simply sent overflown value in
   > Mikrotik-Total-Limit and hence lmit of more than 4Gb couldn't be
   > enforced.
   Use a 64-bit attribute. e.g. Tmp-Integer64
   > Any way I can send the extra reply attribute from the sqlcounter?
   You will need to manually split Tmp-Integer64 into two different 32-bit
   attributes.
   Alan DeKok.
   ------------------------------