There appear to be problems with conflicting authentication

	packets when proxying synchronously.  For now, the work-around
	is to make proxying non-synchronous by default.

	based on input from VISP Systems Administration <support@visp.net>

diff --git a/raddb/proxy.conf b/raddb/proxy.conf
index 80969b1..9d35a8a 100644 (file)
--- a/raddb/proxy.conf
+++ b/raddb/proxy.conf
@@ -24,7 +24,7 @@ proxy server {
 #  sends it's retries to the server, then set this to 'yes', and
 #  set the other proxy configuration parameters to 0 (zero).
 #
-       synchronous = yes
+       synchronous = no
 
 #
 #  The time (in seconds) to wait for a response from the proxy, before

diff --git a/src/main/radiusd.c b/src/main/radiusd.c
index 44fe946..9d9b404 100644 (file)
--- a/src/main/radiusd.c
+++ b/src/main/radiusd.c
@@ -107,7 +107,7 @@ int acct_port;
 int proxy_port;
 int proxy_retry_delay = RETRY_DELAY;
 int proxy_retry_count = RETRY_COUNT;
-int proxy_synchronous = TRUE;
+int proxy_synchronous = FALSE;
 int need_reload = FALSE;
 struct main_config_t mainconfig;
 const char *radiusd_version = "FreeRADIUS Version " RADIUSD_VERSION ", for host " HOSTINFO ", built on " __DATE__ " at " __TIME__;
@@ -161,7 +161,7 @@ extern int rad_spawn_child(REQUEST *, RAD_REQUEST_FUNP);
 static CONF_PARSER proxy_config[] = {
        { "retry_delay",  PW_TYPE_INTEGER, 0, &proxy_retry_delay, Stringify(RETRY_DELAY) },
        { "retry_count",  PW_TYPE_INTEGER, 0, &proxy_retry_count, Stringify(RETRY_COUNT) },
-       { "synchronous",  PW_TYPE_BOOLEAN, 0, &proxy_synchronous, "yes" },
+       { "synchronous",  PW_TYPE_BOOLEAN, 0, &proxy_synchronous, "no" },
        { NULL, -1, 0, NULL, NULL }
 };