RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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