So the Linux box and the portmaster are running TCP/IP on their own
ethernet segment and are just happy as can be. I can easily telnet
from Linux to Portmaster, or even login via the Portmaster's console
and telnet, rlogin, ping, traceroute quite successfully to the Linux
box. Now, I want to install radius so we can authenticate our users from
the Linux box. So... I cheerfully grabbed the radius source from
ftp.livingston.com, compiled it, installed it as /etc/radiusd, created
the /etc/raddb directory ...all as per the radius.install file. The
radiusd daemon goes up without a hiccup. However, if I try and login
to the portmaster , I get an error to the effect of "*** Host unavailable ***"
Now I know the host is available, since I can telnet to it from the
portmaster's admin account. So what gives?
Here are some symptoms.
Acounts defined as netuser in the Livingston user table are dropped
straight into slip/ppp negotiation. That seems to work.
Accounts defined as login user return errors of host unavailable
as outlined above.
Radius does not seem to be authenticating anyone, but output
from radius -x indicates it is being sent information _only_
on accounts defined in the linvingston's user table. (ie,
nothing is returned or received when a different account is specified.
I've never setup a server like this before, so please bear with me on this.
All I want is for the exception of a few local accounts, all authentication
must be done via the radius server. Nuff said. If anyone out there who
has run radius under linux, could post some instructions on pitfalls to
avoid, it would be much appreciated. (I've been going by the radius.install
and setup.isp files, but this is a stumbling block)
Peter L. Buschman /|\ |.| .^. .--.
plbuschm@alpha.delta.edu \|/ ||| |~| `--.infonia!
http://www.delta.edu/~plbuschm Phi Mu Alpha `--'