FreeRADIUS 2 not listening on right port

Michael Griego mgriego at
Fri May 16 06:45:43 CEST 2008

I did a little looking into this this evening.  This assessment looks  
to be correct as it looks to be related to compiler optimizations.   
With the optimizations disabled in, FreeRADIUS will start up  
on the correct port.  For the fr_socket function, gcc appears to be  
optimizing the arguments by sending them through the registers instead  
of the stack frame, but the "port" argument is being clobbered  
("optimized out") before the htons(port) call.  Specifically,  
according to a step-through with GDB, after the first function call in  
fr_socket (which is to socket()), the port variable is gone  
("optimized out").


On May 15, 2008, at 4:30 PM, Casartello, Thomas wrote:

> Fedora 9 did do a pretty big gcc version jump. Fedora 8 used 4.1.2,
> while 9 uses 4.3.0. BTW I tested it in Fedora 8 and it worked fine, so
> it's definitely a 9 issue.
> Thomas E. Casartello, Jr.
> Infrastructure Technician
> Linux Specialist
> Department of Information Technology
> Westfield State College
> Wilson 105-A
> (413) 572-8245
> E-Mail: tcasartello at
> Red Hat Certified Technician (RHCT)
> -----Original Message-----
> From:
> at
> [ at lists.freeradius
> .org] On Behalf Of Alan DeKok
> Sent: Thursday, May 15, 2008 4:22 PM
> To: FreeRadius users mailing list
> Subject: Re: FreeRADIUS 2 not listening on right port
> Hoggins! wrote:
>> I'm running FC9, by the way... maybe that explains this sudden amount
> of
>> same problems, since the FC9 release was on tuesday.
>  Maybe someone running FC9 could try "debugging" the problem.
>  I haven't run a redhat-based system for *years*.
>  Since this works on every other system on the planet, it sounds  
> *very*
> much like an issue in FC9.
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
> -
> List info/subscribe/unsubscribe? See

More information about the Freeradius-Users mailing list