Maybe you are correct. But when we use radwho -r, we can use the port number we see. I copied the radutmp file to a linux/freeradius test server, and i can zap the user.
The problem is in the real server, the server that runs FreeBSD. It seems that radzap does not find the radiusd server, but they are on the same machine. It is not that problem of "port already in use", the release i am using is 0.9.1. thanks, Luiz Gustavo > I don't know if this has anything to do with it but the UTMP > on FreeBSD is slightly different than many other platforms. I > came across these differences a number of years ago, when I was > having problems. The main consequence I came across was that > FreeBSD truncates the nas/port information. > > If radutmp on FreeBSD is using a standard structure on all > platforms rather than the platform standard, this may be a > mute point. > > On Tue, 2005-11-01 at 13:53 +0100, [EMAIL PROTECTED] wrote: >> Luiz Gustavo Anflor Pereira schrieb: >> >> > There is some problem about radzap 0.9.1 in a FreeBSD >> > system? >> > Why it does not zap the users from radutmp? >> >> Because there's a bug in the source code which prevents >> it from working when you're trying to run it on the same server >> on which the server is running - no matter what OS that >> box is using? >> Didn't we have some detailled description of the problem in >> the past weeks? >> >> Regards, >> Stefan >> >> - >> List info/subscribe/unsubscribe? See >> http://www.freeradius.org/list/users.html >> > -- > Guy Fraser > Network Administrator > The Internet Centre > 1-888-450-6787 > (780)450-6787 > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
