Hi, The main_pool line in the accounting section of the radiusd.conf file was commented ... Maybe that was my mistake. Ok for the rlm_ippool_tool I'm gonna use it to see if my modification of radiusd.conf is working or not. I was not using accounting at all so I forgot about it but it seems that I will have to configure it well to get the ip_pool working. Thank for answering.
Best regards, -- Sebastien Cantos <[EMAIL PROTECTED]> Network / System Manager Neopost DIVA > -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] De la > part de Kostas Kalevras > Envoyà : jeudi 31 mars 2005 13:47 > à : freeradius-users@lists.freeradius.org > Objet : Re: Problem with ip pools > > On Thu, 31 Mar 2005, SÎbastien Cantos wrote: > > > Hi, > > > > I'm using ip pools to manage my client ips from the radius side. > > Here's my conf: > > * users file : > > DEFAULT Service-Type == Framed-User, Pool-Name := "main_pool" > > Framed-Protocol = PPP, > > Framed-MTU = 576 > > > > * radiusd.conf file: > > ippool main_pool { > > range-start = 192.168.52.2 > > range-stop = 192.168.52.254 > > netmask = 255.255.255.0 > > cache-size = 800 > > session-db = ${raddbdir}/db.ippool > > ip-index = ${raddbdir}/db.ipindex > > } > > > > Everything is working well for some days then my clients > could not get > > anymore ips from the radius. I've found a way to correct > this by deletinf > > the db.ip* files and restarting the radius but this is not *clean*. > > Is there a way to dump the content of the ippool database ? > > I want to understand how ips are freed from the pool > because I think that > > there's a problem when a client disconnects. It seems that > ips stay in the > > pool as used even if the client has disconnected. > > Thanks in advance for your help. > > There's rlm_ippool_tool which might help you in > src/modules/rlm_ippool. > rlm_ippool depends on accounting working ok. If it is not > working then you might > get into problems. The module *does* have a few more methods > of finding out > stale records and deleting them: > 1. maximum-timeout directive. You can set that to the maximum > session time > expected in your network (if that can be calculated) in order > to make sure no ip > remains active for more time than maximum-timeout. > 2. Each time an authentication request is performed from a > nas ip/port pair > which has already an ip allocated that ip is cleaned up. That > means that as long > as your ip pool is as large as your nas ports number it will > be difficult to run > out of available ip's. > > My suggestion is to make sure you don't run an old version of > the module (older > version did have problems) and to take a closer look at how > well your accounting > works. > > > > > Regargs, > > -- > > Sebastien Cantos <[EMAIL PROTECTED]> > > Network / System Manager > > Neopost DIVA > > > > > > - > > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > > > > -- > Kostas Kalevras Network Operations Center > [EMAIL PROTECTED] National Technical University of Athens, Greece > Work Phone: +30 210 7721861 > 'Go back to the shadow' Gandalf > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
