(RADIATOR) Client - group by subnet

[Mike McCauley]

Hello Bjoern,

After much further consideration, we have just added CIDR address 
specification support for Clients.

You can now have optional CIDR masks, for example:

<Client 203.63.154.0/24>

or 
<Client 127.0.0.0.1/32>

etc.

The support is now in the latest patch set.
Please let us know if it works for you. Feedback to me please.

Cheers.

On Wednesday 04 June 2008 21:02, you wrote:
> On Wed, 4 Jun 2008, Hugh Irvine wrote:
>
> Hi Hugh,
>
> > We've looked at this several times, but we haven't been able to come up
> > with a suitable solution.
> >
> > The problem is unbounded memory usage if the Client definition isn't done
> > correctly, and we consider this an unacceptable possibility.
>
> Can you elaborate on this? In what way could a Client definition use
> unlimited amounts of memory?
>
> Would the problem be like if someone accidentally gives a /2 instead
> of a /24 and you'd then explode that to a list of single addresses?
> Or is it something different maybe affecting runtime?
>
>
> Regards,
> Bjoern

-- 
Mike McCauley                               mikem at open.com.au
Open System Consultants Pty. Ltd            Unix, Perl, Motif, C++, WWW
9 Bulbul Place Currumbin Waters QLD 4223 Australia   http://www.open.com.au
Phone +61 7 5598-7474                       Fax   +61 7 5598-7070

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX etc on Unix, Windows, MacOS, NetWare etc.

--
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.