Hello Dean -
On Tue, 20 Jun 2000, Dean Brandt wrote:
> Hi Hugh,
>
> The AuthByDynaddress is for a different realm, thats why it is
> placed where it is. This RADIUS server is acting as a primary for our
> service and as a "proxy" for a VISP scenario. We only want to allocate the
> DYNADDRESS stuff to the VISP, not us, our NAS allocates our users the
> right IP addresses. Does this clear up the *confusion*/ :)
>
Well actually no. Where is the PoolHint coming from in that case? And placing
an AuthBy DYNADDRESS after an AuthBy RADIUS won't work anyway as the AuthBy
RADIUS clause will Fork.
I suggest you rethink your strategy.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
