Deduplication of accounting requests
From RFC: "The RADIUS server can detect a duplicate request if it has the same client source IP address and source UDP port and Identifier within a short span of time."
Does it mean, if my application send accounting requests from one port, I can send only 256 request in short span of time, next request will be handled as duplicate regardless of attributes in it? How freeradius detect that package is duplicated? What fields used for this purposes ? Where and how it configured? Thanks, --Artem
On Feb 12, 2016, at 9:25 AM, apopov@cybervisiontech.com wrote:
From RFC: "The RADIUS server can detect a duplicate request if it has the same client source IP address and source UDP port and Identifier within a short span of time."
Does it mean, if my application send accounting requests from one port, I can send only 256 request in short span of time, next request will be handled as duplicate regardless of attributes in it?
No.
How freeradius detect that package is duplicated? What fields used for this purposes ? Where and how it configured?
It detects duplicates using (among other things) the request authenticator. To be clear, if you're not implementing a RADIUS client or a RADIUS server, you have no reason to worry about this kind of detail. Just trust that the RADIUS client and server do the right thing. If you are implementing a RADIUS client or a RADIUS server, go read the RFCs, and the FreeRADIUS source code. This list is for FreeRADIUS questions. We're not in the business of helping people write competing software. Alan DeKok.
This list is for FreeRADIUS questions. We are trying to integrate our system with FreeRadius Server and we want to be sure that FreeRadius will handle our requests as we expect.So, it is FreeRADIUS question. We must be sure that FreeRadius server will never drop packages which it should do not drop and all our data will be delivered. If you have no time to explain all details, just help we to find file where this logic implemented.
----- Original Message ----- From: "Alan DeKok" <aland@deployingradius.com> To: "freeradius-users" <freeradius-users@lists.freeradius.org> Sent: Friday, February 12, 2016 4:28:18 PM Subject: Re: Deduplication of accounting requests On Feb 12, 2016, at 9:25 AM, apopov@cybervisiontech.com wrote:
From RFC: "The RADIUS server can detect a duplicate request if it has the same client source IP address and source UDP port and Identifier within a short span of time."
Does it mean, if my application send accounting requests from one port, I can send only 256 request in short span of time, next request will be handled as duplicate regardless of attributes in it?
No.
How freeradius detect that package is duplicated? What fields used for this purposes ? Where and how it configured?
It detects duplicates using (among other things) the request authenticator. To be clear, if you're not implementing a RADIUS client or a RADIUS server, you have no reason to worry about this kind of detail. Just trust that the RADIUS client and server do the right thing. If you are implementing a RADIUS client or a RADIUS server, go read the RFCs, and the FreeRADIUS source code. This list is for FreeRADIUS questions. We're not in the business of helping people write competing software. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Feb 12, 2016, at 10:43 AM, apopov@cybervisiontech.com wrote:
This list is for FreeRADIUS questions. We are trying to integrate our system with FreeRadius Server and we want to be sure that FreeRadius will handle our requests as we expect.So, it is FreeRADIUS question.
As I already explained, no. If you wrote your own RADIUS client, it is *your* responsibility to read the RFCs. We have a BSD licensed RADIUS client which is publicly available. It works. Questions about the RADIUS protocol are *not* FreeRADIUS questions. They are questions that are already answered by the RADIUS specifications.
We must be sure that FreeRadius server will never drop packages which it should do not drop and all our data will be delivered.
Think about it. FreeRADIUS is the most widely used RADIUS server. Is it: a) broken and not working or b) working correctly?
If you have no time to explain all details, just help we to find file where this logic implemented.
Don't make rude statements. If you continue, you will be unsubscribed from the list, and permanently banned. It is *your* responsibility to read the RFCs. It is not *my* responsibility to explain them to you. By the same token, if you're too lazy to read the RFCs, I'm too lazy to explain them to you. Go read the RFCS. If you continue to argue, you will be banned. This is your only warning. Alan DeKok.
participants (2)
-
Alan DeKok -
apopov＠cybervisiontech.com