Diferent Session-Timeout depending on NAS
Hi people, I have been working with RADIUS for sereral years and now we want to implement a different accounting for prepaid cards. I will explain my quesion shortly. Two types of hotspots zones: Spain and Mexico. Everyone know prizces in Mexico are cheaper than in Spain. Well, my accounts are valid in both countries, however the conection time are shorter in Spain than in Mexico. How can I modify the Session-Timeout attribute depending on NAS? Thanks. _________________________________________________________________ Horóscopo, tarot, numerología... Escucha lo que te dicen los astros. http://astrocentro.msn.es/
Two types of hotspots zones: Spain and Mexico. Everyone know prizces in Mexico are cheaper than in Spain. Well, my accounts are valid in both countries, however the conection time are shorter in Spain than in Mexico. How can I modify the Session-Timeout attribute depending on NAS?
First, a general question: all those geographically disperse NASes are connected to *one* central server? Huh. My proposed solution: add a line to the users file for each NAS saying DEFAULT NAS-IP-Address == 1.2.3.4 Session-Timeout := Whatever-you-like (assuming the NAS sends his IP address as attribute. If it doesn't, and is directly connected, use Client-IP-Address instead). That way, you can set Session-Timeout on a per-NAS basis. Greetings, Stefan Winter -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
Yeah!! Your solution is the easiest one. I did not explain enough well my problem. the session-timeout has to asign depending on the NAS and the remaining time. My goal is sends the value of Session-Timeout attribute once this value had benn multiplied by a factor depending on the NAS. For instance, an account has Session-timeout = 600. If the account is used in Europe Session-timeout = 600, but it is used in Mexico Session-timeout = 600*2.5 = 1500. Yes. Value is modified in execution time. Does someone know any solution ?
From: Stefan Winter <stefan.winter@restena.lu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Subject: Re: Diferent Session-Timeout depending on NAS Date: Fri, 30 Jun 2006 15:27:16 +0200
Two types of hotspots zones: Spain and Mexico. Everyone know prizces in Mexico are cheaper than in Spain. Well, my accounts are valid in both countries, however the conection time are shorter in Spain than in Mexico. How can I modify the Session-Timeout attribute depending on NAS?
First, a general question: all those geographically disperse NASes are connected to *one* central server? Huh.
My proposed solution: add a line to the users file for each NAS saying
DEFAULT NAS-IP-Address == 1.2.3.4 Session-Timeout := Whatever-you-like
(assuming the NAS sends his IP address as attribute. If it doesn't, and is directly connected, use Client-IP-Address instead).
That way, you can set Session-Timeout on a per-NAS basis.
Greetings,
Stefan Winter
-- Stefan WINTER
Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung
6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
<< attach4 >>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Dale rienda suelta a tu tiempo libre. Mil ideas para exprimir tu ocio con MSN Entretenimiento. http://entretenimiento.msn.es/
Yes. Value is modified in execution time. Does someone know any solution ?
In your scenario, Session-Time does not need to be calculated at execution time, it is solely dependent on the NAS. The solution I proposed accounts to that. Depending on the NAS IP address, you can enter whatever session timeout you like. Your problem is solved by that. Stefan -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
For instance, an account has Session-timeout = 600. If the account is used in Europe Session-timeout = 600, but it is used in Mexico Session-timeout = 600*2.5 = 1500.
Yes. Value is modified in execution time. Does someone know any solution ?
Um, sorry. After reading your post again, I think I got it. You have users with different default timeouts, and depending on the location these defaults may have to be stretched by a constant factor? In that case, think do get a bit more complicated. But you can do it by adding an instance of rlm_perl, feed a perl script with the user's default time and the NAS's IP address, let the perl script calculate the Session-Timeout and return that to the RADIUS server. Greetings, Stefan -- Stefan WINTER Stiftung RESTENA - Réseau Téléinformatique de l'Education Nationale et de la Recherche Ingenieur Forschung & Entwicklung 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg E-Mail: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
participants (2)
-
Santiago Balaguer García -
Stefan Winter