Thanks, turns out to be what you have mentioned above Alan " shared secret" another issue in my newly installed FreeRADIUS Version 3.0.4, i do not see detail file is created although I have enabled in sites-enabled/default file. This server is just act as an proxy i.e forwards realms to remote home servers. I copied from my version 2 radius server proxy.conf and clients.conf , doing radiusd -XC tell me OK. Off course all the server ip and port listen are moved to sites-enabled/default file. are there any specific change that I have to make in version 3.0.4 just act radius server as an proxy ? K On Mon, Dec 8, 2014 at 5:48 PM, Alan DeKok <aland@deployingradius.com> wrote:
On Dec 8, 2014, at 12:01 PM, Khapare Joshi <khapare77@gmail.com> wrote:
I testing freeradius 3 version for upgrade our old version 2 freeradius server.
Local auth works well but when I need to proxy realm I always got "no response from the server", I spoke to the guy who look after the remote radius server and he confirms it is running.
my version 2 configuration is working well though.
Version 3 does RADIUS correctly.
this is what i get in debug mode:
Unfortunately, that’s not relevant. What matters is why the *home* server doesn’t respond. For that, look at the logs on the home server.
As with *all* of these issues, the problem is the same:
- not listing the IP of the client in the home server - not using the correct shared secret
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html