Re: R: Re: R: Re: R: rlm_ippool: No available ip addresses in pool
Tabacchiera Stefano wrote:
Alan, here's the content of gdbm db:
Ah... it's the DBM pools. I already stated that in the subject of my mail (did you notice the module name?).
Well.. use "rlm_ippool_tool" to manage the pool.
Great idea! Too bad that tool allow only to cleal *all* the entries in the DBM pool. Or am I just missing something?
Or, get your NAS to send accounting stop packets. It's *supposed* to send stop packets when a user session is cleared.
As I already said, I know the NAS sometimes doesn't send acct-stop pkts, but it's out of my control. My questions (still unanswered, let me say) are: 1) is maximum_timeout useless? 2) Is there a way to keep my dbm pool safe and updated (I mean no expired addresses), even in the case some acct-stop pkt are loss? 3) Should I switch to sql pool, 'cause dbm it's actually unreliable? Thanks again. ST ______________________________________________________________________________________ La presente comunicazione ed i suoi allegati e' destinata esclusivamente ai destinatari. Qualsiasi suo utilizzo, comunicazione o diffusione non autorizzata e' proibita. Se ha ricevuto questa comunicazione per errore, la preghiamo di darne immediata comunicazione al mittente e di cancellare tutte le informazioni erroneamente acquisite. (Rif. D.Lgs. 196/2003). Grazie This message and its attachments are intended only for use by the addressees. Any use, re-transmission or dissemination not authorized of it is prohibited. If you received this e-mail in error, please inform the sender immediately and delete all the material. (Rif. D.Lgs. 196/2003). Thank you.
How is FreeRADIUS supposed to know when a user disconnects and frees up the IP address from the pool if the NAS doesn't tell it? Anything else is not exactly reliable. If you have a user with a long duration session that lasts longer than your timeout the IP could be put back into the pool when it is still in use. The best solution would be to fix the NAS to send the packets or fix the network to make sure they get delivered. Michael ---------------------------------------------------------------------- Michael J. Hartwick, VE3SLQ hartwick@hartwick.com Hartwick Communications Consulting (519) 396-7719 Kincardine, ON, CA http://www.hartwick.com ---------------------------------------------------------------------- From: freeradius-users-bounces+hartwick=hartwick.com@lists.freeradius.org [mailto:freeradius-users-bounces+hartwick=hartwick.com@lists.freeradius.org] On Behalf Of Tabacchiera Stefano Sent: Tuesday, May 04, 2010 15:39 To: freeradius-users@lists.freeradius.org Subject: Re: R: Re: R: Re: R: rlm_ippool: No available ip addresses in pool
Tabacchiera Stefano wrote:
Alan, here's the content of gdbm db:
Ah... it's the DBM pools.
I already stated that in the subject of my mail (did you notice the module name?).
Well.. use "rlm_ippool_tool" to manage the pool.
Great idea! Too bad that tool allow only to cleal *all* the entries in the DBM pool. Or am I just missing something?
Or, get your NAS to send accounting stop packets. It's *supposed* to send stop packets when a user session is cleared.
As I already said, I know the NAS sometimes doesn't send acct-stop pkts, but it's out of my control. My questions (still unanswered, let me say) are: 1) is maximum_timeout useless? 2) Is there a way to keep my dbm pool safe and updated (I mean no expired addresses), even in the case some acct-stop pkt are loss? 3) Should I switch to sql pool, 'cause dbm it's actually unreliable?
Tabacchiera Stefano wrote:
Great idea! Too bad that tool allow only to cleal *all* the entries in the DBM pool.
Or am I just missing something?
<shrug> Then write a Perl script to manage the pool. It's just a DBM file.
Or, get your NAS to send accounting stop packets. It's *supposed* to send stop packets when a user session is cleared.
As I already said, I know the NAS sometimes doesn't send acct-stop pkts, but it's out of my control.
Well... your NAS is broken. There's little we can do to fix that.
My questions (still unanswered, let me say) are:
1) is maximum_timeout useless?
No idea. I don't use that module.
2) Is there a way to keep my dbm pool safe and updated (I mean no expired addresses), even in the case some acct-stop pkt are loss?
No.
3) Should I switch to sql pool, 'cause dbm it's actually unreliable?
You should switch to the sqlippool module. It uses SQL features to automatically clear old entries, even if the NAS is broken. This isn't about an "unreliable" DBM file. The DBM file is reliable. It's your *NAS* that is broken. The additional features of SQL (which are missing in DBM) makes it easier for FreeRADIUS to work around a broken NAS. Alan DeKok.
participants (3)
-
Alan DeKok -
Michael J. Hartwick -
Tabacchiera Stefano