December 2006 - Freeradius-Devel - lists.freeradius.org

Reemission bug in multi-threaded mode - FreeRADIUS does not wake up properly
by Chaigneau Nicolas 12 Jan '07

12 Jan '07

FreeRADIUS 1.1.3 - Reemission bug in multi-threaded mode - FreeRADIUS does not wake up properly When receiving a request to proxy, FreeRADIUS should wake up in (at most) the proxied request retransmission delay parameter. This does not work. Note that in the case of the NAS reemitting the request, the problem does not appear, because when receiving new requests, FreeRADIUS wakes up and process its request list. The problem happens when a request is received, the request has to be proxied, but the NAS does not reemit (and no other request is received by FreeRADIUS from any NAS). The "wake up" delay is then set to 31 (probably max_request_time + 1) seconds instead of 5 (retry_delay), as we can see in debug mode: rad_recv: Accounting-Request packet from host *****:16384, id=233, length=53 Mon Nov 6 15:11:57 2006 : Debug: --- Walking the entire request list --- Mon Nov 6 15:11:57 2006 : Debug: Thread 4 got semaphore Mon Nov 6 15:11:57 2006 : Debug: Waking up in 31 seconds... Mon Nov 6 15:11:57 2006 : Debug: Thread 4 handling request 3, (1 handled so far) The behaviour is the same in normal (non debug) mode : the proxy server does only receive the request once, thus FreeRADIUS is not reemitting. In function refresh_request of file request_list.c, we should pass in the following condition : if (request->proxy && !request->proxy_reply) { ... (ie, request unfinished, but has been proxied and we are waiting for response from proxy server) It seems the condition is not met, so the next condition (ie, request unfinished but no proxy) is fulfilled. Thus, FreeRADIUS computes the time difference with: difference = (request->timestamp + mainconfig.max_request_time) - info->now; If FreeRADIUS is launched in single-thread mode (-X), the problem does not occur. It seems that "request->proxy" is 0 when the condition is tested, thus, FreeRADIUS considers there is no proxy outstanding for this request. From what I understand, when receiving a request, the thread that handles the list of requests wakes up, process its list and goes back to sleep. This thread finishes its work *before* the thread handling the request has proxied the request. This is the cause of the problem described above. Any hint as how to fix this ? (the problem is not critical: it appears on a test environment but will not happen in production, as a RADIUS server receives lots of requests) Should I log this in bugzilla ? Thanks. Best regards, Nicolas. ___________________________________________________________________________ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com

3 2

Need help in writing a radius client
by Abhinay Sinha 06 Jan '07

06 Jan '07

Hi, I am planning to write an ISP billing server and gateway which communicates with a RADIUS server for AAA work. Can anybody please help me with the following: 1. I need an open source library for client. I found radiusclient-ng. Is it sufficient for work. 2. Can anybody please help me find some better documentation for working me with the library, i.e. details regarding its API, cause the docs provided with the library are minimal? 3. Can I get some sample code for client anywhere? Thanks in advance Abhinay

4 3

RE: [rlm_ldap] chase_referrals option
by Wileczek Michaël 30 Dec '06

30 Dec '06

> From: "Sandworm" <sandworm(a)mepd.hush.com> > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Friday, 29 December 2006 1:36 AM, Wileczek MichaÃ«l wrote: > > > > Since i was fighting with authentication on a Microsoft Active > > Directory (bad idea, i know) using referrals , i added an option > in > > rlm_ldap to > > enable/disable referral chasing during ldap requests. > > > > Here is the proposed patch : > > > <snip> > > That's not really necessary. See > http://lists.freeradius.org/pipermail/freeradius-users/2004-October/037218.… > > SW Modifying /etc/openldap/ldap.conf is a general configuration parameter. With the patch i provided, the option is switchable at the rlm_ldap module instance, therefore it allow using rlm_ldap in a mixed directories scheme. Michaël Wileczek System engineer - Technical Operations !TO-MCP-SSPI-IU-IW http://www.atosorigin.com Atos Wordline is an Atos Origin company : www.atosorigin.com Ce message est strictement confidentiel. Son intégrité n'est pas assurée sur Internet. Le contenu de ce message ne peut engager la responsabilité du groupe Atos Origin. Si vous n'êtes pas destinataire du message, merci d'en avertir immédiatement l'expéditeur et de le détruire. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail is privileged and may contain confidential information intended only for the person(s) named above. If you receive this e-mail in error, please notify the sender immediately by telephone or return e-mail. Although the sender endeavours to maintain a computer virus free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

3 2

Re: Need help in writing a radius client
by Abhinay Sinha 29 Dec '06

29 Dec '06

Hi, Thanks for the comments. Anyways, I am not interested in radiusclient-ng specifically. I need a library to create a client to work with freeradius with some documentation of its API. On 12/29/06, Frank Cusack <fcusack(a)fcusack.com> wrote: > On December 29, 2006 2:07:09 AM +0530 Abhinay Sinha <sinhabhinay(a)gmail.com> > wrote: > > 1. I need an open source library for client. I found radiusclient-ng. > > Is it sufficient for work. > > Not sure why you are asking about non-freeradius software on a freeradius > mailing list. > > > 2. Can anybody please help me find some better documentation for > > working me with the library, i.e. details regarding its API, cause the > > docs provided with the library are minimal? > > Not sure why you are asking about non-freeradius software on a freeradius > mailing list. > > As to minimal docs, welcome to open source. > > > 3. Can I get some sample code for client anywhere? > > See radclient and radtest source in the freeradius distribution. Of > course this won't help you with radiusclient-ng. > > -frank > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html >

1 0

RE: [rlm_ldap] chase_referrals option
by Sandworm 29 Dec '06

29 Dec '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > On Friday, 29 December 2006 1:36 AM, Wileczek Michaël wrote: > > Since i was fighting with authentication on a Microsoft Active > Directory (bad idea, i know) using referrals , i added an option in > rlm_ldap to > enable/disable referral chasing during ldap requests. > > Here is the proposed patch : > <snip> That's not really necessary. See http://lists.freeradius.org/pipermail/freeradius-users/2004- October/037218.html SW -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.5 wkYEARECAAYFAkWUZIAACgkQmw4BJyaatJ3/qQCdER+kvVy+nYj0jh/aXSFq9xz2BmYA oIq+iZXExqJnq3X3nFmHtZjXDoRP =WX6x -----END PGP SIGNATURE-----

1 0

(no subject)
by Sandworm 29 Dec '06

29 Dec '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > On Friday, 29 December 2006 1:36 AM, Wileczek Michaël wrote: > > Since i was fighting with authentication on a Microsoft Active > Directory (bad idea, i know) using referrals , i added an option in > rlm_ldap to > enable/disable referral chasing during ldap requests. > > Here is the proposed patch : > <snip> That's not really necessary. See http://lists.freeradius.org/pipermail/freeradius-users/2004- October/037218.html SW -----BEGIN PGP SIGNATURE----- Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 2.5 wkYEARECAAYFAkWUZCAACgkQmw4BJyaatJ3NYACgiG2jhwnBJZ2RH1StHRhwl+x2rXQA oIBr6QRCVE8VSGA31//2A9zPUXp8 =+S8c -----END PGP SIGNATURE-----

1 0

[rlm_ldap] chase_referrals option
by Wileczek Michaël 28 Dec '06

28 Dec '06

Since i was fighting with authentication on a Microsoft Active Directory (bad idea, i know) using referrals , i added an option in rlm_ldap to enable/disable referral chasing during ldap requests. Here is the proposed patch : ===patch=== --- rlm_ldap.c Thu Dec 28 15:30:43 2006 +++ new_rlm_ldap.c Thu Dec 28 15:30:56 2006 @@ -270,6 +270,7 @@ struct timeval net_timeout; struct timeval timeout; int debug; + int chase_referrals; int tls_mode; int start_tls; int num_conns; @@ -326,6 +327,7 @@ /* allow server unlimited time for search (server-side limit) */ {"timelimit", PW_TYPE_INTEGER, offsetof(ldap_instance,timelimit), NULL, "20"}, {"identity", PW_TYPE_STRING_PTR, offsetof(ldap_instance,login), NULL, ""}, + {"chase_referrals", PW_TYPE_BOOLEAN, offsetof(ldap_instance,chase_referrals), NULL, "yes"}, {"tls_mode", PW_TYPE_BOOLEAN, offsetof(ldap_instance,tls_mode), NULL, "no"}, {"start_tls", PW_TYPE_BOOLEAN, offsetof(ldap_instance,start_tls), NULL, "no"}, {"tls_cacertfile", PW_TYPE_STRING_PTR, offsetof(ldap_instance,tls_cacertfile), NULL, NULL}, @@ -1972,6 +1974,15 @@ } if (ldap_set_option(ld, LDAP_OPT_NETWORK_TIMEOUT, (void *) &(inst->net_timeout)) != LDAP_OPT_SUCCESS) { radlog(L_ERR, "rlm_ldap: Could not set LDAP_OPT_NETWORK_TIMEOUT %ld.%ld", inst->net_timeout.tv_sec, inst->net_timeout.tv_usec); + } + if(inst->chase_referrals) { + rc=ldap_set_option(ld, LDAP_OPT_REFERRALS, LDAP_OPT_ON); + } else { + rc=ldap_set_option(ld, LDAP_OPT_REFERRALS, LDAP_OPT_OFF); + } + if (rc != LDAP_OPT_SUCCESS) { + ldap_get_option(ld, LDAP_OPT_ERROR_NUMBER, &ldap_errno); + radlog(L_ERR, "rlm_ldap: Could not set LDAP_OPT_REFERRALS %d %s", inst->chase_referrals, ldap_err2string(ldap_errno)); } if (ldap_set_option(ld, LDAP_OPT_TIMELIMIT, (void *) &(inst->timelimit)) != LDAP_OPT_SUCCESS) { radlog(L_ERR, "rlm_ldap: Could not set LDAP_OPT_TIMELIMIT %d", inst->timelimit); ===patch=== Michaël Wileczek System engineer - Technical Operations !TO-MCP-SSPI-IU-IW http://www.atosorigin.com Atos Wordline is an Atos Origin company : www.atosorigin.com Ce message est strictement confidentiel. Son intégrité n'est pas assurée sur Internet. Le contenu de ce message ne peut engager la responsabilité du groupe Atos Origin. Si vous n'êtes pas destinataire du message, merci d'en avertir immédiatement l'expéditeur et de le détruire. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail is privileged and may contain confidential information intended only for the person(s) named above. If you receive this e-mail in error, please notify the sender immediately by telephone or return e-mail. Although the sender endeavours to maintain a computer virus free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

1 0

Automatic report from sources (radiusd) between 18.12.2006 - 19.12.2006 GMT
by Automatic cvs log generator 19 Dec '06

19 Dec '06

CVS log entries from 18.12.2006 (Mon) 09:00:00 - 19.12.2006 (Tue) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/modules/rlm_pap/rlm_pap.c; Revisions: 1.15.2.2.2.2 File: radiusd/doc/ChangeLog; Revisions: 1.57.2.31.2.31 File: radiusd/raddb/radiusd.conf.in; Revisions: 1.188.2.4.2.14 File: radiusd/man/man5/rlm_pap.5; Revisions: 1.3.4.1 ===================================================== Combined list of identical log entries ===================================================== Description: Updated functionality for rlm_pap Modified files: File: radiusd/man/man5/rlm_pap.5; Revision: 1.3.4.1; Date: 2006/12/19 00:35:57; Author: aland; Lines: (+117 -10) File: radiusd/raddb/radiusd.conf.in; Revision: 1.188.2.4.2.14; Date: 2006/12/19 00:35:57; Author: aland; Lines: (+21 -8) File: radiusd/src/modules/rlm_pap/rlm_pap.c; Revision: 1.15.2.2.2.2; Date: 2006/12/19 00:35:58; Author: aland; Lines: (+667 -197) ===================================================== Log entries ===================================================== Description: Note changes to rlm_pap Modified files: File: radiusd/doc/ChangeLog; Revision: 1.57.2.31.2.31; Date: 2006/12/19 00:37:15; Author: aland; Lines: (+3 -1) ===================================================== Summary of modified files ===================================================== File: radiusd/doc/ChangeLog Revisions: 1.57.2.31.2.31 Authors: aland (+3 -1) ------------------------------- File: radiusd/man/man5/rlm_pap.5 Revisions: 1.3.4.1 Authors: aland (+117 -10) ------------------------------- File: radiusd/raddb/radiusd.conf.in Revisions: 1.188.2.4.2.14 Authors: aland (+21 -8) ------------------------------- File: radiusd/src/modules/rlm_pap/rlm_pap.c Revisions: 1.15.2.2.2.2 Authors: aland (+667 -197) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Help with Simultaneous Login on Freeradius+Ldap
by listasmw＠netconsult.inf.br 15 Dec '06

15 Dec '06

Hi, we are using FreeRadius 1.1.3 on Fedora Core 6 and the RLM_LDAP module, we're needing control simultaneous logins, eg. the ldap user "John" can authenticate only one time. When are monitoring the ldap users logins, they can log successfully in ldap, but we can't see or monitoring the users login in radutmp log file is empty with 0kb, when we execute the radwho command, it is empty but is opening. could you help me please? Regards, Maicon Wendhausen Freeradius Files Logs File: [root@firedap3 radius]# ls -la total 24 drwx------ 3 radiusd radiusd 4096 Dec 14 18:21 . drwxr-xr-x 10 root root 4096 Dec 14 19:06 .. drwx------ 3 radiusd radiusd 4096 Dec 14 19:55 radacct -rw------- 1 radiusd root 5357 Dec 14 20:03 radius.log -rw-r--r-- 1 radiusd root 0 Dec 14 18:21 radutmp -rw-r--r-- 1 radiusd root 0 Dec 14 18:21 radwtmp [root@firedap3 radius]# Log do Radius in Debug mode rad_recv: Access-Request packet from host 10.69.70.210:32771, id=87, length=63 User-Name = "user6" User-Password = "user6" NAS-IP-Address = 10.69.70.210 Service-Type = Authenticate-Only NAS-Port = 0 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 2 modcall[authorize]: module "chap" returns noop for request 2 modcall[authorize]: module "mschap" returns noop for request 2 rlm_realm: No '@' in User-Name = "user6", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 2 modcall[authorize]: module "digest" returns noop for request 2 users: Matched entry DEFAULT at line 222 modcall[authorize]: module "files" returns ok for request 2 rlm_ldap: - authorize rlm_ldap: performing user authorization for user6 radius_xlat: '(uid=user6)' radius_xlat: 'dc=nct,dc=com,dc=br' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in dc=nct,dc=com,dc=br, with filter (uid=user6) rlm_ldap: Added password {SSHA}f21M8OjksIKSJ1zUEii6JWKu43tWPRFgsBeiQg== in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: Setting Auth-Type = ldap rlm_ldap: user user6 authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module "ldap" returns ok for request 2 modcall: leaving group authorize (returns ok) for request 2 rad_check_password: Found Auth-Type ldap auth: type "LDAP" Processing the authenticate section of radiusd.conf modcall: entering group LDAP for request 2 rlm_ldap: - authenticate rlm_ldap: login attempt by "user6" with password "user6" rlm_ldap: user DN: uid=user6,dc=nct,dc=com,dc=br rlm_ldap: (re)connect to 10.69.70.25:389, authentication 1 rlm_ldap: could not set LDAP_OPT_X_TLS_REQUIRE_CERT option to allow rlm_ldap: bind as uid=user6,dc=nct,dc=com,dc=br/user6 to 10.69.70.25:389 rlm_ldap: waiting for bind result ... rlm_ldap: Bind was successful rlm_ldap: user user6 authenticated succesfully modcall[authenticate]: module "ldap" returns ok for request 2 modcall: leaving group LDAP (returns ok) for request 2 Processing the session section of radiusd.conf modcall: entering group session for request 2 radius_xlat: '/var/log/radius/radutmp' radius_xlat: 'user6' modcall[session]: module "radutmp" returns ok for request 2 modcall: leaving group session (returns ok) for request 2 Login OK: [user6] (from client firepass port 0) Sending Access-Accept of id 87 to 10.69.70.210 port 32771 Finished request 2 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... users file #...... DEFAULT Simultaneous-Use := 1 Fall-Through = 1 clients.conf file .... default configuration..... client 10.69.70.210 { secret = teste shortname = firepass } radiusd.conf prefix = /usr exec_prefix = /usr sysconfdir = /etc localstatedir = /var sbindir = /usr/sbin logdir = ${localstatedir}/log/radius raddbdir = ${sysconfdir}/raddb radacctdir = ${logdir}/radacct confdir = ${raddbdir} run_dir = ${localstatedir}/run/radiusd log_file = ${logdir}/radius.log libdir = ${exec_prefix}/lib pidfile = ${run_dir}/radiusd.pid max_request_time = 30 delete_blocked_requests = no cleanup_delay = 5 max_requests = 1024 bind_address = * port = 0 hostname_lookups = no allow_core_dumps = no regular_expressions = yes extended_expressions = yes log_stripped_names = no log_auth = yes log_auth_badpass = no log_auth_goodpass = no usercollide = no lower_user = no lower_pass = no nospace_user = no nospace_pass = no checkrad = ${sbindir}/checkrad security { max_attributes = 200 reject_delay = 1 status_server = yes } proxy_requests = yes $INCLUDE ${confdir}/proxy.conf $INCLUDE ${confdir}/clients.conf snmp = no $INCLUDE ${confdir}/snmp.conf thread pool { start_servers = 5 max_servers = 32 min_spare_servers = 3 max_spare_servers = 10 max_requests_per_server = 0 } modules { radutmp { filename = ${logdir}/radutmp ## username = "(uid=%{Stripped-User-Name:-%{User-Name}})" username = %{User-Name} case_sensitive = "yes" check_with_nas = "yes" perm = "0644" callerid = "no" } pap { encryption_scheme = crypt } chap { authtype = CHAP } #$INCLUDE ${confdir}/eap.conf mschap { authtype = MS-CHAP use_mppe = yes require_encryption = yes require_strong = no } ldap { server="10.69.70.25" identity="uid=gged,dc=nct,dc=com,dc=br" password=ged basedn="dc=nct,dc=com,dc=br" filter = (uid=%{Stripped-User-Name:-%{User-Name}}) ## filter= (uid=gged,dc=nct,dc=com,dc=br) password_attribute = userPassword dictionary_mapping = ${raddbdir}/ldap.attrmap ldap_cache_timeout = 150 ldap_cache_size = 0 ldap_connections_number = 1 timeout = 3 timelimit = 5 net_timeout = 1 compare_check_items = no } realm suffix { format = suffix delimiter = "@" } realm realmpercent { format = suffix delimiter = "%" ignore_default = no ignore_null = no } preprocess { huntgroups = ${confdir}/huntgroups hints = ${confdir}/hints with_ascend_hack = no ascend_channels_per_line = 23 with_ntdomain_hack = no with_specialix_jetstream_hack = no with_cisco_vsa_hack = yes } files { usersfile = ${confdir}/users acctusersfile = ${confdir}/acct_users compat = no } detail { detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d detailperm = 0600 } acct_unique { #key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port" key = "User-Name, Acct-Session-Id, NAS-IP-Address" } radutmp sradutmp { filename = ${logdir}/sradutmp perm = 0644 callerid = "no" } attr_filter { attrsfile = ${confdir}/attrs } counter daily { filename = ${raddbdir}/db.daily key = User-Name count-attribute = Acct-Session-Time reset = daily counter-name = Daily-Session-Time check-name = Max-Daily-Session allowed-servicetype = Framed-User cache-size = 5000 } always fail { rcode = fail } always reject { rcode = reject } always ok { rcode = ok simulcount = 0 mpp = no } expr { } digest { } exec { wait = yes input_pairs = request } exec echo { wait = yes program = "/bin/echo %{User-Name}" input_pairs = request output_pairs = reply } ippool main_pool { range-start = 192.168.1.1 range-stop = 192.168.3.254 netmask = 255.255.255.0 cache-size = 800 session-db = ${raddbdir}/db.ippool ip-index = ${raddbdir}/db.ipindex override = no maximum-timeout = 0 } } instantiate { exec expr # daily } authorize { #preprocess # auth_log # attr_filter chap mschap suffix digest # ntdomain #eap # Read the 'users' file files ldap # daily # checkval } authenticate { Auth-Type PAP { pap ldap } Auth-Type CHAP { chap ldap } Auth-Type MS-CHAP { mschap ldap } Auth-Type LDAP { ldap } } preacct { preprocess acct_unique suffix # Read the 'acct_users' file #files } accounting { detail # daily # # For Simultaneous-Use tracking. # radutmp # sradutmp # main_pool } session { radutmp # sql } post-auth { } pre-proxy { } post-proxy { }

1 0

Automatic report from sources (radiusd) between 14.12.2006 - 15.12.2006 GMT
by Automatic cvs log generator 15 Dec '06

15 Dec '06

CVS log entries from 14.12.2006 (Thu) 09:00:01 - 15.12.2006 (Fri) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: nbk File: radiusd/src/lib/udpfromto.c; Revisions: 1.9 File: radiusd/src/main/smux.c; Revisions: 1.21 ===================================================== Log entries ===================================================== Description: Include "autoconf.h" before testing the macro WITH_UDPFROMTO. Modified files: File: radiusd/src/lib/udpfromto.c; Revision: 1.9; Date: 2006/12/14 14:20:01; Author: nbk; Lines: (+4 -4) ------------------------------- Description: Include "autoconf.h" before testing the macro WITH_SNMP. Modified files: File: radiusd/src/main/smux.c; Revision: 1.21; Date: 2006/12/14 14:20:36; Author: nbk; Lines: (+3 -4) ===================================================== Summary of modified files ===================================================== File: radiusd/src/lib/udpfromto.c Revisions: 1.9 Authors: nbk (+4 -4) ------------------------------- File: radiusd/src/main/smux.c Revisions: 1.21 Authors: nbk (+3 -4) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Latest cvs debian build with udpfromto and smux
by Joe Maimon 14 Dec '06

14 Dec '06

During linking udpfromto and smux were unresolved I brute forced it by placing a #define WITH_xxx 1 at the top of the source file. Apparently those two arent defined to 1 in autconf.h Is this something specific to me?

3 2

Automatic report from sources (radiusd) between 13.12.2006 - 14.12.2006 GMT
by Automatic cvs log generator 14 Dec '06

14 Dec '06

CVS log entries from 13.12.2006 (Wed) 09:00:01 - 14.12.2006 (Thu) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: pnixon File: radiusd/doc/DIFFS; Revisions: 1.5 ===================================================== Log entries ===================================================== Description: Fix list address Modified files: File: radiusd/doc/DIFFS; Revision: 1.5; Date: 2006/12/13 13:33:34; Author: pnixon; Lines: (+1 -1) ===================================================== Summary of modified files ===================================================== File: radiusd/doc/DIFFS Revisions: 1.5 Authors: pnixon (+1 -1) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Automatic report from sources (radiusd) between 12.12.2006 - 13.12.2006 GMT
by Automatic cvs log generator 13 Dec '06

13 Dec '06

CVS log entries from 12.12.2006 (Tue) 09:00:01 - 13.12.2006 (Wed) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/main/threads.c; Revisions: 1.114 Author: pnixon File: radiusd/doc/examples/postgresql.sql; Revisions: 1.11, 1.1.2.7 File: radiusd/src/modules/rlm_sql/drivers/rlm_sql_postgresql/sql_postgresql.c; Revisions: 1.49, 1.48, 1.47 ===================================================== Log entries ===================================================== Description: Fix syntax typo Modified files: File: radiusd/doc/examples/postgresql.sql; Revision: 1.11; Date: 2006/12/12 12:08:48; Author: pnixon; Lines: (+2 -2) ------------------------------- Description: oops. invalid syntax.. Test things before you commit to cvs peter! Modified files: File: radiusd/doc/examples/postgresql.sql; Revision: 1.1.2.7; Date: 2006/12/12 12:10:30; Author: pnixon; Lines: (+2 -2) ------------------------------- Description: Fix stupid bug. rad_send() takes secret as second argument, listener->send takes REQUEST* Modified files: File: radiusd/src/main/threads.c; Revision: 1.114; Date: 2006/12/12 19:56:48; Author: aland; Lines: (+3 -3) ------------------------------- Description: Minor formatting cleanups. Modified files: File: radiusd/src/modules/rlm_sql/drivers/rlm_sql_postgresql/sql_postgresql.c; Revision: 1.49; Date: 2006/12/12 16:15:06; Author: pnixon; Lines: (+6 -8) ------------------------------- Description: Code is a bit clearer this way. Functionality should not change. Modified files: File: radiusd/src/modules/rlm_sql/drivers/rlm_sql_postgresql/sql_postgresql.c; Revision: 1.48; Date: 2006/12/12 16:03:38; Author: pnixon; Lines: (+4 -4) ------------------------------- Description: Fix a STUPID memory leak introduced by yours truely.. Modified files: File: radiusd/src/modules/rlm_sql/drivers/rlm_sql_postgresql/sql_postgresql.c; Revision: 1.47; Date: 2006/12/12 11:51:44; Author: pnixon; Lines: (+2 -5) ===================================================== Summary of modified files ===================================================== File: radiusd/doc/examples/postgresql.sql Revisions: 1.11, 1.1.2.7 Authors: pnixon (+2 -2), pnixon (+2 -2) ------------------------------- File: radiusd/src/main/threads.c Revisions: 1.114 Authors: aland (+3 -3) ------------------------------- File: radiusd/src/modules/rlm_sql/drivers/rlm_sql_postgresql/sql_postgresql.c Revisions: 1.49, 1.48, 1.47 Authors: pnixon (+6 -8), pnixon (+4 -4), pnixon (+2 -5) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Re: Memory Use
by Abdul Qadir 12 Dec '06

12 Dec '06

> With which sql backend? I am using Oracle 9. Message: 2 Date: Mon, 11 Dec 2006 11:49:37 +0200 From: Peter Nixon <listuser(a)peternixon.net> Subject: Re: memory use To: FreeRadius developers mailing list <freeradius-devel(a)lists.freeradius.org> Message-ID: <200612111149.43049.listuser(a)peternixon.net> Content-Type: text/plain; charset="iso-8859-15" On Mon 11 Dec 2006 06:28, Abdul Qadir wrote: > >Which modules are you using? There haven't been reports of memory > > leaks in the server for quite a while, so your configuration may be > > using parts of the server that no one else uses. > > I am using rlm_digest and rlm_sql With which sql backend? --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.

1 0

Re: memory use
by Abdul Qadir 11 Dec '06

11 Dec '06

>Which modules are you using? There haven't been reports of memory > leaks in the server for quite a while, so your configuration may be > using parts of the server that no one else uses. I am using rlm_digest and rlm_sql Message: 3 Date: Thu, 07 Dec 2006 19:58:35 -0800 From: Alan DeKok <aland(a)deployingradius.com> Subject: Memory use To: FreeRadius developers mailing list <freeradius-devel(a)lists.freeradius.org> Message-ID: <4578E2EB.5020904(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Abdul Qadir wrote: > This thing is very nice that server is doing caching. But i think its > still server's responsibilty to release all memory even the cache memroy > at time of exit. Ideally, yes. Patches are welcome. > Yes the memory keeps on growing, otherwise y I would be looking into > Valgrind logs and trying to find out whats wrong with the server. And > this leak becomes very clear when the number of requests become greater. Which modules are you using? There haven't been reports of memory leaks in the server for quite a while, so your configuration may be using parts of the server that no one else uses. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog --------------------------------- Any questions? Get answers on any topic at Yahoo! Answers. Try it now.

2 1

Automatic report from sources (radiusd) between 08.12.2006 - 09.12.2006 GMT
by Automatic cvs log generator 09 Dec '06

09 Dec '06

CVS log entries from 08.12.2006 (Fri) 09:00:01 - 09.12.2006 (Sat) 09:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/include/radius.h; Revisions: 1.66.4.3 File: radiusd/share/dictionary.freeradius.internal; Revisions: 1.6.2.6 ===================================================== Combined list of identical log entries ===================================================== Description: Defined Cleartext-Password and Password-With-Header, taken from the CVS head Modified files: File: radiusd/share/dictionary.freeradius.internal; Revision: 1.6.2.6; Date: 2006/12/09 00:17:37; Author: aland; Lines: (+3 -1) File: radiusd/src/include/radius.h; Revision: 1.66.4.3; Date: 2006/12/09 00:17:36; Author: aland; Lines: (+3 -1) ===================================================== Log entries ===================================================== ===================================================== Summary of modified files ===================================================== File: radiusd/share/dictionary.freeradius.internal Revisions: 1.6.2.6 Authors: aland (+3 -1) ------------------------------- File: radiusd/src/include/radius.h Revisions: 1.66.4.3 Authors: aland (+3 -1) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Re: Re: accounting_reply_query (corrected)
by Alexander S. Holodny 08 Dec '06

08 Dec '06

> Why? Accounting-Response packets are empty. by RFC - may be; i've not read it. > Which NAS other than your patched PPPd supports this? If the answer > is "none", then the patch isn't useful to anyone other than you. don't know about NAS. but, i saw some radiusd configs, which uses servers ability to send "Accounting-Response" packets using EXEC module. that's why i thought, that "Accounting-Response" can be sent to NASes. and my patch makes it easy. one of them: ... exec kicker { wait = yes program = "/usr/bin/kicker %{User-Name} %{Acct-Status-Type}" input_pairs = request output_pairs = reply packet_type = Accounting-Request } accounting { sql kicker } ...

2 1

Re: Freeradius-Devel Digest, Vol 20, Issue 4
by Abdul Qadir 08 Dec '06

08 Dec '06

Hi, >The server caches requests and responses for a time, so if you kill > the server immediately after a response is sent, there may be many > requests and responses still in memory. This thing is very nice that server is doing caching. And I think there should be some limit on caching memory or its unlimited. I don't know exactly what it is. But i think its still server's responsibilty to release all memory even the cache memroy at time of exit. >i.e. memory *lost* while it is running is bad. Slow memory growth > over time is bad. The problems you're seeing are likely unimportant. The problem we are seeing is that the memory keeps on growing and growing, therefore we wrote some cron job which kills the server and restart it. But its not the right solution for a production system. >If you leave the server running, does it's total memory use grow over > time? If not, there's probably no memory leak. Yes the memory keeps on growing, otherwise why I would be looking into Valgrind logs and trying to find out whats wrong with the server. And this leak becomes very clear when the number of requests become greater. I thought it would some minor issue which can be fixed quickly, but it seems like some thing else, which need assistance from your side. Best Regards, Abdul Qadir Message: 6 Date: Thu, 07 Dec 2006 18:19:52 -0800 From: Alan DeKok Subject: Re: FreeRadius 1.1.3 Memory Leak To: FreeRadius developers mailing list Message-ID: <4578CBC8.1030907(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Abdul Qadir wrote: > Actually the problem is why this keeps on grwoing. If i start the > process and exit it the statistics are different If i send some > authentication request, the memory which is not freed by the process at > exit keeps on growing. Is there any solution for this. Please see the > difference below. The server caches requests and responses for a time, so if you kill the server immediately after a response is sent, there may be many requests and responses still in memory. i.e. memory *lost* while it is running is bad. Slow memory growth over time is bad. The problems you're seeing are likely unimportant. If you leave the server running, does it's total memory use grow over time? If not, there's probably no memory leak. 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/devel.html End of Freeradius-Devel Digest, Vol 20, Issue 4 *********************************************** --------------------------------- Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.

2 1

Re: Freeradius-Devel Digest, Vol 20, Issue 4
by Abdul Qadir 08 Dec '06

08 Dec '06

Hi, >The server caches requests and responses for a time, so if you kill > the server immediately after a response is sent, there may be many > requests and responses still in memory. This thing is very nice that server is doing caching. But i think its still server's responsibilty to release all memory even the cache memroy at time of exit. >If you leave the server running, does it's total memory use grow over > time? If not, there's probably no memory leak. Yes the memory keeps on growing, otherwise y I would be looking into Valgrind logs and trying to find out whats wrong with the server. And this leak becomes very clear when the number of requests become greater. Best Regards, Abdul Qadir ----------------------------- Message: 6 Date: Thu, 07 Dec 2006 18:19:52 -0800 From: Alan DeKok Subject: Re: FreeRadius 1.1.3 Memory Leak To: FreeRadius developers mailing list Message-ID: <4578CBC8.1030907(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Abdul Qadir wrote: > Actually the problem is why this keeps on grwoing. If i start the > process and exit it the statistics are different If i send some > authentication request, the memory which is not freed by the process at > exit keeps on growing. Is there any solution for this. Please see the > difference below. The server caches requests and responses for a time, so if you kill the server immediately after a response is sent, there may be many requests and responses still in memory. i.e. memory *lost* while it is running is bad. Slow memory growth over time is bad. The problems you're seeing are likely unimportant. If you leave the server running, does it's total memory use grow over time? If not, there's probably no memory leak. 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/devel.html End of Freeradius-Devel Digest, Vol 20, Issue 4 *********************************************** --------------------------------- Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.

2 1

Re: FreeRadius 1.1.3 Memory Leak
by Abdul Qadir 08 Dec '06

08 Dec '06

Hi, I agree with you that this memory is not freed when the process exit. Actually the problem is why this keeps on grwoing. If i start the process and exit it the statistics are different If i send some authentication request, the memory which is not freed by the process at exit keeps on growing. Is there any solution for this. Please see the difference below. This Paragraph show when no request was sent ==811== LEAK SUMMARY: ==811== definitely lost: 108 bytes in 7 blocks. ==811== possibly lost: 340 bytes in 5 blocks. ==811== still reachable: 1,353,886 bytes in 25,961 blocks. ==811== suppressed: 0 bytes in 0 blocks. ==811== Reachable blocks (those to which a pointer was found) are not shown. ==811== To see them, rerun with: --show-reachable=yes This Paragraph show when few authentication requests were sent. ==842== LEAK SUMMARY: ==842== definitely lost: 108 bytes in 7 blocks. ==842== possibly lost: 476 bytes in 7 blocks. ==842== still reachable: 1,353,950 bytes in 25,963 blocks. ==842== suppressed: 0 bytes in 0 blocks. ==842== Reachable blocks (those to which a pointer was found) are not shown. ==842== To see them, rerun with: --show-reachable=yes Best Regards, Abdul Qadir Message: 2 Date: Thu, 07 Dec 2006 01:47:54 -0800 From: Alan DeKok Subject: Re: FreeRadius 1.1.3 Memory Leak To: FreeRadius developers mailing list Message-ID: <4577E34A.8070203(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Abdul Qadir wrote: > Hi, > > I just configured radius 1.1.3 and found that there are some memory > leaks in it. > > Here is the output of Valgrind i.e. memory is not free'd when the process exits. This is not a "memory leak" that will affect anything. The only reason to fix these issues is to prevent valgrind from complaining about them. 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/devel.html End of Freeradius-Devel Digest, Vol 20, Issue 3 *********************************************** --------------------------------- Any questions? Get answers on any topic at Yahoo! Answers. Try it now.

2 1

accounting_reply_query (corrected)
by halic 07 Dec '06

07 Dec '06

my previous message incuded one stupid error. sorry. here is corrected one. this is a simple patch to rlm_sql module. it allows module to get attributes from db and send them in Accounting-Response packet. "select-query" configured via default sql.conf; parameter is accounting_reply_query. it is useful to, for example, send "vendor-specific-drop" attribute to NAS in response to Interim-Update. other accounting_*_query parameters may not be defined. configuration example: accounting_reply_query="select id, login as UserName, 'Terminate-Session' as Attribute, 'Yes' as Value, '=' as op from clients where ballance <= 0 and '%{Acct-Status-Type}' = 'Interim-Update' and login = '%{User-Name}'" creating db-view is also a good choise; query like: accounting_reply_query="select id, UserName, Attribute, Value, op from acct_reply status_type = '%{Acct-Status-Type}' and UserName = '%{User-Name}'" my patched pppd recieves "Terminate-Session" attribute. mpd can also receive "Drop-User" attr. currenty a lot of billing systems use different nas-specific scripts to drop client with negative ballance. i think this patch is pretty usefull. sorry, but it's patch to 1.1.3 version; not devel, from cvs. due to bad internet i didnt downloaded cvs version. here it is: diff -urN freeradius-1.1.3/src/modules/rlm_sql/conf.h freeradius-1.1.3-oops/src/modules/rlm_sql/conf.h --- freeradius-1.1.3/src/modules/rlm_sql/conf.h Sat May 20 12:44:37 2006 +++ freeradius-1.1.3-oops/src/modules/rlm_sql/conf.h Wed Dec 6 21:56:15 2006 @@ -29,6 +29,7 @@ char *accounting_start_query_alt; char *accounting_stop_query; char *accounting_stop_query_alt; + char *accounting_reply_query; char *simul_count_query; char *simul_verify_query; char *groupmemb_query; diff -urN freeradius-1.1.3/src/modules/rlm_sql/rlm_sql.c freeradius-1.1.3-oops/src/modules/rlm_sql/rlm_sql.c --- freeradius-1.1.3/src/modules/rlm_sql/rlm_sql.c Sat May 20 12:44:37 2006 +++ freeradius-1.1.3-oops/src/modules/rlm_sql/rlm_sql.c Wed Dec 6 22:03:35 2006 @@ -103,6 +103,8 @@ offsetof(SQL_CONFIG,accounting_stop_query), NULL, ""}, {"accounting_stop_query_alt", PW_TYPE_STRING_PTR, offsetof(SQL_CONFIG,accounting_stop_query_alt), NULL, ""}, + {"accounting_reply_query", PW_TYPE_STRING_PTR, + offsetof(SQL_CONFIG,accounting_reply_query), NULL, ""}, {"group_membership_query", PW_TYPE_STRING_PTR, offsetof(SQL_CONFIG,groupmemb_query), NULL, ""}, {"connect_failure_retry_delay", PW_TYPE_INTEGER, @@ -887,6 +889,7 @@ char querystr[MAX_QUERY_LEN]; char logstr[MAX_QUERY_LEN]; char sqlusername[MAX_STRING_LEN]; + VALUE_PAIR *sql_reply = NULL; #ifdef CISCO_ACCOUNTING_HACK int acctsessiontime = 0; @@ -1103,6 +1106,19 @@ break; } + + radius_xlat(querystr, sizeof(querystr), inst->config->accounting_reply_query, request, sql_escape_func); + query_log(request, inst, querystr); + + if (*querystr) { + if(sqlsocket == NULL && (sqlsocket = sql_get_socket(inst)) == NULL) + return(RLM_MODULE_FAIL); + + sql_getvpdata(inst, sqlsocket, &sql_reply, querystr, PW_VP_USERDATA); + + pairxlatmove(request, &request->reply->vps, &sql_reply); + pairfree(&sql_reply); + } sql_release_socket(inst, sqlsocket);

2 1

accounting_reply_query
by halic 07 Dec '06

07 Dec '06

this is a simple patch to rlm_sql module. it allows module to get attributes from db and send them in Accounting-Response packet. "select-query" configured via default sql.conf; parameter is accounting_reply_query. it is useful to, for example, send "vendor-specific-drop" attribute to NAS in response to Interim-Update. other accounting_*_query parameters may not be defined. configuration example: accounting_reply_query="select id, login as UserName, 'Terminate-Session' as Attribute, 'Yes' as Value, '=' as op from clients where ballance <= 0 and '%{Acct-Status-Type}' = 'Interim-Update' and login = '%{User-Name}'" creating db-view is also a good choise; query like: accounting_reply_query="select id, UserName, Attribute, Value, op from acct_reply status_type = '%{Acct-Status-Type}' and UserName = '%{User-Name}'" my patched pppd recieves "Terminate-Session" attribute. mpd can also receive "Drop-User" attr. currenty a lot of billing systems use different nas-specific scripts to drop client with negative ballance. i think this patch is pretty usefull. sorry, but it's patch to 1.1.3 version; not devel, from cvs. due to bad internet i didnt downloaded cvs version. here it is: diff -urN freeradius-1.1.3/src/modules/rlm_sql/conf.h freeradius-1.1.3-oops/src/modules/rlm_sql/conf.h --- freeradius-1.1.3/src/modules/rlm_sql/conf.h Sat May 20 12:44:37 2006 +++ freeradius-1.1.3-oops/src/modules/rlm_sql/conf.h Wed Dec 6 21:56:15 2006 @@ -29,6 +29,7 @@ char *accounting_start_query_alt; char *accounting_stop_query; char *accounting_stop_query_alt; + char *accounting_reply_query; char *simul_count_query; char *simul_verify_query; char *groupmemb_query; diff -urN freeradius-1.1.3/src/modules/rlm_sql/rlm_sql.c freeradius-1.1.3-oops/src/modules/rlm_sql/rlm_sql.c --- freeradius-1.1.3/src/modules/rlm_sql/rlm_sql.c Sat May 20 12:44:37 2006 +++ freeradius-1.1.3-oops/src/modules/rlm_sql/rlm_sql.c Wed Dec 6 22:03:35 2006 @@ -103,6 +103,8 @@ offsetof(SQL_CONFIG,accounting_stop_query), NULL, ""}, {"accounting_stop_query_alt", PW_TYPE_STRING_PTR, offsetof(SQL_CONFIG,accounting_stop_query_alt), NULL, ""}, + {"accounting_reply_query", PW_TYPE_STRING_PTR, + offsetof(SQL_CONFIG,accounting_reply_query), NULL, ""}, {"group_membership_query", PW_TYPE_STRING_PTR, offsetof(SQL_CONFIG,groupmemb_query), NULL, ""}, {"connect_failure_retry_delay", PW_TYPE_INTEGER, @@ -887,6 +889,7 @@ char querystr[MAX_QUERY_LEN]; char logstr[MAX_QUERY_LEN]; char sqlusername[MAX_STRING_LEN]; + VALUE_PAIR *sql_reply = NULL; #ifdef CISCO_ACCOUNTING_HACK int acctsessiontime = 0; @@ -1103,6 +1106,19 @@ break; } + + radius_xlat(querystr, sizeof(querystr), inst->config->accounting_reply_query, request, sql_escape_func); + query_log(request, inst, querystr); + + if (*querystr) { + if(sqlsocket == NULL && (sqlsocket = sql_get_socket(inst)) == NULL) + return(RLM_MODULE_FAIL); + + sql_getvpdata(inst, sqlsocket, &sql_reply, "SELECT 4 as id, 'dayset' as UserName, 'Terminate-Session' as Attribute, 'Yes' as Value, '=' as op", PW_VP_USERDATA); + + pairxlatmove(request, &request->reply->vps, &sql_reply); + pairfree(&sql_reply); + } sql_release_socket(inst, sqlsocket);

2 1

FreeRadius 1.1.3 Memory Leak
by Abdul Qadir 07 Dec '06

07 Dec '06

Hi, I just configured radius 1.1.3 and found that there are some memory leaks in it. Here is the output of Valgrind ==30841== ERROR SUMMARY: 4365 errors from 82 contexts (suppressed: 44 from 2) ==30841== malloc/free: in use at exit: 1,354,452 bytes in 25,976 blocks. ==30841== malloc/free: 35,826 allocs, 9,850 frees, 3,185,516 bytes allocated. ==30841== For counts of detected errors, rerun with: -v ==30841== searching for pointers to 25,976 not-freed blocks. ==30841== checked 75,458,816 bytes. ==30841== ==30841== ==30841== 11 bytes in 1 blocks are possibly lost in loss record 12 of 93 ==30841== at 0x43BF53F: malloc (m_replacemalloc/vg_replace_malloc.c:149) ==30841== by 0x441F567: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x44200B1: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4420CB7: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4421881: lt_dlopenext (in /usr/lib/libltdl.so.3.1.0) ==30841== by 0x8052C5A: (within /usr/local/sbin/radiusd) ==30841== by 0x8052F66: find_module_instance (in /usr/local/sbin/radiusd) ==30841== by 0x8054564: (within /usr/local/sbin/radiusd) ==30841== by 0x805475B: compile_modsingle (in /usr/local/sbin/radiusd) ==30841== by 0x8053422: (within /usr/local/sbin/radiusd) ==30841== by 0x8053958: setup_modules (in /usr/local/sbin/radiusd) ==30841== by 0x805683D: main (in /usr/local/sbin/radiusd) ==30841== ==30841== ==30841== 97 bytes in 6 blocks are definitely lost in loss record 43 of 93 ==30841== at 0x43BF53F: malloc (m_replacemalloc/vg_replace_malloc.c:149) ==30841== by 0x441F567: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x44200B1: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4420CB7: (within /usr/lib/libltdl.so.3.1.0) ==30841== by 0x4421881: lt_dlopenext (in /usr/lib/libltdl.so.3.1.0) ==30841== by 0x8052C5A: (within /usr/local/sbin/radiusd) ==30841== by 0x8052F66: find_module_instance (in /usr/local/sbin/radiusd) ==30841== by 0x8054564: (within /usr/local/sbin/radiusd) ==30841== by 0x805475B: compile_modsingle (in /usr/local/sbin/radiusd) ==30841== by 0x8053422: (within /usr/local/sbin/radiusd) ==30841== by 0x8053958: setup_modules (in /usr/local/sbin/radiusd) ==30841== by 0x805683D: main (in /usr/local/sbin/radiusd) ==30841== ==30841== ==30841== 476 bytes in 7 blocks are possibly lost in loss record 68 of 93 ==30841== at 0x43C0C58: calloc (m_replacemalloc/vg_replace_malloc.c:279) ==30841== by 0x8464EA: _dl_allocate_tls (in /lib/ld-2.3.3.so) ==30841== by 0xAB978D: pthread_create@@GLIBC_2.1 (in /lib/tls/libpthread-2.3.3.so) ==30841== by 0x8059A3E: (within /usr/local/sbin/radiusd) ==30841== by 0x8059D20: thread_pool_init (in /usr/local/sbin/radiusd) ==30841== by 0x8056A8B: main (in /usr/local/sbin/radiusd) ==30841== ==30841== LEAK SUMMARY: ==30841== definitely lost: 97 bytes in 6 blocks. ==30841== possibly lost: 487 bytes in 8 blocks. ==30841== still reachable: 1,353,868 bytes in 25,962 blocks. ==30841== suppressed: 0 bytes in 0 blocks. ==30841== Reachable blocks (those to which a pointer was found) are not shown. ==30841== To see them, rerun with: --show-reachable=yes Can any one help me how to fix this.? Best Regards, Abdul Qadir --------------------------------- Need a quick answer? Get one in minutes from people who know. Ask your question on Yahoo! Answers.

2 1

Automatic report from sources (radiusd) between 03.12.2006 - 04.12.2006 GMT
by Automatic cvs log generator 04 Dec '06

04 Dec '06

CVS log entries from 03.12.2006 (Sun) 09:00:01 - 04.12.2006 (Mon) 09:00:04 GMT ===================================================== Summary by authors ===================================================== Author: bjordanov File: radiusd/src/modules/rlm_perl/rlm_perl.c; Revisions: 1.45 ===================================================== Log entries ===================================================== Description: Added new hash RAD_CONFIG Modified files: File: radiusd/src/modules/rlm_perl/rlm_perl.c; Revision: 1.45; Date: 2006/12/04 08:49:38; Author: bjordanov; Lines: (+8 -2) ===================================================== Summary of modified files ===================================================== File: radiusd/src/modules/rlm_perl/rlm_perl.c Revisions: 1.45 Authors: bjordanov (+8 -2) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0