Hello Chris -
On Fri, 12 Nov 1999, Admin wrote:
> Thanks David. Our NAS is now using Radiator and all of the dial-ins are
> humming along.
>
> One thing that I've broken along the way is inbound telnet sessions, which I
> use from another office to manage the NAS. I assume this is because the
> default in my nt.cfg specifies that Radiator tells the NAS all incoming
> users are to use PPP. My telnet sessions work to the point of successful
> authentication and then telnet drops out altogether. I guess this is
> telnet's way of saying it doesn't talk PPP :)
>
>
> <Realm DUMMY_REALM>
> <AuthBy NT>
> Identifier System
> Domain ****
> DomainController
> DefaultReply Service-Type=Framed-User,Framed-Protocol=PPP
> </AuthBy>
> </Realm>
> ------
>
> and here's a snippet of my rac1 (user file) where I've tried to allow the
> username gpm_cc access via telnet:
>
> -----
>
> gpm_cc Auth-Type = System
> Service-Type = Login-User,
> Login-Service = Telnet
>
You should check what your NAS expects as reply attributes to allow you to log
in remotely. And check what attributes are in your Access-Request packets,
that may give you an indication of what you need to send back in the reply. Or
you can configure the telnet ports to not use radius.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
