IP Grouping

George Innocent ginnocentus2002 at gmail.com
Mon Oct 8 21:06:14 CEST 2012


I had followed the clients file to group the IP's.

*# Grouped IP:*

client 10.250.0.0/31 { <http://10.250.0.0/31%7B>
         secret = grouping
        {

On doing the connection from the NAS it doesn't connect but when i test
using NAS'es having the full addresses without the grouping they connect
well.
The Full IP's ranges from 10.250.144.0- 10.250.189.9. This are very many
IP's to create single.

So one of my IP's will be :

client 10.250.144.6 {
secret = grouping
nastype= other
}


On Mon, Oct 8, 2012 at 9:40 PM, alan buxey <A.L.M.Buxey at lboro.ac.uk> wrote:

> Hi,
>
> >    I have a set of IP for my NAS and wish to group this together so i
> don't
> >    have to create a set of new ones on the clients.conf file every time
> a new
> >    NAS is created.
>
> well, the depends on whether these NASes can be grouped by their IP
> address - in which case
> they can be identified as one (or more) blocks of addresses within a
> subnet.
> see clients.conf original file for example).
>
> another way is to uas SQL to store the clients - and then you can use the
> dynamic clients
> module to check if they are NAS clients as they are added to the network
> without having
> to restart the server
>
> >    What's the best way to do this without causing a crash
>
> well, just adding new entries to clients.conf doesnt cause a crash.
>  restarting
> the RADIUS daemon after adding entries to clients.conf doesnt cause a
> crash (unless
> youve made a spectacular error in the config! ;-) )
>
> alan
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>



-- 
Regards:
George Innocent.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20121008/303964ae/attachment.html>


More information about the Freeradius-Users mailing list