(RADIATOR) IPs allocated forever
Jon Omagojeaskoa
omago at sarenet.es
Wed Jul 4 10:09:36 CDT 2001
Hello,
We use <Authby DYNADDRES> with <AddressAllocator SQL> and we've seen that
IPs are allocated (AllocateQuery) as soon as Authentication packets arrive.
Wed Jul 4 16:00:11 2001: DEBUG: Packet dump:
*** Received from 212.81.251.101 port 1645 ....
Code: Access-Request
Identifier: 35
Authentic: XXX
Attributes:
(...)
Wed Jul 4 16:00:11 2001: DEBUG: Handling with Radius::AuthDYNADDRESS
Wed Jul 4 16:00:11 2001: DEBUG: Query is: select TIME_STAMP,
YIADDR from RADPOOL where POOL='pool_profesional'
and STATE=0 order by TIME_STAMP LIMIT 1
Wed Jul 4 16:00:11 2001: DEBUG: do query is: update RADPOOL set
STATE=1,TIME_STAMP=994255211, EXPIRY=994341611, USERNAME='xxxxx' where
YIADDR='212.81.164.10' and TIME_STAMP =994251930
(...)
What happends when 2 Access-Request (duplicated) are received for the same
user conection ?
2 IPs are allocated and only the second one (the one followed by Accounting
packets) is deallocated (when Accounting-STOP arrives).
Is there any way to solve this ? We can't use "DefaultLeasePeriod",
"LeaseReclaimInterval" ... directives because we've users connected for
very long time periods (10-12 days!).
Thanks in advance.
-------------------------------------------------------------------
Jon Mikel Omagojeaskoa Insunza
SARENET
<omago at sarenet.es>
+34 94 4209470
-------------------------------------------------------------------
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
More information about the radiator
mailing list