Hi Jason.
On Apr 14, 2:28pm, Jason J. Horton wrote:
> Subject: (RADIATOR) <Client> doesn't seem to be working
> I have a ton of <Client w.x.y.z> statements in my radius.cfg
> file, but for some reason, all my requests fall thru to
> to teh <Client DEFAULT> statement. Is this a known bug?
> Anyone know what could be causing this?
Are the Client clauses in terms of DNS names or IP addresses?
If DNS names, it may be that you dont have reverse DNS set up for your NASs, so
Radiator cant figure out the Client clause from the IP address.
If you have IP addresses in the Client clauses, then it should work fine
regardless. Please send your config file (no secrets) and your radiator log
file a trace level 4, showing what happens when a request is received.
Cheers.
>
> -Jason J. Horton <[EMAIL PROTECTED]>
> Senior Network & Systems Engineer
> Intercom Online Inc.
> 212.378.2202 | http://www.intercom.com
>
>
> ===
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>-- End of excerpt from Jason J. Horton
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
