Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10448 - [freeradius 2.0.4-1] radiusd binds to incorrect ports
Attached to Project:
Community Packages
Opened by Michael Gwin (oksijun) - Monday, 19 May 2008, 12:37 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 28 May 2008, 21:50 GMT
Opened by Michael Gwin (oksijun) - Monday, 19 May 2008, 12:37 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 28 May 2008, 21:50 GMT
|
DetailsDescription:
The radiusd daemon binds to incorrect and arbitrary ports when run. For example: Listening on authentication address * port 40996 Listening on accounting address * port 34698 Listening on proxy address * port 52645 Ready to process requests. The ports should be 1812 and 1813, not sure about the proxy one, I don't use this feature normally. Additional info: * package version(s) freeradius-2.0.4-1 * config and/or log files etc. Default config files (/etc/raddb/*) The relevant section of /etc/raddb/radiusd.conf (comments removed) is: -------------- listen { type = auth ipaddr = * port = 0 } listen { ipaddr = * port = 0 type = acct } --------------- /etc/services contains: $ grep radius /etc/services radius 1812/tcp radius 1812/udp radius-acct 1813/tcp radacct radius-acct 1813/udp radacct Steps to reproduce: Start radiusd. Result is the same whether it's run in debug mode or not or whether the ip address and port are given on the command line or not. |
This task depends upon
# Port on which to listen.
# Allowed values are:
# integer port number (1812)
# 0 means "use /etc/services for the proper port"
from radiusd.conf.in
I think it is an upstream bug.
http://bugs.freeradius.org/show_bug.cgi?id=560