26 Jun
2015
26 Jun
'15
1:24 p.m.
On Jun 26, 2015, at 12:08 PM, Jake He <jake.he@gmail.com> wrote:
Sorry, I make a mistake. I am using Mikrotik-Total-Limit not Mikrotik-Recv-Limit.
Describing the problem correctly helps.
This is the debug for my perl script. (1) check_usage: &reply:Session-Timeout = $RAD_REPLY{'Session-Timeout'} -> '10800' (1) check_usage: &reply:Mikrotik-Total-Limit-Gigawords = $RAD_REPLY{'Mikrotik-Total-Limit-Gigawords'} -> ‘232830643'
So it’s getting set. That’s nice.
This means that Mikrotik-Total-Limit is set right?
Yes. Then go read the debug log to see when it’s being set, and when your perl script is being executed. There’s no magic here. Just read the debug output to see what it’s doing. Alan DeKok.