using freeradius 1.1.7 and use variabel Gigawords, still same problem

modcall: leaving group session (returns ok) for request 0
radius_xlat:  '/usr/local/bin/rmauth.pl ADMIN 00:16:17:52:8F:94 172.1.1.248'
Exec-Program: /usr/local/bin/rmauth.pl ADMIN 00:16:17:52:8F:94 172.1.1.248
Exec-Program output: Mikrotik-Xmit-Limit-Gigawords = 7890652485, Mikrotik-Recv-Limit-Gigawords=5599872474, Ascend-Data-Rate=98304, Ascend-Xmit-Rate=262144, Exec-Program-Wait: value-pairs: Mikrotik-Xmit-Limit-Gigawords =* 7890652485*, Mikrotik-Recv-Limit-Gigawords=*5599872474*, Ascend-Data-Rate=98304, Ascend-Xmit-Rate=262144,
Exec-Program: returned: 0
Sending Access-Accept of id 14 to 10.128.3.3 port 1027
       Mikrotik-Xmit-Limit-Gigawords = *3595685189*
       Mikrotik-Recv-Limit-Gigawords = *1304905178*
       Ascend-Data-Rate = 98304
       Ascend-Xmit-Rate = 262144

[EMAIL PROTECTED] wrote:
Wrong. Learn about binary numbers. And read Mikrotik documentation. You
will find out that there are attributes containg something called
"gigaword". You will also find out that there is also no need for
shoehorns, hammer and chisel, rewriting operating systems and such in an
attempt to squeeze something into a space it can't fit.

Ivan Kalik
Kalik Informatika ISP


Dana 11/10/2007, "Kris" <[EMAIL PROTECTED]> piše:

it is not mikrotik issue cause freeradius send incorret values , that
mean i must configure freeradius to support more than 32-bit right ?

[EMAIL PROTECTED] wrote:
how much are 32-bit number ?

2 times 2 times 2 times etc. 32 times. If that's the numer of bytes than
4GB.


any possible way to configure it larger than 32-bit number ?

Ask Mikrotik (it's a vendor attribute). Or use "ordinary" input and
output octets.

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html



-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to