I know this thread has appeared in the group a few times in the past, but I believe I have a new occurrence which is related to a memory issue. The infamous line: datestamp : Error: Dropping conflicting authentication packet from client clientname.realm.net:1645 - ID: xxx I am currently running the snapshot dated 08/14/01, and this issue seemed to crop up recently after perhaps this snapshot, or could have even been beta 2. The issue only seems to start up after the radius server has been running a couple hours and processed a few thousand requests. Then these conflicting lines begin showing up in the logs, usually 2-6 per unique login. The logins still seem to be making it through; however, these lines persist. I have checked TS settings, and tried multiple TSs to ensure it is not a TS error. But in most instances the TS is set to re-send packet 10 seconds after IF it has not received a reply. These conflicting packet lines seem to appear mere seconds, after the request, and well before the TS sends a 2nd request. A restart of the radius process clears these errors immediately, until about 2 hours later where they start up again. I am assuming a memory issue is perhaps causing this phenomenon. Ideas? ---------------------------------- Nathan Miller Visp Systems Administration Voice: 541-476-5352 ext. 4 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
