Re: freeradius unistalling
or may be, when configuring the installation, use --prefix, to install the server in location other than default # ./configure --prefix=/opt/freeradius I will ease use to remove freeradius using command # rm -rf /opt/freeradius On 3/24/07, Thor Spruyt [EMAIL PROTECTED] wrote: There is no uninstall and make clean just cleans the source tree. Use rpmbuild to make an rpm. - Original Message - From: elmalhi abdelghani To: FreeRadius users mailing list Sent: Friday, March 23, 2007 3:48 PM Subject: Re : freeradius unistalling hi, but i found always my directory usr/local/etc/raddb regards! Abdelghani ELMALHI Devesestr. 1 45897 Gelsenkirchen Deutschland Tel. 00 49 176 65 84 38 50 Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Best Regards, Fadli M. Zain Leadership and Lifelong Learning - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: bandwidth and volume limit
A) bandwidth limit You can use WISPr-Bandwidth-Max-Down and WISPr-Bandwidth-Max-Up attribute to limit the bandwidth. they should be inserted in radreply or groupradreply table. But you need to modify NAS firewall to force the attribute to user. I use chillispot. In the NAS I force all user Internet session to use tun0 device which is created by chillispot. This is my rule for forward chain : # iptables -P FORWARD DROP # iptables -F FORWARD # iptables -A FORWARD -o tun0-j ACCEPT # iptables -A FORWARD -i tun0 -j ACCEPT b) volume limit. I face the same problem too when dealing with freeradius 1.1.3. but after upgrade to freeradius 1.1.4, the problems solved itself, no more Session Time generated, but only AcctInputOctet. I suggest you to upgrade to Freeradius 1.1.4. but if you insist to stick on current version, you must create some perl script to help freeradius server to generate AcctInputOctet for accounting. On 3/22/07, Mathieu Lemaitre [EMAIL PROTECTED] wrote: HI all, I'm running freeradius 1.0.2 on a debian stable. For new clients, I need to implement 2 functions: * a bandwidth limit on a per-user basis. I mean, I need to be able to set, for a user, a value for his upstream and downstream bw, which is sent by the radius as a reply attribute. Are they predefined attributes to do this? * a volume limit: I'd like to be able to set a maximum amount of data monthly downloadable for each user. I tried with rlm_slqcounter, changing the sql request to check AcctInputOctet instead of SessionTime, but the problem is that radius always reply an attribute called MaxSessionTime (or sthg like that), containing the remaining data volume for the user... is there as way to change the name of the attribute answered by freeradius?? Many thaks, Mathieu - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Best Regards, Fadli M. Zain Leadership and Lifelong Learning - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Questions about Freeradius counter
On 3/22/07, guest01 [EMAIL PROTECTED] wrote:
Hi guys!
I have two minor problems with the radius counter. I am using the radius
counter for counting the sessiontimeout, which works quite good.
counter sessiontimeout {
filename = ${logdir}/db.sessiontimeout
key = User-Name
count-attribute = Acct-Session-Time
reset = never
counter-name = Daily-Session-Time
check-name = Session-Timeout
cache-size = 5000
}
If the user reaches the saved allowed max session time, the connection
gets disconnected and the user is not allowed to connect again until the
time value has been reseted. Works great ...
I also want to achieve the same behavior for another counter, the
Acct-Input-Octets, but it doesn't really work. I can define a maximum
value for Input Octets and if the user exceeds this value, he cannot
connect again. Unfortunately, the connection doesn't get disconnected
after the user reached his limit, do I have to configure something
additional? It works for the Sessiontimeout, why doesn't it work for the
Input-Octets? Any ideas? Is it possible?
counter maxinput {
filename = ${logdir}/db.maxinput
key = User-Name
count-attribute = Acct-Input-Octets
reset = never
counter-name = Input-Octets
check-name = ChilliSpot-Max-Input-Octets
cache-size = 5000
}
I face the same problem on Freeradius 1.1.3, and to overcome the situation,
I wrote a perl script to set the correct ChilliSpot-Max-Input-Octets for
Freeradius. But I have upgraded to Freeradius 1.1.4, the no more problem
with it.
The second problem is, that I have Acct-Input-Octets AND
Acct-Output-Octets in my radius dialog and I want to use ONE counter,
which should contain the sum of Acct-Input-Octets+Acct-Output-Octets, I
already tried to use
count-attribute = (Acct-Input-Octets+Acct-Output-Octets),
but it didn't work ... Any suggestions for that problem? Any ideas?
U can specify the sql query for the counter:
counter maxinput {
filename = ${logdir}/db.maxinput
key = User-Name
count-attribute = Acct-Input-Octets
reset = never
counter-name = Input-Octets
check-name = ChilliSpot-Max-Input-Octets
query = SELECT SUM(Acct-Input-Octets+Acct-Output-Octets) FROM
radacct where UserName='%{%k}'
}
I appreciate every kind of help!
Thanks guys!
best regards
Peter Gastinger
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
--
Best Regards,
Fadli M. Zain
Leadership and Lifelong Learning
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
