Hi Skeeve, Maybe it would be a good idea to give Session-Timeout also and set it to 24 hours. So if even the user is online and useing the address for longer than 23:59 then it will be disconnected and ip address we bee released. Of cource then you have to make official policy out of it that you don't allow longer than 24 hour sessions (what is not a bad thing and I hope that I would have done it when my network was starting - release unused resources).
Rgds Toomas ----- Original Message ----- From: "Skeeve Stevens" <[EMAIL PROTECTED]> To: "Hugh Irvine" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 25, 2002 11:55 PM Subject: Re: (RADIATOR) IP Lease problem > > If there is a problem with stop records, and people are staying on for 1 or 2 days... then there is quite possibly a chance for problems. > > Using static IP for a large number of customer without good reason could cause us to bleed higher usage on Address Space which APNIC would also not be responsive to.... so I am trying to be conservative. > > Is there no solution? or is it just complicated. > > ...Skeeve > > > On Thu, Sep 26, 2002 at 07:38:33AM +1000, Hugh Irvine wrote into the ether: > > > > Hello Skeeve - > > > > The short answer is to use static addresses for long-held connections. > > > > By definition, dynamic addresses are designed for frequent re-use. > > > > regards > > > > Hugh > > > > > > On Wednesday, September 25, 2002, at 11:50 PM, Skeeve Stevens wrote: > > > > > > > > > > > Question > > > > > > We currently have a pool of 64 IP's stored in a database, and when a > > > user connects AND they don't have a static IP they get assigned one > > > from > > > the database of dynamic IP's... > > > > > > The problem I have is that the pool has the Lease Period set to 24 > > > hours > > > after 24 hours the dynamic IP is reclaimed... which is all good.. > > > > > > But what if the user was dedicated and did not disconnect after 24 > > > hours. > > > The IP still gets reclaimed.. and can be assigned by the database to a > > > new connection even though the user is still using it.. > > > > > > If I set it to have no Lease or a Lease longer than, lets say a week > > > and > > > the user has no stop record, then I risk not getting the IP back for a > > > while if not at all... and the pool can fill. > > > > > > Any Thoughts.... > > > > > > > > > _______________________________________________________ > > > Skeeve Stevens, RHCE Email: [EMAIL PROTECTED] > > > Website: www.skeeve.org - Telephone: (0414) 753 383 > > > Address: P.O Box 1035, Epping, NSW, 1710, Australia > > > > > > eIntellego - [EMAIL PROTECTED] - www.eintellego.net > > > _______________________________________________________ > > > Si vis pacem, para bellum > > > > > > > > > === > > > Archive at http://www.open.com.au/archives/radiator/ > > > Announcements on [EMAIL PROTECTED] > > > To unsubscribe, email '[EMAIL PROTECTED]' with > > > 'unsubscribe radiator' in the body of the message. > > > > > > > > > > -- > > Radiator: the most portable, flexible and configurable RADIUS server > > anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. > > - > > Nets: internetwork inventory and management - graphical, extensible, > > flexible with hardware, software, platform and database independence. > > -- > --------------------------------------------------------------------- > | Skeeve Stevens url: http://www.skeeve.org/ | > | email:[EMAIL PROTECTED]/ url: http://www.eIntellego.org/ | > --------------------------------------------------------------------- > === > Archive at http://www.open.com.au/archives/radiator/ > Announcements on [EMAIL PROTECTED] > To unsubscribe, email '[EMAIL PROTECTED]' with > 'unsubscribe radiator' in the body of the message. > === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
