(RADIATOR) IP Filters

[Hugh Irvine]

Hello Todd -

The correct way to deal with this is with a suitable Identifier in 
each Client clause and one or more hooks to return the correct reply 
attributes for each type of NAS. There are some example hooks in the 
file "goodies/hooks.txt" which do similar things.

Ie:

# define Client clauses

<Client .....>
	Identifier Cisco
	.....
</Client>

<Client .....>
	Identifier Ascend
	.....
</Client>

<Client .....>
	Identifier USR
	.....
</Client>


hth

Hugh


At 14:22 -0700 01/8/3, Todd Dokey wrote:
>In the Radiator manual it mentions the USR Ip filter to take down IP
>spoofing.
>
>If I include this (and hopefully there is a similar one for Ascend) in the
>users file..
>
>What happens if the user uses the opposite modem type?
>
>In other words.. if an Ascend dials up and there is the USR attribute.. will
>it just ignore the USR IP Filter string?
>
>===
>Archive at http://www.open.com.au/archives/radiator/
>Announcements on radiator-announce at open.com.au
>To unsubscribe, email 'majordomo at open.com.au' with
>'unsubscribe radiator' in the body of the message.

-- 

NB: I am travelling this week, so there may be delays in our correspondence.

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.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.