On Thu, 2002-03-07 at 16:01, Alan DeKok wrote: > Eduardo Roldan <[EMAIL PROTECTED]> wrote: > > I dowloaded the CVS snapshot freeradius-snapshot-20020307.tar.gz > > radzap has changed from the 0.4 version, correct? > > Slightly. > > > And the new version request a radius server.. I don't understand. Why an > > app to clean the utmp request a radius server? > > It now does more than that. Multiple databases may have utmp-style > data. The only way to update ALL of them is to send a packet to the > server.
mmmm. Now I understand. > > > radzap: zapping termserver 200.40.77.19, port 117440712, user > > [EMAIL PROTECTED] > > radzap: no response from server > > You should be able to use "server:port" to send the packet to the > port that the server is listening on. Ok, the sintax server:port doesn't work for me, but I use -p PORT, it's the same. But, something strange happens to me. Start the server with -X parameter. OK, for me the latest 2 lines says: Listening on IP address *, ports 1812/udp and 1813/udp. Ready to process requests. Ok, now zap that bad user! radzap -r data -p 1812 rac 117440712 [EMAIL PROTECTED] Ooops, the log says: rad_recv: Accounting-Request packet from host 127.0.0.1:32850, id=97, length=127 Accounting-Request packet sent to a non-accounting port from client localhost:32850 - ID 97 : IGNORED --- Walking the entire request list --- Nothing to do. Sleeping until we see a request. Hehe, 1812 isn't the accounting port, it's 1813. Ok , this will work now: [root@data sbin]# radzap -r data -p 1813 rac 117440712 [EMAIL PROTECTED] radzap: zapping termserver 200.40.77.19, port 117440712, user [EMAIL PROTECTED] radzap: no response from server Arrgggg!!!, now nothing new in the logs, nothing. What happens now? This is driving me mad. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
