[rbak-nsp] RES: limit traffic ession

[Reda Nedjar]

Hi Alexandre,

On the SmartEdge plateforme you can use its integrated volume based feature to set a volume limit for the session. Once that limit is reached the SmartEdge can take one of the 2 actions depending on its configuration :
-either disconnect automatically the user session. Accounting-stop with disconnect reason (volume limit reached) is sent to a Radius server.
-or keep the session live and send a triggered interim accounting indicating that volume limit is reached. From here your Radius can take the action to set a new policy (new rate-limit, qos policy, volume quota...etc) for the user's session through CoA.

For this to work you need to return the Redback VSA 113 RB-Session-Traffic-Limit in the access-accept.
--------------------
RB-Session-Traffic-Limit : String. Specifies that inbound, outbound, or aggregated traffic be limited. Use the in: limit, out:limit or aggregate: limit format where limits are in Kbytes. The limit values set for inbound andoutbound traffic are independent of each other, while the limit value set for aggregate traffic is the total sum of both inbound and outbound traffic. When configuring Session-Traffic-Limit, you can configure the limit for either of these options:  Inbound traffic, outbound traffic, or both
-------------------

Regards,
Reda

From: redback-nsp-bounces at puck.nether.net [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Thiago Lizardo de Moraes
Sent: Thursday, August 20, 2009 10:14 PM
To: Alexandre Chapellon; redback-nsp at puck.nether.net
Subject: [rbak-nsp] RES: limit traffic ession
Importance: High

Hi Alexandre,

            I think you should combine two radius features at Redback and your Radius platform to solve that issue:

1)     Enable "RADIUS Interim" feature at Redback devices. This feature able Redback device to send accounting interim packets from a specific subscriber each time interval(usually 30 seconds).
2)     Enable "Radius CoA(change-of-authorization)" feature at Redback devices and Radius Platform: Your Radius platform needs to analyze that Interim packets to trigger a Radius CoA(disconnect value) when the traffc transferred reach 4Gb.

Free for ask me if you have some doubts,

Best regards,
Thiago Lizardo de Moraes
GVT - 25 - Network Consultant Sp
*   +55 41 3022 9348
È   +55 41 8838 8561
*     thiago.moraes at gvt.com.br
________________________________
De: redback-nsp-bounces at puck.nether.net [mailto:redback-nsp-bounces at puck.nether.net] Em nome de Alexandre Chapellon
Enviada em: quinta-feira, 20 de agosto de 2009 15:25
Para: redback-nsp at puck.nether.net
Assunto: [rbak-nsp] limit traffic ession

Hello,

I have radius talking to redback devices, but as I don't own thoose devices myself... I don't have official support from redback: here is why i'm here.
I would like to disconnect user whe, they have reached a certain amount of traffic (inbound+outbound)
Does anyone know about attributes (eg. sent in acces-accept) supported by redback devices that would allow disconnection of sessions based on the amount of traffic transfered during the session and which could be set to higher than 4Gb?

If such an attribute does not exist... how could I acheive session disconnection based on user traffic.

thanks to any redback guru!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20090820/7951dea0/attachment.html>