Hello Team, We have the setup to update the postgreSQL database for START and STOP accounting request and its working fine. I would like to have an option to make freeRADIUS not to send reply for any accounting messages but accounting request should get logged in Database. Will it be possible on freeRADIUS 3.0.13? Regards, Raghu
On Fri, 2019-03-08 at 19:58 +0530, Raghu nathan wrote:
We have the setup to update the postgreSQL database for START and STOP accounting request and its working fine.
I would like to have an option to make freeRADIUS not to send reply for any accounting messages but accounting request should get logged in Database.
You know how accounting works, right? A reply sent back to the NAS says "I received this, all is good". No reply sent back tells the NAS "it didn't get through, send it again". So by not responding, the NAS will keep re-sending the packet, *until* you respond.
Will it be possible on freeRADIUS 3.0.13?
Likely with do_not_respond. But it's not a good idea. -- Matthew
Hi, It's not like that NAS keep resending unitl radiud responds , it's very much in control normally 3 retries are configured at Nas. For your case you can log sql query via sql_log module and to reply or not can be controlled via setting return codes You can also Handle the Nas retransmissions by keeping optimal cleanup time so that radius holds one request and consider RTs as duplicate and discard them On Fri, Mar 8, 2019, 9:54 PM Matthew Newton <mcn@freeradius.org> wrote:
On Fri, 2019-03-08 at 19:58 +0530, Raghu nathan wrote:
We have the setup to update the postgreSQL database for START and STOP accounting request and its working fine.
I would like to have an option to make freeRADIUS not to send reply for any accounting messages but accounting request should get logged in Database.
You know how accounting works, right?
A reply sent back to the NAS says "I received this, all is good".
No reply sent back tells the NAS "it didn't get through, send it again".
So by not responding, the NAS will keep re-sending the packet, *until* you respond.
Will it be possible on freeRADIUS 3.0.13?
Likely with do_not_respond. But it's not a good idea.
-- Matthew
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Discarding accounting is not my experience with most NASes I have worked with. They will keep on retrying until they get a response for STARTS and especially STOPS and not give up after 3 attempts unless you explicitly configured it on the NAS to discard STOPS. If you have configured the NAS to discard accounting then sure if that is what you wanted. But a NAS normally expects a response to EVERY message it sends and when it doesn't get a response it will keep on retrying. Such as if it has a round-robin configuration with multiple radius server endpoints it would typically give up on one, and then try another. But ultimately it is entirely the control of the NAS and the Radius server no matter what variant it is should always respond to any requests it gets unless the shared secret is wrong and it has been configured not to reply. To have a Radius server not respond to valid accounting messages that were initiated by the NAS is a terrible idea. The few use cases where you don't want a response to a valid request is typically with proxied requests where you are sending the messages to multiple servers with enough redundancy so they will reconcile at some point. So in short I wouldn't do it.
Hi, In my experience I have never seen any Nas that keeps on trying as this concludes that it will keep trying even bypassing next interim update too.. If the guy who posted question wants to do this it's very much possible. ( Atleast you should try don't loose hope ) I have given the idea of how this can be achieved if need working configuration I can provide you On Sun, Mar 10, 2019, 2:13 PM Peter Lambrechtsen <peter@crypt.nz> wrote:
Discarding accounting is not my experience with most NASes I have worked with. They will keep on retrying until they get a response for STARTS and especially STOPS and not give up after 3 attempts unless you explicitly configured it on the NAS to discard STOPS.
If you have configured the NAS to discard accounting then sure if that is what you wanted.
But a NAS normally expects a response to EVERY message it sends and when it doesn't get a response it will keep on retrying. Such as if it has a round-robin configuration with multiple radius server endpoints it would typically give up on one, and then try another.
But ultimately it is entirely the control of the NAS and the Radius server no matter what variant it is should always respond to any requests it gets unless the shared secret is wrong and it has been configured not to reply.
To have a Radius server not respond to valid accounting messages that were initiated by the NAS is a terrible idea. The few use cases where you don't want a response to a valid request is typically with proxied requests where you are sending the messages to multiple servers with enough redundancy so they will reconcile at some point.
So in short I wouldn't do it. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (4)
-
arjun sharma -
Matthew Newton -
Peter Lambrechtsen -
Raghu nathan