[Bug-gnu-radius] Patch proposal: usage of netmasks in naslist config file

[Maurice Makaay]

Hi,

The naslist file can contain a "DEFAULT" entry, which will catch all
non matching NASes. This is quite handy, but we could use a bit more
control over grouping NASes. Our radius servers get requests from
a lot of different NASes, from different infrastructures. To keep the
radacct directory a bit clean, we use the nickname in the naslist to
structurize this directory (so radius requests from multiple NASses will
be logged in the same directory). However, there are so many NASes, that the
naslist file grows very large. Moreover, new NASses appear once in a while,
which means that we regularly have to add these to the naslist.

Using the attached patch, the naslist can contain not only IP-addresses but
also netmasks in CIDR notation (e.g. /32 or /24). This solves our problems.
The naslist is now very short and new NASses almost always appear in an
already defined subnet. An example naslist could be:

127.0.0.1       local           true
192.168.0.0/24  private-1       true
192.168.1.0/24  private-2       true
192.168.2.5     private-2       true
172.16.0.0/24   private-3       true
172.16.10.0/24  private-3       true

It would be great if this patch could be added to gnu-radius.

Regards,

-- Maurice Makaay

P.S. The patch I sent earlier this day for SEGFAULTING on having no
     nastype in a naslist entry is also included in this patch.

CVS-patch-naslist-netmask
Description: Text document