Can't connect to remote freeradius server
I've installed freeradius 1.1.5 and am able to run radtest successfully on the machine that freeradius is installed on. However, when I try to run radtest (or NTRadPing or radius test client) it is unable to connect to the server. Does anyone have any ideas? I do have the servers I'm running radtest on listed in clients.conf Here is the output from NTRadPing (IP address removed by me): Sending authentication request to server XX.XXX.XXX.XXX:1812 Transmitting packet, code=1 id=0 length=67 recvfrom() error, WSAGetLastError() = 10054 could not receive a response from the server Any suggestions would be appreciated.
A B wrote:
I've installed freeradius 1.1.5 and am able to run radtest successfully on the machine that freeradius is installed on. However, when I try to run radtest (or NTRadPing or radius test client) it is unable to connect to the server. Does anyone have any ideas? I do have the servers I'm running radtest on listed in clients.conf
first off, when you run radiusd -X (debug) do you see any requests coming into the server? is UDP port 1812 open on your hosts firewall (iptables, ipchains, pf, whatever your using) and ya you should prolly have an entry in clients.conf for the client you are testing from... Joe
This is the output of radiusd -x. It does say it's listening on 1812 for authentication and 1813 for accounting. Starting - reading configuration files ... Using deprecated naslist file. Support for this will go away soon. Module: Loaded exec rlm_exec: Wait=yes but no output defined. Did you mean output=none? Module: Instantiated exec (exec) Module: Loaded expr Module: Instantiated expr (expr) Module: Loaded PAP Module: Instantiated pap (pap) Module: Loaded CHAP Module: Instantiated chap (chap) Module: Loaded MS-CHAP Module: Instantiated mschap (mschap) Module: Loaded preprocess Module: Instantiated preprocess (preprocess) Module: Loaded realm Module: Instantiated realm (suffix) Module: Loaded SQL rlm_sql (sql): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked rlm_sql (sql): Attempting to connect to radius@localhost:/radius rlm_sql (sql): starting 0 rlm_sql (sql): Attempting to connect rlm_sql_mysql #0 rlm_sql_mysql: Starting connect to MySQL server for #0 rlm_sql (sql): Connected new DB handle, #0 rlm_sql (sql): starting 1 rlm_sql (sql): Attempting to connect rlm_sql_mysql #1 rlm_sql_mysql: Starting connect to MySQL server for #1 rlm_sql (sql): Connected new DB handle, #1 rlm_sql (sql): starting 2 rlm_sql (sql): Attempting to connect rlm_sql_mysql #2 rlm_sql_mysql: Starting connect to MySQL server for #2 rlm_sql (sql): Connected new DB handle, #2 rlm_sql (sql): starting 3 rlm_sql (sql): Attempting to connect rlm_sql_mysql #3 rlm_sql_mysql: Starting connect to MySQL server for #3 rlm_sql (sql): Connected new DB handle, #3 rlm_sql (sql): starting 4 rlm_sql (sql): Attempting to connect rlm_sql_mysql #4 rlm_sql_mysql: Starting connect to MySQL server for #4 rlm_sql (sql): Connected new DB handle, #4 Module: Instantiated sql (sql) Module: Loaded Acct-Unique-Session-Id Module: Instantiated acct_unique (acct_unique) Module: Loaded detail Module: Instantiated detail (detail) Module: Loaded System Module: Instantiated unix (unix) Module: Loaded radutmp Module: Instantiated radutmp (radutmp) Module: Loaded eap rlm_eap: Loaded and initialized type md5 rlm_eap: Loaded and initialized type leap rlm_eap: Loaded and initialized type gtc rlm_eap: Loaded and initialized type mschapv2 Module: Instantiated eap (eap) Initializing the thread pool... Listening on authentication *:1812 Listening on accounting *:1813 Ready to process requests. On 4/3/07, joe vieira <jvieira@clarku.edu> wrote:
A B wrote:
I've installed freeradius 1.1.5 and am able to run radtest successfully on the machine that freeradius is installed on. However, when I try to run radtest (or NTRadPing or radius test client) it is unable to connect to the server. Does anyone have any ideas? I do have the servers I'm running radtest on listed in clients.conf
first off, when you run radiusd -X (debug) do you see any requests coming into the server? is UDP port 1812 open on your hosts firewall (iptables, ipchains, pf, whatever your using) and ya you should prolly have an entry in clients.conf for the client you are testing from...
Joe - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
A B wrote:
This is the output of radiusd -x. It does say it's listening on 1812 for authentication and 1813 for accounting.
rlm_eap: Loaded and initialized type mschapv2 Module: Instantiated eap (eap) Initializing the thread pool... Listening on authentication *:1812 Listening on accounting *:1813 Ready to process requests.
That doesn't mean that you can access those ports from off of the box...did you check your firewall configuration to make sure those ports are accessible? easy test is to nmap -sU "whatever your freeradius box's ip is"
On 4/3/07, *joe vieira* <jvieira@clarku.edu <mailto:jvieira@clarku.edu>> wrote:
A B wrote: > I've installed freeradius 1.1.5 and am able to run radtest > successfully on the machine that freeradius is installed on. However, > when I try to run radtest (or NTRadPing or radius test client) it is > unable to connect to the server. Does anyone have any ideas? I do have > the servers I'm running radtest on listed in clients.conf > first off, when you run radiusd -X (debug) do you see any requests coming into the server? is UDP port 1812 open on your hosts firewall (iptables, ipchains, pf, whatever your using) and ya you should prolly have an entry in clients.conf for the client you are testing from...
Joe - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
A B -
joe vieira