Rejected proxy requests not making it to the client

Ti Leggett leggett at
Tue Jul 2 19:38:12 CEST 2013

I'm not sure how the script could be blocking the server after it's already ran and returned the updated packet so the proxying can take place which does happen:

	• rlm_perl: Changing User-Name: leggett at
	• rlm_perl: Added pair NAS-Port-Type = Virtual
	• rlm_perl: Added pair Service-Type = Authenticate-Only
	• rlm_perl: Added pair Auth-Type = System
	• rlm_perl: Added pair Calling-Station-Id =
	• rlm_perl: Added pair User-Name = leggett at
	• rlm_perl: Added pair User-Password = 654321
	• rlm_perl: Added pair NAS-Identifier = sshd
	• rlm_perl: Added pair Stripped-User-Name = leggett
	• rlm_perl: Added pair NAS-IP-Address =
	• rlm_perl: Added pair NAS-Port = 32448
	• rlm_perl: Added pair Ldap-UserDn = uid=leggett,ou=people,dc=mcs,dc=example,dc=com
	• Cached username is "leggett at", list username is "leggett at"
	• ++[get_domain] returns updated
	• [suffix] Looking up realm "" for User-Name = "leggett at"
	• [suffix] Found realm ""
	• [suffix] Adding Stripped-User-Name = "leggett"
	• [suffix] Adding Realm = ""
	• [suffix] Proxying request from user leggett to realm
	• [suffix] Preparing to proxy authentication request to realm ""
	• Cached username is "leggett", list username is "leggett at"
	• ++[suffix] returns updated

The request packet then gets proxied off, comes back and this script is never called again. The same script gets called the same way on successful requests and this script is only called in the authorize phase. I've also tested that when one of the failure cases is reached (return RLM_MODULE_FAIL) that a fail packet is sent back to the client and no proxying ever takes place which is what I would expect.

The script is at

On Jul 2, 2013, at 12:20 PM, Alan DeKok <aland at> wrote:

> Ti Leggett wrote:
>> Tue Jul  2 10:39:04 2013 : Error: WARNING: Unresponsive child for request 0, in component <core> module <thread>
>  Fix your scripts so that they don't block the server.
>> The upstream server does get the request, send the reject back to the proxy and the proxy receives the reject but doesn't seem to send the reject back to the client. When the user types the password successfully everything works fine - the client gets an OK and none of the hung request errors show up.
>  The default configuration doesn't have this issue.  Access-Requests
> can be proxied.  Access-Rejects can be returned through a proxy to a client.
>> A debug log of one of these failed sessions is at Any ideas what might be going on?
>  The debug log shows nothing interesting.
>  The most probable issue is that your scripts are blocking the server.
> Fix that.
>  You can verify this by configuring a test system *without* your
> scripts.  Or a test user, which bypasses the scripts.  It will work.
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See

More information about the Freeradius-Users mailing list