First off, I'll apologize for being overtired when I write this reply, so
hopefully I'm not way off base here.
If you were to add a ContinueUntilAccept in your realm, then it would go
into the users file, ultimately fail authentication and then fall over to
the passwd file. You could add a DefaultReply in there as well to send
those default items to the users, also NoDefaultIfFound might be useful
too.
In looking at your config file, you may want to have both of the AuthBy
clauses within the Realm as well?
Hopefully that'll get you going in the right direction. If you haven't
already, check the FAQ and the mailing list archives online too, they've
saved my life and lowered my blood pressure more than a few times.
Steve
On Fri, 9 Jun 2000, Chris wrote:
> If the users file dictates "System" for password, then radiator should
> then goto passwd file for authentication. The probelm I am having is:
>
> It authenticates with the word "System" instead of falling over to
> the passwd file.
>
> Here is what I have currently:
>
> <Realm DEFAULT>
> <AuthBy FILE>
> </AuthBy>
>
> </Realm>
> <AuthBy UNIX>
> Identifier System
> </AuthBy>
>
> ...and this in my users file
>
> DEFAULT Password = "System"
> Port-Limit = 1,
> User-Service-Type = Framed-User,
> Framed-Protocol = PPP,
> Framed-Address = 255.255.255.254,
> Framed-Netmask = 255.255.255.255,
> Framed-Routing = None,
> Idle-Timeout = 900,
> Framed-Compression = Van-Jacobsen-TCP-IP,
> Framed-MTU = 1500
>
>
> I am kind of new to the radius game, any help would be gladly taken. We are
> trying to implement this from our current Livingston radius. Im sure its
> something small that I am overlooking.
>
> Thanks,
>
> Chris
>
===
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.
