I saw that, but the "home_server example below", does not mention anything about retry_count or retry_delay. Any simply putting retry_count = <value> in the home_server section dosn't seem to have any effect. So how are these values set for home servers? - Murray On Fri, Jul 16, 2010 at 1:54 PM, Alan DeKok <aland@deployingradius.com>wrote:

Murray Long wrote:

...

Does anyone know how to set the retry_count and retry_delay values for home servers?

Read raddb/proxy.conf:

# i.e. "retry_delay" and "retry_count" have been replaced # with per-home-server configuration. See the "home_server" # example below for details. #

Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

I'm trying to integrate with Ipass and they have asked for a 12 second or more delay between retry attempts. The default behavior for freeradius seems to be sending 3 retries every 5 secs, which is why I've been trying to change it. As I only have a single home-server for the realm i don't mind applying the change to either the realm or the home-server, but I havn't been able to figure out how to do either. Am I going about this the wrong way? Thanks, Murray On Fri, Jul 16, 2010 at 2:06 PM, Alan DeKok <aland@deployingradius.com> wrote:

Murray Long wrote:

...

I saw that, but the "home_server example below", does not mention anything about retry_count or retry_delay.

 Because this is documented in proxy.conf:

       #        #  Note that as of 2.0, the "synchronous", "retry_delay",        #  "retry_count", and "dead_time" have all been deprecated.        #  For backwards compatibility, they are are still accepted        #  by the server, but they ONLY apply to the old-style realm        #  configuration.  i.e. realms with "authhost" and/or "accthost"        #  entries.

...

Any simply putting retry_count = <value> in the home_server section dosn't seem to have any effect.

So how are these values set for home servers?

 You don't.  The configuration entries that work are documented in proxy.conf.

 Why do you want to set "retry_delay" and "retry_count" for a home server?  If you think you need them, see the above documentation.  You can still set them for realms.  But for the new home_server configuration, the new method is better and more stable.

 Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Oh, that makes more sense now. My confusion was in assuming that the retry packets I was seeing where generated by freeradius when they where actually just being forwarded from the NAS. Thanks very much for the help, -Murray On Fri, Jul 16, 2010 at 2:55 PM, Alan DeKok <aland@deployingradius.com> wrote:

Murray Long wrote:

...

I'm trying to integrate with Ipass and they have asked for a 12 second or more delay between retry attempts.   The default behavior for freeradius seems to be sending 3 retries every 5 secs, which is why I've been trying to change it.

 No.  The default behavior for the *NAS* is to send 3 retries every 5 seconds.  FreeRADIUS just passes those packets along to the home server.

...

As I only have a single home-server for the realm i don't mind applying the change to either the realm or the home-server, but I havn't been able to figure out how to do either.

Am I going about this the wrong way?

 I don't see what is unclear about the documentation.

1) you can still set retry_delay and retry_count

2) just as with 1.x

3) in the same place in the config files as with 1.x

4) those 2 configuration items will only apply to old-style realms

5) old-style realms have "authhost" and "accthost"

6) so... configure retry_delay and retry_count as you did with 1.x

7) configure a realm as you did with 1.x

8) it *will* work

 Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Murray Long wrote:

Oh sorry it does! But only for server type "coa",

No. The irt/mrt/etc. configurations for CoA are *completely* different.

Are they not supported for the other types?

Have you been reading my messages? Alan DeKok.