Freeradius says it is listening on port 1812, but isn't
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, and trying telnet on port 1812 results in "Connection Refused" I've tried reverting the configuration to default but it hasn't worked. running radiusd -x does not throw any errors Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests. Anyone have any ideas as to why this would be happening all of a sudden? perhaps the system updates broke it? Regards, Matt Harlum
Am 24.03.2010 um 09:51 schrieb Matt Harlum:
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, and trying telnet on port 1812 results in "Connection Refused"
I've tried reverting the configuration to default but it hasn't worked. running radiusd -x does not throw any errors
Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Listening on proxy address * port 1814 Ready to process requests.
Anyone have any ideas as to why this would be happening all of a sudden? perhaps the system updates broke it?
Have you checked firewalls and such? Perhaps you can also check with tools like tcpdump if the packets arrive on the computer where freeradius is running. Also perhaps check that the computer has really the IP address or name that you think it has and that the IP or name is really used by the AP.
Regards, Matt Harlum
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Have a nice day! Nicolas Goutte extragroup GmbH - Karlsruhe Waldstr. 49 76133 Karlsruhe Germany Geschäftsführer: Stephan Mönninghoff, Hans Martin Kern, Tilman Haerdle Registergericht: Amtsgericht Münster / HRB: 5624 Steuer Nr.: 337/5903/0421 / UstID: DE 204607841
On Wed, Mar 24, 2010 at 3:51 PM, Matt Harlum <matt@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.
and trying telnet on port 1812 results in "Connection Refused"
you can't test UDP with telnet. Try the included radtest and radclient
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? -- Fajar
On 24/03/2010, at 8:21 PM, Fajar A. Nugraha wrote:
On Wed, Mar 24, 2010 at 3:51 PM, Matt Harlum <matt@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
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@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
participants (3)
-
Fajar A. Nugraha -
Matt Harlum -
Nicolas Goutte