November 2013 - Freeradius-Users - lists.freeradius.org

Version 2.2.2 has been released
by Alan DeKok 01 Nov '13

01 Nov '13

Changelog is below. It fixes all known problems in 2.2.1, and a few which weren't reported. Version 3.0.1 should be released soon as well. ---- FreeRADIUS 2.2.2 Wednesday 30 Oct 2013 9:30:00 DST, urgency=medium Feature improvements * Add "timeout" to exec, and "ntlm_auth_timeout" to mschap. So that run-away child processes are caught earlier. * Print out thread number for "unresponsive child". Bug fixes * Fix erroneous fall-through in "case" statements * Fix priority handling in new module handling code * Fix threading issue with Perl. Closes #436 * Fix EAP-TLS check_cert_issuer when X509v2 extensions existed. Patch from David Wood. * Fix pointer references in rlm_python. * Fix "unresponsive child" issue when proxying. * Set log output correctly when using -l. Fix ported from 3.0.0. * Buffer debug output when threaded, so that text from different threads isn't interspersed. * Fix SEGV in rlm_perl when using dynamic expansions. * Fix build for OSX Mavericks, which hid the header files in a magical place. * Port DHCP fixes from 3.0.

6 8

Please add me
by Chuck 01 Nov '13

01 Nov '13

So I may post. Thank you, Chuck

1 0

Still seeing WARNING: Child is hung after ... messages in 2.2.2
by Alex Sharaz 01 Nov '13

01 Nov '13

Hi, Just upgraded my development server to 2.2.2. It’s not heavily loaded but I’m now seeing the following which I didn’t see even in 2.2.1. Can;t remember, was that the problem that was fixed in 2.2.2 that was present in 2.2.1? Rgds Alex Fri Nov 1 15:38:49 2013 : Info: [<thread>] WARNING: Child is hung after "max_request_time" for request 165

3 4

LDAP-UserDn not populated? (Was: Re: Radius, LDAP and Openvpn)
by Andres Septer 01 Nov '13

01 Nov '13

> You need to read the documentation, and *understand* how FreeRADIUS > works. The alternative is random changes, confusion, upset users, and > *more* work and pain. > Skipped the idea to use different LDAP attributes for WiFi and OpenVPN altogether and turned to the LDAP groups. But my Ldap-UserDn attribute wont get populated (even though user is successfully authenticated in LDAP). So group search obviously fails When I manually insert my test users DN, everything works as expected. read the rlm_ldap manual but i still do not understand why my LDAP-UserDn is not populated. A.

2 4