I tried hardcoding them in the listen section. Same result. Thomas E. Casartello, Jr. Infrastructure Technician Linux Specialist Department of Information Technology Westfield State College Wilson 105-A (413) 572-8245 E-Mail: [EMAIL PROTECTED]
Red Hat Certified Technician (RHCT) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] .org] On Behalf Of Alan DeKok Sent: Thursday, May 15, 2008 2:16 PM To: FreeRadius users mailing list Subject: Re: FreeRADIUS 2 not listening on right port Casartello, Thomas wrote: > Compiling from source did NOT solve the problem. It looks like Fedora is broken. The server code does this: if (port == 0) { call system function to look up "radius" port in /etc/services if (found ) { port = port found in /etc/services } else { port = 1812 } } The only way I can see it choosing "random" ports is if the lookup in /etc/services returns "found", with a random port. I suggest hard-coding the port numbers (1812/1813) into the "listen" sections. Maybe also see if 'radius" and "radacct" are defined in /etc/services. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
