This is a discussion on Re: Global address pool within the FreeRADIUS Users forums, part of the Networking and Network Related category; --===============0282885323== Content-Type: multipart/alternative; boundary="----=_Part_61922_7824572.1165533998049" ------=_Part_61922_7824572.1165533998049 Content-Type: text/plain; charset=ISO-8859-1; ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============0282885323==
Content-Type: multipart/alternative; boundary="----=_Part_61922_7824572.1165533998049" ------=_Part_61922_7824572.1165533998049 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline from what I've seen on the lists, sqlippool is full of bugs and holes. If you're planning to put it into a production environment, I'd strongly suggest booking a coder for a couple of days :-) Such is the nature of open-source I guess. There is no other truly feasable way of leasing IPs over multiple servers, other than Rsync'ing the pool files, or manually assigning different RADIUS servers for different pools - the second means that you are basically splitting your system into multiple independent groups - several NASes to one RADIUS server. However, both of these are hacks. I'm using rlm_ippool at the moment on a multi-nas basis, as I have had both two NASes getting IPs assigned to users from a single shared pool, and also one-pool-per-NAS. Both work fine. It's your choice really - you can always just use one-pool-per-NAS and manually assign each NAS to a RADIUS server responsible for maintaining the pool, while you're getting sqlippool up to production standards. Hope this helps, Jan On 07/12/06, Paul Khavkine <paul.khavkine@distributel.ca> wrote: > > > > > Hi folks. > > > I'm looking into ways to implement a "global address pool" for multiple > NASes and multiple RADIUS servers. > > I see that there's 2 possible ways of doing it with FreeRADIUS. > > 1) use rlm_ippool > 2) use rlm_sqlippool > > I'm leaning towards rlm_sqlippool since it can be used to "lease" an > address to a subscriber for a period of time > so they get same ip address for the duration of the "lease". > > Is there any other ways to implement NAS independent address pool and be > able to "lease" same address to a subscriber ? > > Is anyone using sqlippool in production ? > > Thanx > Paul > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > ------=_Part_61922_7824572.1165533998049 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline from what I've seen on the lists, sqlippool is full of bugs and holes. If you're planning to put it into a production environment, I'd strongly suggest booking a coder for a couple of days :-) Such is the nature of open-source I guess. <br><br>There is no other truly feasable way of leasing IPs over multiple servers, other than Rsync'ing the pool files, or manually assigning different RADIUS servers for different pools - the second means that you are basically splitting your system into multiple independent groups - several NASes to one RADIUS server. However, both of these are hacks. <br><br>I'm using rlm_ippool at the moment on a multi-nas basis, as I have had both two NASes getting IPs assigned to users from a single shared pool, and also one-pool-per-NAS. Both work fine.<br><br>It's your choice really - you can always just use one-pool-per-NAS and manually assign each NAS to a RADIUS server responsible for maintaining the pool, while you're getting sqlippool up to production standards. <br><br>Hope this helps,<br><br>Jan<br><br><div><span class="gmail_quote">On 07/12/06, <b class="gmail_sendername">Paul Khavkine</b> <<a href="mailto:paul.khavkine@distributel.ca">paul.kh avkine@distributel.ca</a>> wrote: </span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div> <br> <br> <br> <p><font size="2">Hi folks.<br> <br> <br> I'm looking into ways to implement a "global address pool" for multiple NASes and multiple RADIUS servers.<br> <br> I see that there's 2 possible ways of doing it with FreeRADIUS.<br> <br> 1) use rlm_ippool<br> 2) use rlm_sqlippool<br> <br> I'm leaning towards rlm_sqlippool since it can be used to "lease" an address to a subscriber for a period of time<br> so they get same ip address for the duration of the "lease".<br> <br> Is there any other ways to implement NAS independent address pool and be able to "lease" same address to a subscriber ?<br> <br> Is anyone using sqlippool in production ?<br> <br> Thanx<br> Paul<br> </font> </p> </div> <br>-<br>List info/subscribe/unsubscribe? See <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.freeradius.org/list/users.html" target="_blank">http://www.freeradius.org/list/users.html</a><br><br> </blockquote></div><br> ------=_Part_61922_7824572.1165533998049-- --===============0282885323== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html --===============0282885323==-- |