>> I do know, that of the 900 or so IP's marked as active in my IPPool, >> only 600+ are actually IN USE. This disturbs me. >> I have upgraded to version 1.0.1, but the behaviour is the same. >> It seems like the IP's are still not "freed" after a client disconnects.
> The IP's can only be free'd if the NAS tells the server that the >user has disconnected. If the NAS fails to do this, then FreeRADIUS >won't de-allocate the IP. >> I have tried to radzap both a NAS, and a NAS+PORT, but the IP is not >> marked as non-active in the IP-pool. > Use the IP in the pool for radzap, not the IP of the NAS. > Alan DeKok. If I run "radzap <stale-IP-from-pool>" the line returned is Tue Dec 28 20:19:53 2004 : Info: Starting - reading configuration files ... and then the program ends. In the radius.log-file, I find an entry "Tue Dec 28 20:19:53 2004 : Error: There appears to be another RADIUS server running on the authentication port 1812" What do I do wrong? -- Med vennlig hilsen/Sincerely Alfred H. Dahl Hostmaster �lla Kommunikasjon - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
