the clients.conf to be xlat'ed?
tariq
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Nicolas Baradakis
Sent: 13 September 2005 18:08
To: FreeRadius users mailing list
Subject: Re: custom variable in config files
Tariq Rashid wrote:
but this doesn't
Tariq Rashid [EMAIL PROTECTED] wrote:
i'd like to do something like ...
realm abc.def {
type= radius
authhost= `%{config:network_address}`.126:1812
The expansion of configuration-file variables is not the same as the
expansion of
trying and report back anything that works.
tariq
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Alan
DeKok
Sent: 15 September 2005 17:18
To: FreeRadius users mailing list
Subject: Re: custom variable in config files
Tariq Rashid [EMAIL PROTECTED] wrote
Tariq Rashid [EMAIL PROTECTED] wrote:
thanks for the suggestion and clarification. trying what you suggested gives
me ...
Config: including file: /opt/freeradius102/etc/raddb/proxy.conf
config: No such entry network_address for string
${network_address}.126:1812
thanks - that works - i can confirm that for the list
tariq
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Nicolas Baradakis
Sent: 13 September 2005 18:08
To: FreeRadius users mailing list
Subject: Re: custom variable in config files
Tariq Rashid
ok - i've worked out how to do this wityh {config:var_name} where var_name can
be declared in radiusd.conf or an included file.
the %{config:var_name} can be used in a users file easily - in the reply
attibutes, in the password condition test too .. but not in the user name...
so this works
6 matches
Mail list logo