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.