Freeradius says it is listening on port 1812, but isn't

[Matt Harlum]

After my previous email I've successfully re-installed my custom config and am able to auth my clients again

Regards,
Matt Harlum

On 25/03/2010, at 12:11 AM, Gary Gatten wrote:

> If u really want 2 knw the issue, undo the changes one by one until it breaks again.
> 
> ----- Original Message -----
> From: freeradius-users-bounces+ggatten=waddell.com at lists.freeradius.org <freeradius-users-bounces+ggatten=waddell.com at lists.freeradius.org>
> To: FreeRadius users mailing list <freeradius-users at lists.freeradius.org>
> Sent: Wed Mar 24 04:56:19 2010
> Subject: Re: Freeradius says it is listening on port 1812, but isn't
> 
> Hi,
> 
> I believe the problem is now resolved
> 
> The only things I changed was that my hosts file was wrong, the IP for the servers FQDN was incorrect but I'm not sure this is what it was
> I also turned off ip forwarding with sysctl -w net.inet.ip.forwarding=0
> Even though natd, and the firewall have been disabled. must be a weird OSX thing
> 
> Sorry for wasting your time guys and thanks for the help
> 
> Regards,
> Matt Harlum
> 
> On 24/03/2010, at 8:27 PM, Matt Harlum wrote:
> 
>> On 24/03/2010, at 8:21 PM, Fajar A. Nugraha wrote:
>> 
>>> On Wed, Mar 24, 2010 at 3:51 PM, Matt Harlum <matt at cactuar.net> wrote:
>>>> Hi,
>>>> 
>>>> I'm running Freeradius 2.1.6 on MacOSX 10.5.7 on a Dual-G4 867Mhz PowerMac
>>>> 
>>>> Since march last year I've had 2.1.6 installed however it's been switched off for the last few months.
>>>> Recently I powered it back on and have run system updates etc and got to the point I am now
>>>> 
>>>> When I launch FreeRadius it says it is listening on *:1812 for auth however my AP is unable to connect,
>>> 
>>> "unable to connect" is the result. Many things can cause it, from
>>> incorrent radius IP/secret settings on AP to firewalls blocking
>>> packets.
>> 
>> Checked both which are correct, no firewalls enabled
>> 
>>> 
>>>> and trying telnet on port 1812 results in "Connection Refused"
>>> 
>>> you can't test UDP with telnet. Try the included radtest and radclient
>>> 
>> 
>> Ahh ok, I'll give those a try
>> 
>>>> 
>>>> I've tried reverting the configuration to default but it hasn't worked. running radiusd -x does not throw any errors
>>> 
>>> does it print incoming packets and process it?
>>> does tcpdump (or whatever packet capture tools you have) shows incoming packets?
>>> 
>> 
>> It doesn't show anything when connection attempts are made, I'll let you know how I go with netcat and the radtest tools
>> Thanks
>> 
>>> -- 
>>> Fajar
>>> -
>>> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>> 
>> 
>> -
>> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> 
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html