Sorry, I make a mistake. I am using Mikrotik-Total-Limit not Mikrotik-Recv-Limit. 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' I tested by this code update control{ Total-Limit := &reply:Mikrotik-Total-Limit Total-Limit-G := &reply:Mikrotik-Total-Limit-Gigawords } debug: (1) update control { (1) Total-Limit := &Mikrotik-Total-Limit -> 2514812512 (1) Total-Limit-G := &Mikrotik-Total-Limit-Gigawords -> 232830643 (1) } # update control = noop This means that Mikrotik-Total-Limit is set right? On 26 June 2015 at 23:55, Alan DeKok <aland@deployingradius.com> wrote:
On Jun 25, 2015, at 11:38 PM, Jake He <jake.he@gmail.com> wrote:
Here is the debug output:
Why is it double spaced? You should be able to cut & paste plain text, or add it as a text attachment.
And if you read the debug messages you posted to the list, you'll see that Mikrotik-Recv-Limit doesn't show up *anywhere*. So it's not being sent in *any* packet.
You said it comes from a Perl script. But the debug output clearly shows that the Perl script never sets that attribute.
Fix your Perl script.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html