[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cistron-radius
Subject:    Re: Handing out IP Ranges
From:       "Miquel van Smoorenburg" <miquels () cistron ! nl>
Date:       2004-12-15 17:47:29
Message-ID: cpptbh$ps1$1 () news ! cistron ! nl
[Download RAW message or body]

In article <s1c021e9.091@FLTG01.FLTG.COM>,
Greg De Ruyter <gregd@fltg.com> wrote:
> Hello everyone,
> 
> Hoping you can all help me out with a little problem I'm having.  Using Cistron \
> Radius 1.6.4 to hand out dynamic IP addresses.   I'm using the IP address \
> 204.18.2.0+ option with in radius to incrementally hand out IPs based on the \
> session number.

That's not how it works. The "+" means "add the value of the NAS-Port
attribute to the base IP address. It only works if you have a
single NAS with limited ports. If you have multiple NASes or more
ports than IP addresses it's not going to work.

> Problem is
> my ISP has allotted me 30 IPs(255.255.255.224 mask) and when I get to that 31st IP \
> address I'm going to run into problems.   
> Is there anyway to setup a stop IP?  Ex. Tell it that when it hits 204.18.2.30 stop \
> handing out IPs?

Nope, you're trying to use it for something it wasn't designed for.

> Also is there a way to setup the same group with multiple IP ranges like this?  For \
> ex. use 204.18.2.0/27 and then jump to 204.18.2.64/27 since my ISP has told me if I \
> need another block of addresses they cannot guarantee that they will be contiguous. \
> Another option would be to push the IP assignments off to a DHCP server but from \
> what I have read this is not possible.

A few possibilities:

1. Give your customers a static IP address
2. Ask your ISP if the equipment he uses has support for
   named pools on his side, so you can just send the name
   of a pool to be used as a radius attribute (this is very
   vendor- and setup dependent)
3. Switch to freeradius, it has IP pool support. It has its own
   problems though, inherent to /any/ server side pooling design:
   it uses accounting-stop records to "free" an assigned IP
   back into the pool, but if such an accounting-stop record
   gets corrupted or lost, the IP will stay allocated forever
   and your pool will slowly run out of IPs.

Mike.


- 
List info/subscribe/unsubscribe? See http://www.radius.cistron.nl/list/


[prev in list] [next in list] [prev in thread] [next in thread]