Hello Rodolfo -
Missing stop packets are always a problem when trying to enforce restrictions on simultaneous use.
The first thing to do is establish why the stop packets are missing, and the usual reasons for this are saturated communications links (dropped packets), incorrect configuration files, or incorrect NAS configuration and/or bugs.
You will need to use a network packet dump utility (like tcpdump, snoop, ethereal, ...) to find out exactly what is happening. The only "foolproof" method of avoiding problems is to use a session database and interogate the NAS.
This topic has been discussed many times on the mailing list:
www.open.com.au/archives/radiator
regards
Hugh
On 30/10/2003, at 7:00 AM, Rodolfo Torrado L�pez wrote:
Hi everybody.
�
I have Radiator 3.6 over Windows 2K Server.
�
I am experimenting problems with stop packets (I have�not implemented , yet, Interrogating to NAS or SessionDatabase): some of them are not processed, and the user stay, incorrectly, on line, and they can not log on (I use Simultaneous use = 1)
�
What can�I do in order to fix this problem? (for instance enlarge the buffer size)
�
Thanks
�
Rodolfo
NB: have you included a copy of your configuration file (no secrets), together with a trace 4 debug showing what is happening?
-- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. - CATool: Private Certificate Authority for Unix and Unix-like systems.
=== Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
