Hi Kostas
I have had the detail file enable from day one :) do not trust databases for long term data.
The port is different but there is a stop record in the rad detail file.
One comment is that if I run "freeradius -xx" and then send a stop record for an active IP but use a different NAS port the resulting debug message indicate that there is no IP to release.
I really can not see how it could a something wrong in the configuration because it works most of the time.
I suppose I could be mis-reading the rlm-ippool_tool results, but I know that I'm running out of IP address because the radreply does not have the framed-ip-address in it when to many address are active.
The version of freeradius is 1.0.1 which was packaged using the Debian freeradius package as a basis.
Cheers Mike
rlm_ippool will free an ip address either on an accounting-stop or if a new authentication request comes on an allocated nas-ip/port. Either you 've hit a bug or something is wrong in your installation. Try enbaling authentication and accounting detail files and watch a bit the nas-ip/nas-port combinations for anything strange. Especially the ones that don't get deallocated. Report back anything you find, cause i would be really interested to know what's the problem in your case.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
