Hi Alan, The thing is that, I once tried using Mikrotik-Xmit-Limit as a reply attribute. When I did this, the client kept having the same amount of data left at every login. It was as if the attribute was not being updated. However, when I used Mikrotik-Xmit-Limit as a check attribute, the user's data was updated and subtracted as it should. They got no access after using up their data. I don't know if this experience has been reported before. What do you make of it? On Thursday, January 23, 2014 1:57 PM, Alan DeKok <aland@deployingradius.com> wrote: Kwesi Yankson wrote:
Hi Nick, Thank for replying. Correct me if I'm wrong. From your answer, assuming I want 11GB of data, I need to set Mikrotik-Xmit-Limit to 3GB and Mikrotik-Xmit-Limit-Gigawords to 2 (that is 8GB). That is speaking in simpler terms (with no 0C0000x@#$%^%) :)
Yes. In simpler terms: Limit = X GB Mikrotik-Xmit-Limit-Gigawords = X / 4GB Mikrotik-Xmit-Limit = X - (Mikrotik-Xmit-Limit-Gigawords * 4GB)
If that is so, it mean Mikrotik-Xmit-Limit will be a "check" attribute whiles Mikrotik-Xmit-Limit-Gigawords will be a "reply" attribute".
No. They're both reply attributes. You need to send both to the NAS in order for the limit to be enforced. Alan DeKok.