Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
radisud can't start if proto = udp is specified. radiusd uses udp ports in default configuration. It also supports tcp ports since freeradius 3.
If I explicitly define 'proto = tcp' for all default ports, it fails to start.
Version-Release number of selected component (if applicable):
freeradius-3.0.1-6.el7
How reproducible:
always
Steps to Reproduce:
1.set 'proto = udp' to "listen" section in /etc/raddb/sites-enabled/default and /etc/raddb/sites-enabled/inner-tunnel, add udp to section "home_server localhost" in /etc/raddb/proxy.conf
2.
3.
Actual results:
radiusd fails to start
Expected results:
radiusd is started
Additional info:
output from radiusd -X (I removed 'proto = udp' after each fail, it allowed me to get all error outputs):
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 0
proto = "udp"
/etc/raddb/sites-enabled/default[59]: TLS transport is not available for UDP sockets.
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = 127.0.0.1
port = 18120
proto = "udp"
/etc/raddb/sites-enabled/inner-tunnel[33]: TLS transport is not available for UDP sockets.
} # server inner-tunnel
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 0
limit {
max_connections = 16
lifetime = 0
idle_timeout = 30
}
}
listen {
type = "acct"
ipaddr = *
port = 0
proto = "udp"
/etc/raddb/sites-enabled/default[169]: TLS transport is not available for UDP sockets.
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, 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://rhn.redhat.com/errata/RHBA-2015-0438.html
Description of problem: radisud can't start if proto = udp is specified. radiusd uses udp ports in default configuration. It also supports tcp ports since freeradius 3. If I explicitly define 'proto = tcp' for all default ports, it fails to start. Version-Release number of selected component (if applicable): freeradius-3.0.1-6.el7 How reproducible: always Steps to Reproduce: 1.set 'proto = udp' to "listen" section in /etc/raddb/sites-enabled/default and /etc/raddb/sites-enabled/inner-tunnel, add udp to section "home_server localhost" in /etc/raddb/proxy.conf 2. 3. Actual results: radiusd fails to start Expected results: radiusd is started Additional info: output from radiusd -X (I removed 'proto = udp' after each fail, it allowed me to get all error outputs): radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 proto = "udp" /etc/raddb/sites-enabled/default[59]: TLS transport is not available for UDP sockets. radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = 127.0.0.1 port = 18120 proto = "udp" /etc/raddb/sites-enabled/inner-tunnel[33]: TLS transport is not available for UDP sockets. } # server inner-tunnel radiusd: #### Opening IP addresses and Ports #### listen { type = "auth" ipaddr = * port = 0 limit { max_connections = 16 lifetime = 0 idle_timeout = 30 } } listen { type = "acct" ipaddr = * port = 0 proto = "udp" /etc/raddb/sites-enabled/default[169]: TLS transport is not available for UDP sockets.