Hello Martin -
On Fri, 11 Aug 2000, Martin Cernicka wrote:
> Hello.
>
> >From: Hugh Irvine <[EMAIL PROTECTED]>
> >This sounds like a NAS problem, as Radiator uses the accounting stop to
> >de-allocate the address. If Radiator does not see a stop, then the address will
> >remain allocated until the lease expires.
>
> Exactly.
>
> > I see you have set the
> >DefaultLeasePeriod to one hour and the LeaseReclaimInterval to 10 minutes - do
> >these settings work correctly to return the addresses to the free state?
>
> Yes, these settings are working and when we become a Stop, it works as well. So
> in fact, we are getting the IP adresses back after some finite time. But - when
> somebody is using some IP adress for more than the DefaultLeasePeriod, it will
> be reassigned regardless of that, right? So I cannot simply lower this period
> even when our IP pool is empty after 30 minutes in peak times.
>
> But I have an idea. The Tigris servers are configured so that they send an
> "Acct-Status-Type = Alive" every 10 minutes. Would it be possible to configure
> Radiator so that it will treat the connection as dead if there are no Alives
> within 11 minutes? As a short-time solution it would by good enough.
>
You could possibly do something like this:
Using Handlers, create a special Handler just for "Acct-Status-Type = Alive",
and inside it create a special AuthBy SQL clause that will maintain a new,
seperate ALIVE table.
Then, create a little cron job to go through the ALIVE table and the
ADDRESSPOOL table and return the IP addresses from "dead" sessions to the
available state.
Of course, this assumes that your NAS(s) will actually send the Alive packets,
which may be wishful thinking if it doesn't send Stop packets already.
> >If you are not getting accounting stops, how are you doing your accounting and
> >billing? I think I would check with the NAS vendor to see if there is a fix for
> >the problem.
>
> We are not doing the accounting from Radius, but the logs would be handy. The
> problem is in IP address allocation. We contacted the vendor already, but it
> seems it will take some days.
>
> >I will need to see a trace 4 debug if there are still problems.
>
> I am not sure, which part you are interested in - if the Stop won't come, there
> is nothing to look at. Anyway, I am sure it is not a problem of Radiator - a
> quick search through the old logs showed that this is an old problem.
>
Understood. Let me know if there is anything else I can do.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
