On Sat, 21 Sep 2002, [iso-8859-1] ho k wrote: > Hi > > Can you explain why it can work for NT RAS with using > db file? > > Debug for NT RAS: > rad_recv: Access-Request packet from host > 192.168.59.244:1068, id=26, length=92 > User-Name = "kkho" > CHAP-Challenge = > "\275\376V\366;43\354\360P;\276&a\302\001" > CHAP-Password = > 0x08091bdcb6d497ec98ea941725a9adcc12 > NAS-Port = 0 > Framed-Protocol = PPP > NAS-Identifier = "AUD_AGENT" > NAS-Port-Type = Async > rlm_ippool: Searching for an entry for nas/port: /0
So your nas is sending nas-identifier and a port of 0. First of all support for NAS-Identifier was added in May so you are running quite an old version. In any case I pressume that this nas will always send port 0. rlm_ippool relies on the nas/port information in accounting and authentication packets to find stale entries and delete them. Obviously if it always sees the same nas/port it will deallocate the corresponding entry in the database and give it out. If the same nas/port combination does not show up in an Acounting/Access Rquest it cannot deallocate the corresponding entry from the ip pool. Which is probably the case with your other nas. > rlm_ippool: Found a stale entry for ip/port: > 192.168.59.194/0 > rlm_ippool: num: 0 > rlm_ippool: num: 1 > rlm_ippool: Allocated ip 192.168.59.194 to client on > nas ,port 0 -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 10 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
