"Anteva Support" <[EMAIL PROTECTED]> wrote: > The fact is that radzap won't do jack unless it can talk to the termserver > from whence the connection was made.
No, the error messages are confusing you. > > > radzap: zapping termserver ip.addr.of.termserver, port 14, user > user@realm > > > radzap: no response from server This message does NOT mean that it's trying to contact the terminal server, it means that radzap is trying to contact the RADIUS server. > 1: The termserver parameter is required. Yes... you have to say which NAS the user was logged in on. > 2: It has been my experience that it doesn't matter what the value is, it > still won't work > 3: I've tried the following and always get either 'no entry found' or 'no > response from server': OK... the 'entry not found' means that it's looking up an entry in the 'radutmp' file, and not finding it. 'strace radzap ...' will show you what's happening. The problem is really that 'radzap' is old, and meant to work only with the 'radutmp' file. That's wrong, and should be fixed. Instead, it should send a fake accounting packet to the server, and never look at the radutmp file. That will require source code patches. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
