Enforcing volume (traffic) limit

[wlanmac]

See: http://coova.org/wiki/index.php/CoovaChilli/RADIUS

ChilliSpot-Max-Input-Octets = bytes
ChilliSpot-Max-Output-Octets = bytes
ChilliSpot-Max-Total-Octets = bytes
        Chilli vendor specific attributes for setting the max in, out,
        or total bytes transferred for the session. ...
        
You can limit on data up/down. You'd *also* want to deny subsequent
logins when over the limit...

David


On Wed, 2008-10-22 at 12:25 +0200, Liran Tal wrote:
> 
> 
> On Sun, Oct 19, 2008 at 1:15 PM, Outback Dingo
> <outbackdingo at gmail.com> wrote:
>         coova denies connection on next authentication
>         
>         
>         
> 
> Well there's the Chillispot-Max-Total-Octets attribute but if
> chillispot/coovachilli doesn't track the octets count
> and doesn't disconnect the user when the limit has reached then what's
> the use for it? I can just use an internal
> sqlcounter attribute in freeradius.
> 
> Any comments on that?
> 
>  
>         
>         On Sun, Oct 19, 2008 at 5:14 PM, Liran Tal
>         <liran.tal at gmail.com> wrote:
>                 
>                 Hey guys,
>                 
>                 I was wondering if any of you are enforcing
>                 volume/traffic limiting such as monthly total
>                 upload/download? (AcctInputOctets/AcctOutputOctets)
>                 Which are attribute are you using for it? Does
>                 coovachilli disconnects the session when this quota
>                 has reached or the user may go beyond
>                 the quota but his next session authentication request
>                 will be rejected because of FreeRADIUS's sqlcounter
>                 module?
>                 
>                 
> 
>  
> 
> 
> 
> -- 
> -- 
> Sincerely, Liran Tal
> 
> Head R&D
> Linux and Open Source
> Enginx - http://enginx.com
>