Thanks Hugh for the help. I'll try what you recommended. One quickie:
> > <Realm DEFAULT>
> > <AuthBy FILE>
> > Filename /usr/adm/radius/users
> > AddToReply Service-Type=Framed-User,Framed-Protocol=PPP
> > </AuthBy>
> > <AuthBy UNIX>
> > Identifier System
> > Filename /etc/master.passwd
> > AddToReply Service-Type=Framed-User,Framed-Protocol=PPP
> > </AuthBy>
> >
> >
> > Thanks for the help! Looking to start using Radiator as soon as possible
> > and get off the older version we have :-)
> >
>
> The Realm DEFAULT above is a bit confusing, as the AuthBy UNIX will be called
> twice. As a general rule, it is preferable to define your AuthBy clauses first
> with Identifiers, then refer to them in your Realms and so on by Identifer.
> This makes configuration files *much* easier to understand.
I guess I thought I had to do it this way, because first I want Radiator
to check the users file to see if the user exists, and if not, just check
the /etc/master.password file to authenticate. Mainly because the only
reason we have people in the users file is to give them special
attributes, like dual channel or a static IP or whatever, you know?
Otherwise they are not in there at all and they are only in the
/etc/master.passwd file.
Thanks again,
Dan
===
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.
