Home > radius error > radius error dropping conflicting packet from client

Radius Error Dropping Conflicting Packet From Client

| Report Content as Inappropriate ♦ ♦ Error: Received conflicting packet Hi, all, Sometimes when there are too many requests from a NAS, like right after rebooting it and thus breaking current sessions, etc., freeradius 2.1.3 under FreeBSD begins loggin many many lines like this after the NAS re-sends unanswered packets: Error: Received conflicting packet from client 10.10.70.94 port 1646 - ID: 220 due to unfinished request 511166. Giving up on old request. I looked in src/main/event.c and found this code: default: gettimeofday(&when, NULL); when.tv_sec -= 1; /* * If the cached request was received * within the last second, then we * discard the NEW request instead of the * old one. This will happen ONLY when * the client is severely broken, and is * sending conflicting packets very * quickly. */ if (timercmp(&when, &request->received, <)) { radlog(L_ERR, "Discarding conflicting packet from " "client %s port %d - ID: %d due to recent request %d.", client->shortname, packet->src_port, packet->id, request->number); return 0; } received_conflicting_request(request, client); ^^^ request = NULL; break; Our authorization/accounting happens through rlm_perl and is written in Perl. Perhaps it's not fast enough to process many many requests in under 1 second (when.tv_sec), but aborting the current packet instead of the new duplicate one can hardly be justified. Please look at the line marked with ^^^ - it's where the error is logged and the current request is aborted, unless it was caught earlier by "Discarding conflicting packet", in which case the _new_ duplicate request is aborted, which is more correct. I propose that when.tv_sec be configurable in radiusd.conf, and not hardcoded like that. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Alan DeKok-2 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: Error: Received conflicting packet rihad wrote: > Sometimes when there are too many requests from a NAS, like right after > rebooting it and thus breaking current sessions, etc., freeradius 2.1.3 > under FreeBSD begins loggin many many lines like this after the NAS > re-sends unanswered packets: > > Error: Received conflicting packet

receives about 5 or 6 new calls per minute using a simple authentiaction method, using MySQL as backend for registering the calls. Every day I'm seeing this error logs on my radius.log file: Mon Apr 4 12:15:58 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 30 Mon Apr 4 12:16:03 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 30 Mon Apr 4 12:16:08 2005 : Error: Dropping conflicting packet from client http://freeradius.1045715.n5.nabble.com/Error-Received-conflicting-packet-td2787416.html XXX:1645 - ID: 103 due to unfinished request 221 30 Mon Apr 4 12:16:14 2005 : Error: Dropping conflicting packet from client XXX:1645 - ID: 103 due to unfinished request 221 30 They are not many, but about 3 series like these appear every day. I couldn't find many info on this error on the net... I've seen a couple of threads https://www.mail-archive.com/freeradius-users@lists.freeradius.org/msg15674.html that mention it can be due to the radius taking too much time to authenticate while using scripts, but I'm not using any script, just simple authentication accepting everything... I got this on /etc/raddb/users: DEFAULT Auth-Type := Accept Service-Type = Framed-User, Framed-Protocol = PPP, Fall-Through = 0 I tried increasing max_request_time to 60 (it was on 30) and max_requests to 6400 (I've got 25 clients) on radiusd.conf, but that didn't solve it... What factors can be causing this error?? Thanks in advance, Juan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Previous message View by thread View by date Next message Re: Error: Dropping conflicting packet due to unfinished requ... Juan Nin Re: Error: Dropping conflicting packet due to unfinished... Alan DeKok Re: Error: Dropping conflicting packet due to unfini... Juan Nin Re: Error: Dropping conflicting packet due to un... Dustin Doris Re: Error: Dropping conflicting packet due t... Juan Nin Re: Error: Dropping conflicting packet due to un... Alan DeKok Re: Error: Dropping conflicting packet due t... Juan Nin Re: Error: Dropping conflicting packet ... Alan DeKok Re: Error: Dropping conflicting pac... Juan Nin Re: Error: Dropping conflicting.

10 10:17:30 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 71 due to unfinished request 48567Thu Mar 10 12:52:57 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: http://mailing.unix.freeradius-users.narkive.com/PCtEkS9o/can-somebody-explain-the-errors 89 due to unfinished request 81227Thu Mar 10 14:12:03 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 128 due to unfinished request 101178Thu Mar 10 17:17:30 2005 : Error: Discarding duplicate request from clientapk1:1813 - ID: 253 due to unfinished request 152382Thu Mar 10 20:08:03 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 92 due to unfinished request 209934Can radius error somebody explain the errors I've got. What should I change inradiusd.conf to elliminate these errors?About duplicate request I know. I've got to change: cleanup_delay++ andmax_requests--;What about the "conflicting packet"? What does it mean?Best regards,Serg-List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Alan DeKok 2005-03-11 01:07:25 UTC PermalinkRaw Message Post by Serg ShipaevThu Mar 10 20:08:03 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 92 due to radius error dropping unfinished request 209934Can somebody explain the errors I've got. What should I change inradiusd.conf to elliminate these errors?You don't. You find out why your RADIUS server is taking forever torespond, and fix the problem.Post by Serg ShipaevAbout duplicate request I know. I've got to change: cleanup_delay++ andmax_requests--;I don't see why.Post by Serg ShipaevWhat about the "conflicting packet"? What does it mean?It means that the RADIUS server is taking so long to respond thatthe NAS has given up, and sent another RADIUS packet.Alan DeKok.-List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html Radius 2005-03-11 01:15:37 UTC PermalinkRaw Message I see the same thing with trying to set up realms, but haven't receivedany response to my question.Are you running realms setup?BobPost by Serg ShipaevSirs,Wed Mar 9 22:47:34 2005 : Info: Ready to process requests.Thu Mar 10 10:17:30 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 71 due to unfinished request 48567Thu Mar 10 12:52:57 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 89 due to unfinished request 81227Thu Mar 10 14:12:03 2005 : Error: Dropping conflicting packet from clientapk1:1813 - ID: 128 due to unfinished request 101178Thu Mar 10 17:17:30 200

 

Related content

radius error warning unresponsive child

Radius Error Warning Unresponsive Child p for request in module sqlcomponent accounting Messages sorted by date thread subject author relatedl Hello all I facing this problem with my Freeradius and I don't know how to solve it My NAS is sending only accounting registers to my freeradius server My freeradius server is configured to store these registers into a MySQL server I have configured max request time in the case of MySQL slow performance but the problem perssits My questions are - how can I solve this issue - When a child is unresponsive the register is lost or another

radius error received conflicting packet from client

Radius Error Received Conflicting Packet From Client p author Ivan Kalik wrote Our radius-server timeout is high enough minutes Once again I relatedl suppose that what freeradius thinks of as Received conflicting packet are rather a bit delayed packets normally treated as Discarding conflicting packet i e they arrive at freeradius in maybe second after the first request but freeradius drops the current request instead of the new one Soon I'm gonna rebuild freeradius with changed tv sec and check that huh do you not understand the basic context of this issue if the NAS has sent a repeat RADIUS

radius error messages

Radius Error Messages table id toc tbody tr td div id toctitle Contents div ul li a href Nps Event Viewer a li li a href Nps Log Viewer a li li a href Message Authenticator Attribute That Is Not Valid a li ul td tr tbody table p August RADIUS Error Messages draft-zorn-radius-err-msg- txt Status of this Memo By submitting this Internet-Draft each author represents that any applicable patent or other IPR relatedl claims of which he or she is aware have been or a radius message was received from the invalid radius client ip address will be disclosed

radius error discarding duplicate request from client

Radius Error Discarding Duplicate Request From Client p diams diams Report Content as Inappropriate diams diams Error Discarding duplicate request from client What relatedl does this mean Error Discarding duplicate request from client I get this every time a session expires Session-Timeout every -hours For every new login I get two messages in the log file one successful login and the error see log here Sun Feb Auth Login OK user du from client highstreet port cli F C Sun Feb Error Discarding duplicate request from client highstreet - ID due to unfinished request Sun Feb Auth Login OK linx