Unable to get freeradius server and client to communicate
Server is run in debug mode (radiusd -X) The following is entered in the clients.conf file: client erx.radius-src-ipaddr { secret = juniper nastype = other shorname = ERX1 } -------------------------------- Using netstat the server appears to be listenting on correct UDP port 1812 [root@freerad raddb]# netstat -a | grep radius udp 0 0 *:radius *:* udp 0 0 *:radius-acct *:* -------------------------------- Start Radius with : radiusd -X (debug mode) shows server listening on 1812 client erx.radius-src-ipaddr { require_message_authenticator = no secret = "juniper" nastype = "other" } ... adding new socket proxy address * port 38660 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 authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. Testing local to server works correctly but when I test from NAS (ERX) there is no output observed in the debug window (radiusd -X). I used tcpdump to confirm that packets are reaching the server. Any help would be greatly appreciated...
Haroon Abraham wrote:
Server is run in debug mode (radiusd -X) The following is entered in the clients.conf file:
client erx.radius-src-ipaddr { secret = juniper nastype = other shorname = ERX1 }
Why? Use the format which is in the examples. Add an "ipaddr" field.
Testing local to server works correctly but when I test from NAS (ERX) there is no output observed in the debug window (radiusd -X). I used tcpdump to confirm that packets are reaching the server.
Any help would be greatly appreciated...
Ask your OS why it's blocking packets to the server. You probably have a firewall set up. Alan DeKok.
On Sat, Jan 28, 2012 at 3:41 AM, Alan DeKok <aland@deployingradius.com>wrote:
Haroon Abraham wrote:
Server is run in debug mode (radiusd -X) The following is entered in the clients.conf file:
client erx.radius-src-ipaddr { secret = juniper nastype = other shorname = ERX1 }
Why? Use the format which is in the examples. Add an "ipaddr" field.
Testing local to server works correctly but when I test from NAS (ERX) there is no output observed in the debug window (radiusd -X). I used tcpdump to confirm that packets are reaching the server.
Any help would be greatly appreciated...
Ask your OS why it's blocking packets to the server. You probably have a firewall set up.
From the tcpdump output I can see that the packets are reaching the radius server but in the shell window running radiusd -X there is not output suggesting the request is not processes.
Any idean on how to confirm if there is a client key mismatch even though I have confirmed this and made the key simple ("juniper")? Thanks,
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Haroon Abraham wrote:
From the tcpdump output I can see that the packets are reaching the radius server but in the shell window running radiusd -X there is not output suggesting the request is not processes.
Any idean on how to confirm if there is a client key mismatch even though I have confirmed this and made the key simple ("juniper")?
What I said was:
Ask your OS why it's blocking packets to the server. You probably have a firewall set up.
Read the response AGAIN before asking any more questions. Think about it. Do what it says. Alan DeKok.
participants (2)
-
Alan DeKok -
Haroon Abraham