Hello Tim -
What you are seeing is the expected behaviour.
If you configure an AuthBy DYNADDRESS, it is expected to allocate an address - failure to do so is considered an error.
regards
Hugh
On Sunday, Jul 27, 2003, at 01:54 Australia/Melbourne, Timothy G. Wells wrote:
Hi All,
I have a situation where I set a Class reply item with the AuthSQL query then use that value as a PoolHint
��������������� PoolHint %{Reply:Class}
Here's the interesting part.
If the data retrieved from the db is NULL then radiator never claims to try to allocate an IP from the�� AddressPool. But if it is not NULL but it has a different value then any of the AddressPool names, I'm getting
No PoolHint found. No address will be allocated
Then it fails authentication.
Shouldn't it, if it doesn't see a PoolHint it likes just drop out and tell the NAS to just use one of its own?
Basically,
I have
��������AuthByPolicy��������������������ContinueWhileAccept
��������AuthBy��������������������������ModemSQL
�������
��������<AuthBy DYNADDRESS>
Timothy G. Wells, president����������������������������� 513-662-4443 x11
Good News Internet Services������������������������� fax 513-662-8461
[EMAIL PROTECTED] http://www.goodnews.net
This is the day the Lord has made;
let us rejoice and be glad in it. (Ps 118:24, NIV)
NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
