This question maybe a bit off from RADIUS, but is there a way to limit NAS or RADIUS to send only one access-request/access-accept in a single dial attempt? i am connecting via PPPoE. I can see from RADIUS logs receiving multiple access-request thus it is also giving multiple access-accept. How do i prevent this?

By configuring the NAS correctly... FreeRADIUS is behaving exactly as the standards say it should, see RFC 2865 and RFC 5080 regarding duplicate packets and the response cache.

Coz it is causing an issue "connection is terminated because the remote server did not respond in a timely manner". Then I have to redial again coz the IP does not get assigned to the client.

No.... it's not causing that, thats a result of either a backend database being slow to respond, and lossy link between the RADIUS server and the NAS, or the timeout period on the NAS being set too low. This is absolutely not a FreeRADIUS issue, it's a problem with your NAS. -Arran Arran Cudbard-Bell a.cudbardb@freeradius.org RADIUS - Half the complexity of Diameter

On Tue, Sep 6, 2011 at 3:26 PM, Det Det <det.explorer@yahoo.com> wrote:

Hi, This question maybe a bit off from RADIUS, but is there a way to limit NAS or RADIUS to send only one access-request/access-accept in a single dial attempt?

You're looking at things the wrong way. It's like you're on a beach, and there's a big sign saying "no swimming" because the beach is infested with jellyfish, but you decide to swim anyway. And then when the jellyfish stings you asked "how to make it so it doesn't hurt".

i am connecting via PPPoE. I can see from RADIUS logs receiving multiple access-request thus it is also giving multiple access-accept. How do i prevent this? Coz it is causing an issue "connection is terminated because the remote server did not respond in a timely manner". Then I have to redial again coz the IP does not get assigned to the client.

I'm guessing what happens is something like this: - the NAS sends access-request - radius accepts the request, and consult whatever backend it uses (e.g. files, db, ldap, etc) - backend processing takes a long time - client sends the request again since radius hasn't respond - radius accepts the request again, and notice that it's a duplicate request - processing finally completes. since there are multiple request received, radius sends multiple response (and logs them as duplicates) OR - the NAS sends access-request - radius accepts the request, and consult whatever backend it uses (e.g. files, db, ldap, etc) - radius sends the response, but the response comes from different IP address then what the NAS expects - client sends the request again since it didn't receive expected response from the correct IP address - radius accepts the request again, notice that it's a duplicate request, and simply sends the response again If it's case #1, you need to fix the backed. Usually it involves indexing, fixing schemas/queries, upgrading hardware, and so on. If it's #2, the easiest way is to just register the radius's primary IP address in client's radius server list. Another alternative is to use "--with-udpfromto" when compiling freeradius. -- Fajar