yes im sure, in one terminal i've got the radiusd -X for debugging mode and in another one i do the radtest...and as i said before...for the localhost the output debugging shows how the user is authenticated and the packet is accepted...but the radtest for the AP doesnt respond and there is no output
and this is what happens with ps
[root@localhost raddb]# ps -ax | grep radiusd
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.7/FAQ
13879 pts/2 S+ 0:00 radiusd -X
13928 pts/1 R+ 0:00 grep radiusd
Date: Sat, 1 Oct 2011 19:23:22 -0500
Subject: Re: RE: Radius Server Doesn't Communicate AP
From: conesh@gmail.com
To: freeradius-users@lists.freeradius.org
Mmm weird, are you sure that FreeRadius is running when you test it?
Ps -ax | grep radiusd
Saludos
Ing. Alfonso Alejandro Reyes Jimenez
El oct 1, 2011 7:15 p.m., "Alejandro Moreno" <
mamr901@hotmail.com> escribió:
>
>
> Nothing Happens...its already stopped, the firewall is disabled
> Date: Sat, 1 Oct 2011 18:58:35 -0500
> Subject: Re: RE: Radius Server Doesn't Communicate AP
> From:
conesh@gmail.com> To:
freeradius-users@lists.freeradius.org
>
> Ir seems yo be listening on the radius port.Please execute the following command and test it again:Service iptables stop ( all lower case)And let me know.Regards.Saludos
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html