SQLIPPOOL/IPPOOL prefix/range format

[rsg]

Thanks a lot for the reply and valuable suggestions Phil.

Sorry for the mistyped IP prefix: 10.0.0.0/16 would make sense I
guess. Could you think of the trouble if we are to have tables with
different subnets allocated to different networks.

Regards,
rg


On Mon, Mar 31, 2008 at 12:31 PM, Phil Mayers <p.mayers at imperial.ac.uk> wrote:
> rsg wrote:
>  > Hi,
>  >
>  > SQLIPPOOL requires, maintenance of an IP address table carrying individual IPs
>  >
>  > Is there a way to handle IP prefixes (prefix/range format) so that in
>  > large networks having many different networks could main and utilze
>  > this effectively.
>
>  Sure; write an "allocate-find" SQL query that does just that. You'd
>  probably need a stored procedure.
>
>  There's no native support for it in the module.
>
>
>  >
>  > For example it would be cumbersome if it happens to populate a table
>  > with each IP of 10.10.0.0/16.
>
>  Shrug. It's only 64k rows. I doubt it would be prohibitively expensive.
>
>
>  >
>  > The other query is how would it affect the performance if it happens
>  > to scan through the entire table during new ip assignment of a
>
>  The default SQL schemas for the radippool table are indexed. It won't do
>  a sequential scan, it'll fetch just one row.
>
>
>  > client(e.g. mobile device). On the contrary, Perl has Net::IP for
>  > handling ip prefixes which may be better in performance when it comes
>  > to large deployments.
>  >
>  > What is your opinion please ? Is there a way/module to handle this?
>  >
>  > Thanks a lot for your thoughts/assistance.
>  >
>  > rg
>  > -
>  > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
>  -
>  List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>