Session-Octets-Limit should only be in the reply table ( it is not a value that should be checked – right ? ).

 

If the freeradius replies the attribute – the freeradius is finished with his task. Now your RP-PPPoE server and the radiusclient should do the rest of the work. Traffic limiting is done with PPProtocol on your NAS ( your pppoe server ). Be sure that the radiusclient also has the attribute in his dictionary file. Look at the output of the ppp and pppoe ( increase the log level – or put both in debug mode ).

 

It seems that this is not problem of freeradius anymore !

 

Regards,

 

Edvin

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mordor Networks
Sent: Dienstag, 30. Mai 2006 22:56
To: FreeRadius users mailing list
Subject: Session-Octets-Limits

 

Hello users

I'm trying to add Session-Octets-Limit to limit the user bandwidth i add Session-Octets-Limit := 1000 in radcheck and radreply
and i can see it in the radiusd -X and in the radattr file :

Framed-IP-Address 
70.70.70.70
Session-Octets-Limit 825241648
Framed-Protocol PPP
Framed-IP-Netmask 255.255.255.255
Framed-MTU 1500
Session-Timeout 43200

Idle-Timeout 1200
Port-Limit 1

But it is not disconnecting the user when reach the limit , can someone help me please?




- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to