<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><DIV><FONT face=Tahoma size=2><FONT face=Calibri size=3>Hi , </FONT></DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif">
<DIV style="FONT-SIZE: 13px; FONT-FAMILY: arial, helvetica, sans-serif">
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><FONT face=Calibri size=3>I want to configure for pre-paid billing system in free radius , please let me what are necessary module n</FONT><FONT face=Calibri size=3>eed to configure. </FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><FONT face=Calibri size=3> </FONT></o:p><FONT face=Calibri size=3>Regards,</FONT></P>
<P class=MsoNormal style="MARGIN: 0in 0in 10pt"><FONT face=Calibri size=3>Sachidananda Sahoo</FONT></P>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> "freeradius-users-request@lists.freeradius.org" <freeradius-users-request@lists.freeradius.org><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> freeradius-users@lists.freeradius.org<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, May 18, 2009 6:55:29 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Freeradius-Users Digest, Vol 49, Issue 74<BR></FONT><BR>Send Freeradius-Users mailing list submissions to<BR> <A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A><BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://lists.freeradius.org/mailman/listinfo/freeradius-users" target=_blank>http://lists.freeradius.org/mailman/listinfo/freeradius-users</A><BR>or, via email, send a message with subject or body
'help' to<BR> <A href="mailto:freeradius-users-request@lists.freeradius.org" ymailto="mailto:freeradius-users-request@lists.freeradius.org">freeradius-users-request@lists.freeradius.org</A><BR><BR>You can reach the person managing the list at<BR> <A href="mailto:freeradius-users-owner@lists.freeradius.org" ymailto="mailto:freeradius-users-owner@lists.freeradius.org">freeradius-users-owner@lists.freeradius.org</A><BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Freeradius-Users digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. Re: question about windows users (Alan DeKok)<BR> 2. Re: Wimax + Freeradius (Alan DeKok)<BR> 3. Re: Module-Success-Message / Module-Failure-Message (Alan DeKok)<BR> 4. Re: current RHEL/CentOS pre-built packages (Was: freeRADIUS)<BR> (Alan DeKok)<BR> 5. Re[2]: Wimax + Freeradius (Maxim
Vinnichenko)<BR> 6. Re: Wimax + Freeradius (Alan DeKok)<BR> 7. FreeRADIUS Server Version 2.1.6 has been released (Alan DeKok)<BR> 8. RE: Module-Success-Message / Module-Failure-Message<BR> (Laar van de, Johan, TNF)<BR> 9. duplicate Identity received, freeradius behaviour?<BR> (Jean F. Mousinho)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Mon, 18 May 2009 12:57:38 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: Re: question about windows users<BR>To: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A
href="mailto:4A113F22.8060006@deployingradius.com" ymailto="mailto:4A113F22.8060006@deployingradius.com">4A113F22.8060006@deployingradius.com</A>><BR>Content-Type: text/plain; charset=ISO-8859-1<BR><BR>Bartosz Chodzinski wrote:<BR>> /etc/freeradius/certs/README<BR><BR> I've never understood why people think it's useful to post<BR>documentation from the server on this list. Do you think we haven't<BR>seen it?<BR><BR>> and something happend:<BR>> ( I think key information is <BR>> TLS_accept:error in SSLv3 read client certificate A<BR>> rlm_eap: SSL error error:00000000:lib(0):func(0):reason(0)<BR>> but uncle google find as many diferent answers as peple having this problem)<BR><BR> It means that you're running a server that is YEARS out of date. Why<BR>not use a more recent version?<BR><BR>> log freeradius -X:<BR><BR>> Sending Access-Challenge of id 115 to 192.168.5.206 port
1812<BR>> EAP-Message =<BR>> 0x010b00350d800000002b1403010001011603010020735b6dedb59fdb27811198c86a86bb2fdf2e96ce8f59031cc76f36b80bf1d04c<BR>> Message-Authenticator = 0x00000000000000000000000000000000<BR>> State = 0x9f4e794b784914b1f67ff19696408712<BR>> Finished request 9<BR>> Going to the next request<BR>> Waking up in 5 seconds...<BR>> --- Walking the entire request list ---<BR>> Cleaning up request 5 ID 111 with timestamp 416c8b35<BR><BR> This is in the FAQ. Go read it.<BR><BR> Alan DeKok.<BR><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Mon, 18 May 2009 13:03:42 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: Re: Wimax + Freeradius<BR>To: <A href="mailto:maxim@babilon-t.tj"
ymailto="mailto:maxim@babilon-t.tj">maxim@babilon-t.tj</A>, FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:4A11408E.6060000@deployingradius.com" ymailto="mailto:4A11408E.6060000@deployingradius.com">4A11408E.6060000@deployingradius.com</A>><BR>Content-Type: text/plain; charset=UTF-8<BR><BR>Maxim Vinnichenko wrote:<BR>> Thank you for you answer. I've changed test user and now the server<BR>> sends access-accept but CPE still doesn't connect.<BR><BR> Some NAS equipment will ignore Access-Accept if it doesn't contain the<BR>right magic. The exact definition of this magic is usually found buried<BR>in a footnote on page 400 out of 800 of the vendor documentation.<BR><BR> Go look at the NAS logs, and see if there is
any useful messages. If<BR>not, call the NAS vendor, and tell them that their product is defective.<BR><BR> FreeRADIUS works with WiMAX equipment from Nokia, Cisco and Motorola.<BR>(That I've seen.) Other vendors known to have problems include<BR>Alvarion. They don't seem to care that their equipment doesn't work,<BR>and they haven't answered any of my messages about it.<BR><BR> The only solution is to point out publicly that Alvarion is *not*<BR>following the WiMAX specs, and therefore people should buy *real* WiMAX<BR>equipment.<BR><BR> Alan DeKok.<BR><BR><BR>------------------------------<BR><BR>Message: 3<BR>Date: Mon, 18 May 2009 13:04:35 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: Re: Module-Success-Message / Module-Failure-Message<BR>To: FreeRadius users mailing list<BR> <<A
href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:4A1140C3.5070202@deployingradius.com" ymailto="mailto:4A1140C3.5070202@deployingradius.com">4A1140C3.5070202@deployingradius.com</A>><BR>Content-Type: text/plain; charset=ISO-8859-1<BR><BR>Laar van de, Johan, TNF wrote:<BR>> My Question is, if this is relatively easy, how can I achieve this? <BR><BR> The log messages can be changed via source code edits.<BR><BR> This *could* be made configurable, but that also requires source code<BR>edits.<BR><BR> Alan DeKok.<BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date: Mon, 18 May 2009 13:06:22 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: Re: current RHEL/CentOS pre-built
packages (Was: freeRADIUS)<BR>To: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:4A11412E.1030000@deployingradius.com" ymailto="mailto:4A11412E.1030000@deployingradius.com">4A11412E.1030000@deployingradius.com</A>><BR>Content-Type: text/plain; charset=ISO-8859-1<BR><BR>John Dennis wrote:<BR>> It is critical to note for RHEL customers the updated RPMS are<BR>> considered "tech preview" and do not come with any official RHEL<BR>> support.<BR><BR> If they want support for *any* version of the server, it's available.<BR>See <A href="http://networkradius.com/" target=_blank>http://networkradius.com</A><BR><BR> But that's specific to FreeRADIUS, and not to the entire RHEL package.<BR><BR> Alan
DeKok.<BR><BR><BR>------------------------------<BR><BR>Message: 5<BR>Date: Mon, 18 May 2009 16:25:23 +0500<BR>From: Maxim Vinnichenko <<A href="mailto:maxim@babilon-t.tj" ymailto="mailto:maxim@babilon-t.tj">maxim@babilon-t.tj</A>><BR>Subject: Re[2]: Wimax + Freeradius<BR>To: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Cc: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:471893738.20090518162523@babilon-t.tj" ymailto="mailto:471893738.20090518162523@babilon-t.tj">471893738.20090518162523@babilon-t.tj</A>><BR>Content-Type: text/plain; charset=utf-8<BR><BR>Hello Alan,<BR><BR><BR><BR>Monday, May 18, 2009, 4:03:42 PM, you wrote:<BR><BR>> Maxim Vinnichenko
wrote:<BR>>> Thank you for you answer. I've changed test user and now the server<BR>>> sends access-accept but CPE still doesn't connect.<BR><BR>> Some NAS equipment will ignore Access-Accept if it doesn't contain the<BR>> right magic. The exact definition of this magic is usually found buried<BR>> in a footnote on page 400 out of 800 of the vendor documentation.<BR><BR>> Go look at the NAS logs, and see if there is any useful messages. If<BR>> not, call the NAS vendor, and tell them that their product is defective.<BR><BR>> FreeRADIUS works with WiMAX equipment from Nokia, Cisco and Motorola.<BR>> (That I've seen.) Other vendors known to have problems include<BR>> Alvarion. They don't seem to care that their equipment doesn't work,<BR>> and they haven't answered any of my messages about it.<BR><BR>> The only solution is to point out publicly that Alvarion is
*not*<BR>> following the WiMAX specs, and therefore people should buy *real* WiMAX<BR>> equipment.<BR><BR>> Alan DeKok.<BR><BR>Thank You very much. Vendor forces us to buy theirs "unique" TRIAS<BR>server aka radius. :) That costs several hundred thousands.<BR><BR>Anyway thanks to all of you for help.<BR><BR><BR><BR>-- <BR>?????????? ??????<BR>????? IP ?????????<BR>__________________<BR><BR>??? "Babilon - T", ???????????,<BR>?. ???????, ?-?? ?????? 8.<BR>????: (992 44) 600 00 83<BR>?????????: (992 918) 62 37 22<BR>??. ?????: <A href="mailto:maxim@babilon-t.tj" ymailto="mailto:maxim@babilon-t.tj">maxim@babilon-t.tj</A><BR><BR><BR><BR><BR>------------------------------<BR><BR>Message: 6<BR>Date: Mon, 18 May 2009 13:42:46 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: Re: Wimax + Freeradius<BR>To:
<A href="mailto:maxim@babilon-t.tj" ymailto="mailto:maxim@babilon-t.tj">maxim@babilon-t.tj</A>, FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:4A1149B6.2090402@deployingradius.com" ymailto="mailto:4A1149B6.2090402@deployingradius.com">4A1149B6.2090402@deployingradius.com</A>><BR>Content-Type: text/plain; charset=UTF-8<BR><BR>Maxim Vinnichenko wrote:<BR>> Thank You very much. Vendor forces us to buy theirs "unique" TRIAS<BR>> server aka radius. :) That costs several hundred thousands.<BR><BR> Dollars?<BR><BR> Odds are that their product is less functional than FreeRADIUS. It<BR>would likely be cheaper to figure out what the problem is, and to make<BR>FreeRADIUS inter-operate with the vendor.<BR><BR> And what
the vendor *really* meant is that they do *not* implement the<BR>standards, and they don't care. Why not buy equipment from a vendor<BR>that is interested in making *useful* products?<BR><BR> Alan DeKok.<BR><BR><BR>------------------------------<BR><BR>Message: 7<BR>Date: Mon, 18 May 2009 13:59:07 +0200<BR>From: Alan DeKok <<A href="mailto:aland@deployingradius.com" ymailto="mailto:aland@deployingradius.com">aland@deployingradius.com</A>><BR>Subject: FreeRADIUS Server Version 2.1.6 has been released<BR>To: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:4A114D8B.3090203@deployingradius.com" ymailto="mailto:4A114D8B.3090203@deployingradius.com">4A114D8B.3090203@deployingradius.com</A>><BR>Content-Type: text/plain;
charset=ISO-8859-1<BR><BR> The following is the change log. Thanks to everyone for testing the<BR>pre releases.<BR><BR><BR>FreeRADIUS 2.1.6 Mon May 18 10:00:00 CEST 2009; , urgency=medium<BR> Feature improvements<BR> * radclient exits with 0 on successful (accept / ack), and 1<BR> otherwise (no response / reject)<BR> * Added support for %{sql:UPDATE ..}, and insert/delete<BR> Patch from Arran Cudbard-Bell<BR> * Added sample "do not respond" policy. See raddb/policy.conf<BR> and raddb/sites-available/do_not_respond<BR> * Cleanups to Suse spec file from Norbert Wegener<BR> * New VSAs for Juniper from Bjorn Mork<BR> * Include more RFC dictionaries in the default install<BR> * More documentation for the WiMAX
module<BR> * Added "chase_referrals" and "rebind" configuration to <BR> rlm_ldap.<BR> This helps with Active Directory. See raddb/modules/ldap<BR> * Don't load pre/post-proxy if proxying is disabled.<BR> * Added %{md5:...}, which returns MD5 hash in hex.<BR> * Added configurable "retry_interval" and "poll_interval"<BR> for "detail" listeners.<BR> * Added "delete_mppe_keys" configuration option to rlm_wimax.<BR> Apparently some WiMAX clients misbehave when they see those<BR> keys.<BR> * Added experimental rlm_ruby from<BR> <A href="http://github.com/Antti/freeradius-server/tree/master"
target=_blank>http://github.com/Antti/freeradius-server/tree/master</A><BR> * Add Tunnel attributes to ldap.attrmap<BR> * Enable virtual servers to be reloaded on HUP. For now, only<BR> the "authorize", "authenticate", etc. processing sections are<BR> reloaded. Clients and "listen" sections are NOT reloaded.<BR> * Updated "radwatch" script to be more robust. See<BR> scripts/radwatch<BR> * Added certificate compatibility notes in raddb/certs/README,<BR> for compatibility with different operating systems. (i.e.<BR> Windows)<BR><BR> Bug fixes<BR> * Minor changes to allow building without VQP.<BR> * Minor fixes from John Center<BR> * Fixed raddebug
example<BR> * Don't crash when deleting attributes via unlang<BR> * Be friendlier to very fast clients<BR> * Updated the "detail" listener so that it only polls once,<BR> and not many times in a row, leaking memory each time...<BR> * Update comparison for Packet-Src-IP-Address (etc.) so that<BR> the operators other than '==' work.<BR> * Did autoconf magic to work around weird libtool bug<BR> * Make rlm_perl keep tags for tagged attributes in more<BR> situations<BR> * Update UID checking for radmin<BR> * Added "include_length" field for TTLS. It's needed for RFC<BR> compliance, but not (apparently) for interoperability.<BR><BR><BR>------------------------------<BR><BR>Message: 8<BR>Date: Mon, 18 May 2009
14:38:06 +0200<BR>From: "Laar van de, Johan, TNF" <<A href="mailto:Johan.van.de.Laar@tnf.nl" ymailto="mailto:Johan.van.de.Laar@tnf.nl">Johan.van.de.Laar@tnf.nl</A>><BR>Subject: RE: Module-Success-Message / Module-Failure-Message<BR>To: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID:<BR> <<A href="mailto:1389360D6F590C44A15A626176B599A21069F31B@SR-EXC-006-SON.internal.tnf.nl" ymailto="mailto:1389360D6F590C44A15A626176B599A21069F31B@SR-EXC-006-SON.internal.tnf.nl">1389360D6F590C44A15A626176B599A21069F31B@SR-EXC-006-SON.internal.tnf.nl</A>><BR> <BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>Ok, but there is no other variable available which can be used within a sql query in the Post-Auth section?<BR><BR>Thanks.<BR><BR>Johan
van de Laar<BR><BR><BR>-----Oorspronkelijk bericht-----<BR>Van: freeradius-users-bounces+johan.van.de.laar=<A href="mailto:tnf.nl@lists.freeradius.org" ymailto="mailto:tnf.nl@lists.freeradius.org">tnf.nl@lists.freeradius.org</A> [mailto:freeradius-users-bounces+johan.van.de.laar=<A href="mailto:tnf.nl@lists.freeradius.org" ymailto="mailto:tnf.nl@lists.freeradius.org">tnf.nl@lists.freeradius.org</A>] Namens Alan DeKok<BR>Verzonden: maandag 18 mei 2009 13:05<BR>Aan: FreeRadius users mailing list<BR>Onderwerp: Re: Module-Success-Message / Module-Failure-Message<BR><BR>Laar van de, Johan, TNF wrote:<BR>> My Question is, if this is relatively easy, how can I achieve this? <BR><BR> The log messages can be changed via source code edits.<BR><BR> This *could* be made configurable, but that also requires source code<BR>edits.<BR><BR> Alan DeKok.<BR>-<BR>List info/subscribe/unsubscribe? See <A href="http://www.freeradius.org/list/users.html"
target=_blank>http://www.freeradius.org/list/users.html</A><BR><BR><BR><BR>------------------------------<BR><BR>Message: 9<BR>Date: Mon, 18 May 2009 14:21:03 +0100<BR>From: "Jean F. Mousinho" <<A href="mailto:jean.mousinho@ist.utl.pt" ymailto="mailto:jean.mousinho@ist.utl.pt">jean.mousinho@ist.utl.pt</A>><BR>Subject: duplicate Identity received, freeradius behaviour?<BR>To: FreeRadius users mailing list<BR> <<A href="mailto:freeradius-users@lists.freeradius.org" ymailto="mailto:freeradius-users@lists.freeradius.org">freeradius-users@lists.freeradius.org</A>><BR>Message-ID: <<A href="mailto:1242652863.1410.26.camel@jemos-workd.ist.utl.pt" ymailto="mailto:1242652863.1410.26.camel@jemos-workd.ist.utl.pt">1242652863.1410.26.camel@jemos-workd.ist.utl.pt</A>><BR>Content-Type: text/plain<BR><BR>Hi,<BR><BR>I've noticed that on our radius server logs lots of "EAP state variable<BR>not found", after some packet dump analysis
(also -Xf) I've noticed that<BR>one of the cases that this happened was when some EAP Identity packets<BR>are duplicated during parallel authentications (I mean, when at least<BR>one session already began from the same client, and we're receiving<BR>duplicate ).<BR><BR>I've noticed that these duplicate packets come with just a little<BR>difference which is the Proxy-State, the duplicate packets then, in my<BR>opinion could be caused by some bad proxying implementation (client EAP<BR>Identity passing through 2 or more proxies?), or even bad load<BR>balancing.<BR><BR>Also, we did an upgrade of one of the two proxies connected to our home<BR>radius server and somehow noticed that the amount of EAP state errors<BR>was lower in the old version (1.1.7) than in the newer (2.1.3) (although<BR>its hard to confirm that).<BR><BR>I've tried to compare the code from 1.1.7 and 2.1.3 and didn't come to a<BR>clear conclusion if its there any special treatment to
duplicate proxied<BR>packets between 1.1.7 and 2.1.3 (while proxying).<BR><BR>Thanks for your time.<BR><BR>Jean F. Mousinho<BR><BR><BR><BR>------------------------------<BR><BR>-<BR>List info/subscribe/unsubscribe? See <A href="http://www.freeradius.org/list/users.html" target=_blank>http://www.freeradius.org/list/users.html</A><BR><BR><BR>End of Freeradius-Users Digest, Vol 49, Issue 74<BR>************************************************<BR></DIV></DIV></div><br>
</body></html>