Hi all, Where to find all of FR supported attributes ? I just try rlm_sqlcounter module with noresetconter script and Max-All-Session attribute and they are working fine. And I've plan to add another attribute called expiration (?) and need the correct syntax how to use it. Where to find my needs ? TIA PD
Radius attributes - http://www.freeradius.org/rfc/attributes.html . You actually invent sqlcounter attributes yourself by making the appropriate SQL query. Ivan Kalik Kalik Informatika ISP Dana 9/3/2007, "PD" <paul@ranahminang.net> piše:
Hi all,
Where to find all of FR supported attributes ?
I just try rlm_sqlcounter module with noresetconter script and Max-All-Session attribute and they are working fine.
And I've plan to add another attribute called expiration (?) and need the correct syntax how to use it.
Where to find my needs ?
TIA
PD
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html . Thx, but I can not find expiration attribute on the aboce list.
But I do find 'Expiration' at dictionary.freeradius.internal and also small (not enough information) explanation at http://wiki.freeradius.org/Radiusd.conf PD
Unfortunatelly, I found the answer of the similar question. see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ? The case is suppose to create an account for 10 hours but only valid one week after the creation date. TIA PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
Yes. Expiration can stop them logging on after a week and Max-All-Session can limit usage to 10 hours. Ivan Kalik Kalik Informatika ISP Dana 10/3/2007, "PD" <paul@ranahminang.net> piše:
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue. here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too. Ivan Kalik Kalik Informatika ISP Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> piše:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thx for the answers... Actually we have plan to use multiple tipe and number of wireless NAS, such as chillispot, mikrotik, etc. Therefor we are looking for the attributes that compatiple for all NAS type. For the Expiration attribute, how the correct syntax ? If I want to expire the account at march 20, 2007 which is the correct syntax ? TIA PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> pi¹e:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
It's a date. And it looks like the bug was reported. Expiration format in first thread, patch in second: http://archives.free.net.ph/search/20081201.000000.00000000@sb:patch,sb:sqlc... Ivan Kalik Kalik Informatika ISP Dana 11/3/2007, "PD" <paul@ranahminang.net> piše:
Thx for the answers...
Actually we have plan to use multiple tipe and number of wireless NAS, such as chillispot, mikrotik, etc. Therefor we are looking for the attributes that compatiple for all NAS type.
For the Expiration attribute, how the correct syntax ? If I want to expire the account at march 20, 2007 which is the correct syntax ?
TIA
PD
On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> piše:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
You need send the message for each NAS, because they are not handle an standart attributes I think that. Fabián
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sun, 11 Mar 2007 03:22:15 +0000
Thx for the answers...
Actually we have plan to use multiple tipe and number of wireless NAS, such as chillispot, mikrotik, etc. Therefor we are looking for the attributes that compatiple for all NAS type.
For the Expiration attribute, how the correct syntax ? If I want to expire the account at march 20, 2007 which is the correct syntax ?
TIA
PD
On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> pi¹e:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Find what you need at prices youll love. Compare products and save at MSN® Shopping. http://shopping.msn.com/default/shp/?ptnrid=37,ptnrdata=24102&tcode=T001MSN2...
Chillispot is a gateway, not matter if you passthrough with Wifi connection or wire connection, Chillispot not identify they. The litle diference is, if you use Expiration attribute Chillispot ignores it, so when the time is reach chillispot not logoff the user. So, you need send the correct reply for each gateway, switch or device that manage the connection because Freeradius not disconnect the users, this is a NAS job. Fabián
From: <tnt@kalik.co.yu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 18:49:35 +0100
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> pi¹e:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Find a local pizza place, movie theater, and more .then map the best route! http://maps.live.com/?icid=hmtag1&FORM=MGAC01
Wired chilli? The makers say: "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN." Do you know something they don't? Expiration is an internal FreeRadius attribute - it doesn't go out in radius packets. It is used to generate "real" radius attributes like Session-Timeout. So NAS (Cisco, Chilli, Mickrotik, whatever) will never "see" this attribute. None of them would know what to do with it if they would recieve it. Ivan Kalik Kalik Informatika ISP Dana 12/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> piše:
Chillispot is a gateway, not matter if you passthrough with Wifi connection or wire connection, Chillispot not identify they. The litle diference is, if you use Expiration attribute Chillispot ignores it, so when the time is reach chillispot not logoff the user.
So, you need send the correct reply for each gateway, switch or device that manage the connection because Freeradius not disconnect the users, this is a NAS job.
Fabián
From: <tnt@kalik.co.yu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 18:49:35 +0100
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> piše:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid one week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Find a local pizza place, movie theater, and more .then map the best route! http://maps.live.com/?icid=hmtag1&FORM=MGAC01
Chillispot is a "captive portal that's it" You can use it with wired and wireless LAN. Check It!!! Other point. You right, Expiration is an Internal Freeradius Attribute, but by default only check if the expiration date < NOW(), so if user make a connection 1 milisecond beford that expiration date, the connection is accepted and the user keep connected until it want. Freeradius donŽt generate Session-Timeout reply by default, so the nas donŽt know when disconnect the user, if you use the correct reply message for the nas that manage the connection, the nas will disconnect the user when the timeout.
Do you know something I don't?< I'm sure do you know something I don't, but I don't find more information about freeradius and I write on my experience. I think the idea is put the system to work, because many people like me, need a fast solutions and don't have time to investigate or try find of perfection
Fabián Franzotti
From: <tnt@kalik.co.yu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Mon, 12 Mar 2007 14:04:25 +0100
Wired chilli? The makers say: "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN." Do you know something they don't?
Expiration is an internal FreeRadius attribute - it doesn't go out in radius packets. It is used to generate "real" radius attributes like Session-Timeout. So NAS (Cisco, Chilli, Mickrotik, whatever) will never "see" this attribute. None of them would know what to do with it if they would recieve it.
Ivan Kalik Kalik Informatika ISP
Dana 12/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> pi¹e:
Chillispot is a gateway, not matter if you passthrough with Wifi connection or wire connection, Chillispot not identify they. The litle diference is, if you use Expiration attribute Chillispot ignores it, so when the time is reach chillispot not logoff the user.
So, you need send the correct reply for each gateway, switch or device that manage the connection because Freeradius not disconnect the users, this is a NAS job.
Fabián
From: <tnt@kalik.co.yu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 18:49:35 +0100
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Ivan Kalik Kalik Informatika ISP
Dana 10/3/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> pi¹e:
If you use Chillispot, put in your user Max-All-Session and WISPr-Session-Terminate-Time they work very good together
because if you use Expire attribute the freeradius know it but chillispot no, so if the user try to connect after the Expire time the radius reject this connection, but i the user is connected and the chillispot don't know the expire attribute so the connection continue.
here is the suported attributes for the chillispot http://www.chillispot.org/features.html#mozTocId149863
From: PD <paul@ranahminang.net> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 03:46:50 +0000
Unfortunatelly, I found the answer of the similar question.
see
http://www.arcknowledge.com/gmane.comp.freeradius.user/2003-02/msg00671.html
Well.. just to make sure, can Expiration attribute work together with Max-All-Session attribute ?
The case is suppose to create an account for 10 hours but only valid
one
week after the creation date.
TIA
PD On 3/10/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Radius attributes - http://www.freeradius.org/rfc/attributes.html .
You actually invent sqlcounter attributes yourself by making the appropriate SQL query.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Get a FREE Web site, company branded e-mail and more from Microsoft Office Live! http://clk.atdmt.com/MRT/go/mcrssaub0050001411mrt/direct/01/
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Find a local pizza place, movie theater, and more .then map the best route! http://maps.live.com/?icid=hmtag1&FORM=MGAC01
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
_________________________________________________________________ Play Flexicon: the crossword game that feeds your brain. PLAY now for FREE. http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
On 3/12/2007, "tnt@kalik.co.yu" <tnt@kalik.co.yu> wrote:
Wired chilli? The makers say: "ChilliSpot is an open source captive portal or wireless LAN access point controller. It is used for authenticating users of a wireless LAN." Do you know something they don't?
My first Chilli installation is working for both wired and wireless connections. The mention box still sitting at the same place and still serve both wired and wireless connections. The second and next installations are designed for wireless only.
Expiration is an internal FreeRadius attribute - it doesn't go out in radius packets. It is used to generate "real" radius attributes like Session-Timeout. So NAS (Cisco, Chilli, Mickrotik, whatever) will never "see" this attribute. None of them would know what to do with it if they would recieve it.
I will try the Expiration lately at the end of this week and will let you know the result. TIA PD
Hi guys, Just to let all of you know.. I try the Expiration attribute today and it working find. The NAS used is Chillispot (ChilliSpot inside of WRT54GS). The Expiration attribute inserted into radcheck table with op == the expiration will block an account since the date put into value field. So, if I put (today is March 14, 2007 at our place) an expiration 'Mar 14 2007' the account can not login anymore. If I put an expiration 'Mar 15 2007' the account will able to login till tonight. The only problem is no explanation to user, why the system give an error Login Failed. I did try to add expiration into radiusd.conf as explain at http://wiki.freeradius.org/Radiusd.conf but FR refuse to start with error : Wed Mar 14 15:59:14 2007 : Error: radiusd.conf[1587] Failed to link to module 'rlm_expiration': Shared object "rlm_expiration.so" not found, required by "radiusd" How to fixed this problem ? TIA PD On 3/13/2007, "PD" <paul@ranahminang.net> wrote: ..cut...
Expiration is an internal FreeRadius attribute - it doesn't go out in radius packets. It is used to generate "real" radius attributes like Session-Timeout. So NAS (Cisco, Chilli, Mickrotik, whatever) will never "see" this attribute. None of them would know what to do with it if they would recieve it.
I will try the Expiration lately at the end of this week and will let you know the result.
PD wrote:
I did try to add expiration into radiusd.conf as explain at http://wiki.freeradius.org/Radiusd.conf but FR refuse to start with error : Wed Mar 14 15:59:14 2007 : Error: radiusd.conf[1587] Failed to link to module 'rlm_expiration': Shared object "rlm_expiration.so" not found, required by "radiusd"
The expiration module is not in 1.1.5. You don't need the expiration module in 1.1.5, that functionality is in the server core. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
I am using FR 1.1.4 build from FBSD port do I need to load the module ? TIA PD On 3/14/2007, "Alan DeKok" <aland@deployingradius.com> wrote:
PD wrote:
I did try to add expiration into radiusd.conf as explain at http://wiki.freeradius.org/Radiusd.conf but FR refuse to start with error : Wed Mar 14 15:59:14 2007 : Error: radiusd.conf[1587] Failed to link to module 'rlm_expiration': Shared object "rlm_expiration.so" not found, required by "radiusd"
The expiration module is not in 1.1.5. You don't need the expiration module in 1.1.5, that functionality is in the server core.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
PD wrote:
I am using FR 1.1.4 build from FBSD port do I need to load the module ?
No. If it's not in 1.1.5, it's not in any prior version, either. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
I think the same too... cause expiration is not the new attribute. The expiration attribute itself working fine, the only problem is no explanation to user when the system reject him/her. CMIIW PD On 3/14/2007, "Alan DeKok" <aland@deployingradius.com> wrote:
PD wrote:
I am using FR 1.1.4 build from FBSD port do I need to load the module ?
No. If it's not in 1.1.5, it's not in any prior version, either.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Did you set the reply message in radiusd.conf? # # The expiration module. This handles the Expiration attribute # It should be included in the *end* of the authorize section # in order to handle user Expiration. It should also be included # in the instantiate section in order to register the Expiration # compare function # expiration { # # The Reply-Message which will be sent back in case the # account has expired. Dynamic substitution is supported # reply-message = "Password Has Expired\r\n" # reply-message = "Your account has expired, %{User-Name}\r\n" } Ivan Kalik Kalik Informatika ISP Dana 14/3/2007, "PD" <paul@ranahminang.net> piše:
I think the same too... cause expiration is not the new attribute.
The expiration attribute itself working fine, the only problem is no explanation to user when the system reject him/her.
CMIIW
PD On 3/14/2007, "Alan DeKok" <aland@deployingradius.com> wrote:
PD wrote:
I am using FR 1.1.4 build from FBSD port do I need to load the module ?
No. If it's not in 1.1.5, it's not in any prior version, either.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
PD wrote:
I think the same too... cause expiration is not the new attribute.
The expiration attribute itself working fine, the only problem is no explanation to user when the system reject him/her.
You can edit the code to produce the message, or run the CVS head. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Well... I can see on the source code (auth.c) that FR send the reply. static int check_expiration(REQUEST *request) { VALUE_PAIR *check_item; VALUE_PAIR *vp; check_item = pairfind(request->config_items, PW_EXPIRATION); if (!check_item) return 0; /* * Has this user's password expired? * * If so, remove ALL reply attributes, * and add our own Reply-Message, saying * why they're being rejected. */ if (((time_t) check_item->lvalue) <= request->timestamp) { vp = pairmake("Reply-Message", "Password Has Expired\r\n", T_OP_ADD); pairfree(&request->reply->vps); request->reply->vps = vp; return -1; } Or... should I check another file ? CMIIW PD On 3/14/2007, "Alan DeKok" <aland@deployingradius.com> wrote:
PD wrote:
I think the same too... cause expiration is not the new attribute.
The expiration attribute itself working fine, the only problem is no explanation to user when the system reject him/her.
You can edit the code to produce the message, or run the CVS head.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 3/12/2007, "Internet-Wifi Operador" <internet-wifi@hotmail.com> wrote:
Chillispot is a gateway, not matter if you passthrough with Wifi connection or wire connection, Chillispot not identify they. The litle diference is, if you use Expiration attribute Chillispot ignores it, so when the time is reach chillispot not logoff the user.
So, you need send the correct reply for each gateway, switch or device that manage the connection because Freeradius not disconnect the users, this is a NAS job.
Well.. in my understanding... NAS send username and password to radius and expecting the answer from radius. Then radius will answer accept or reject. This already working well with our Livingston PM2e. I did try Login-Time and Expiration with the above NAS and it working very well too. The different with wireless and or hotspot is the additional attribute about 'Max-All-Session' and 'Expiration'. With this tipe, radius will send conditional accept connection because will contain the time left.
From: <tnt@kalik.co.yu> Reply-To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org> Subject: Re: FR supported attributes Date: Sat, 10 Mar 2007 18:49:35 +0100
There should be no difference in using Expiration and WISPr-Session-Terminate-Time in this case. Expiration sets Session-Timeout and ChilliSpot knows that one. The only difference is that Expiration will work with wired connections too.
Has you try that Expiration working for Chillispot ? I hope it work. We need to set the expiration on the certain date for each time user doing top-up. This is similarly like GSM prepaid way. Example.. on date 1, user buy the primary card (first registration), the session will set for max 2 hours but valid until date 7 on date 7, user buy the top up voucher for 2 hours more, so the session for him/her will upgrate into max 4 hours but the expiration date change into date 15 etc. CMIIW PD
participants (4)
-
Alan DeKok -
Internet-Wifi Operador -
PD -
tnt＠kalik.co.yu