Bug 1115137

Summary:	radiusd listens on udp port even if proto = tcp is specified
Product:	Red Hat Enterprise Linux 7	Reporter:	David Spurek <dspurek>
Component:	freeradius	Assignee:	Nikolai Kondrashov <nikolai.kondrashov>
Status:	CLOSED ERRATA	QA Contact:	Eduard Benes <ebenes>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	dpal, ebenes
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	freeradius-3.0.4-0.1.rc2.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 10:20:16 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:

Description David Spurek 2014-07-01 16:34:01 UTC

Description of problem:
radiusd listens on udp port even if proto = tcp is specified.

radiusd -X output:
...
Listening on auth proto tcp address * port 1812 as server default
Listening on acct proto tcp address * port 1813 as server default
Listening on auth proto tcp address 127.0.0.1 port 18120 as server inner-tunnel
Opening new proxy address * port 1814
Listening on proxy address * port 1814
Ready to process requests.


[test]netstat -putna | grep radius
tcp        0      0 127.0.0.1:18120         0.0.0.0:*               LISTEN     9885/radiusd        
tcp        0      0 0.0.0.0:1812            0.0.0.0:*               LISTEN      9885/radiusd        
tcp        0      0 0.0.0.0:1813            0.0.0.0:*               LISTEN      9885/radiusd        
udp        0      0 0.0.0.0:1814            0.0.0.0:*                           9885/radiusd  


Version-Release number of selected component (if applicable):
freeradius-3.0.1-6.el7

How reproducible:
always

Steps to Reproduce:
1.set 'proto = tcp' to "listen" section in /etc/raddb/sites-enabled/default and /etc/raddb/sites-enabled/inner-tunnel, add tcp to section "home_server localhost" in /etc/raddb/proxy.conf
2.set 'status_check = none' to section "home_server localhost" in /etc/raddb/proxy.conf
3.netstat -putna | grep radius

Actual results:
port 1814 listens on udp


Expected results:
port 1814 listens on tcp


Additional info:

Comment 1 Dmitri Pal 2014-07-16 13:13:59 UTC

It might be by design. If so we will not fix it otherwise if it is a bug we will address. Giving ack.

Comment 3 Nikolai Kondrashov 2014-08-01 15:22:02 UTC

The UDP ports seem to be opened for receiving replies from the home server(s), even though its protocol is specified as TCP.

I've sent a question to freeradius-users asking if this is a correct behavior:
http://lists.freeradius.org/pipermail/freeradius-users/2014-August/073145.html

Comment 4 Nikolai Kondrashov 2014-08-04 12:29:45 UTC

This is now fixed in a commit to be included in the v3.0.4 release: https://github.com/FreeRADIUS/freeradius-server/commit/dda48abc7d016b4db0a93bdde53c3ba77be20df8

Comment 10 errata-xmlrpc 2015-03-05 10:20:16 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, 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