(RADIATOR)

[Hugh Irvine]

Hello Per -

We are of the opinion that it is actually preferable to define individual 
Client clauses for each device in the interests of control and security.

If you have large numbers of Client clauses, you should consider using the 
ClientListSQL clause and storing the definitions in an SQL database.

I have copied this mail to Mike in any case, and he may have other views.

regards

Hugh


On Wed, 10 Jul 2002 18:42, Per Lütkemeyer wrote:
> Hi Hugh,
>
> The function "IdenticalClients" strongly needs the possibility to use
> wildchar in specifying ip-adresses.
> I'm sure that others would appreciate this feature..
>
> - se my example :
>
> <Client 222-routers>
>         Identifier RouterLogin
>         Secret  Radius
>         IdenticalClients  192.162.222.1 192.162.222.2 192.162.222.3
> 192.162.222.4 192.162.222.5
>                                 192.162.223.6 192.162.223.7 192.162.223.8
> 192.162.223.9 192.162.223.3 </Client>
>
>
> The syntax could bee something like .....
>
> <Client 222-routers>
>         Identifier RouterLogin
>         Secret  Radius
>         IdenticalClients  192.162.222.* 192.162.223.*
> </Client>
>
> Would you  discuss this with development...?
>
>
> Regards
> Per Lütkemeyer
> DMdata a/s

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.