Hi Hugh,
The PoolHint in that case would come from the remote users file.
If I put the AuthByDynaddress before the AuthBy RADIUS is that
likely to work?
Is Authbydynaddress only going to work in a scenario where the
intiial auth check is done via an SQL system?
Thanks for the reply and help to date.
On Tue, 20 Jun 2000, Hugh Irvine wrote:
>
> 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
>
>
--
Dean Brandt
Technical Director
Cain Internet Services Pty Ltd
ACN 091949405
Ph 61-3-95231065
Satellite Access - $29.95 - no limits
===
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.
