I found the manual description. I was looking for a batch procedure.
Any chance an enhancement would allow client IPs be handled in a manner
similar to how NAS IPs are handled,
so a filename could be provided rather than putting each IP into the config
file?
We have dozens of Client IPs from each NAS provider.
e.g.
<Client IPLIST=<filename> >
</Client>
-- Brian
-----Original Message-----
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 03, 2000 4:46 PM
To: Brian Keefe; [EMAIL PROTECTED]
Subject: RE: (RADIATOR) IP Filtering
Hello Brian -
On Thu, 04 May 2000, Brian Keefe wrote:
> This helps alot, thanks!
>
> However, where does the manual describe how to put client IP addresses in
> the config file?
>
You are doing it already I'm sure.
# list Clients to listen to
<Client some.client.name>
Secret ....
....
</Client>
<Client xxx.xxx.xxx.xxx>
Secret ....
....
</Client>
You can specify the domain name or IP address for your Clients, but even if
you
use a domain name it will be translated internally to the IP address and all
radius requests that arrive are checked against the list of Clients. My
previous comment concerned the use of <Client DEFAULT>, which of course will
just process any radius request that arrives from anywhere.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
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.
