Bug 1630684

Summary: correct receiving of multiple RADIUS packets through RadSec by freeradius
Product: Red Hat Enterprise Linux 7 Reporter: Milan Kerslager <milan.kerslager>
Component: freeradiusAssignee: Alex Scheel <ascheel>
Status: CLOSED ERRATA QA Contact: Filip Dvorak <fdvorak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: ascheel, mharmsen
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-29 20:20:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fix: correct receiving of multiple RADIUS packets through RadSec none

Description Milan Kerslager 2018-09-19 05:45:58 UTC 
Created attachment 1484574 [details]
fix: correct receiving of multiple RADIUS packets through RadSec

On a site with high load with FreeRADIUS v3 there is a bug with receiving multiple packet from incoming TLS (RadSec) connection that cause the site to fail authorisations for roaming users.

The patch has been verified by multiple admins of eduroam sites and tested in 3.0.12, 3.0.14 and 3.0.15 release.

The bug has been reported upstream and accepted in 3.0.16 release:

  https://github.com/FreeRADIUS/freeradius-server/pull/2106
  https://github.com/FreeRADIUS/freeradius-server/pull/2107

There is a workaround to set lifetime to 600 sec on smaller sites:
https://github.com/CESNET/ansible-freeradius/blob/master/templates/tls.j2#L49

Also there is a bug in 3.0.17 released on Apr 2018 so using latest version is not a solution: https://github.com/FreeRADIUS/freeradius-server/issues/2270
Comment 2 Nikolai Kondrashov 2018-09-19 09:06:08 UTC 
Thank you for the thorough report and explanation, Milan. We'll see if we can incorporate the fix in one of our future releases. If you're a customer, or know a customer affected by this, make sure our support is aware of the issue to speed up resolution.
Comment 22 errata-xmlrpc 2020-09-29 20:20:36 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: freeradius security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:3984