Radius Server Doesn't Communicate AP

yzy-oui-fi yzy-oui-fi at hotmail.fr
Mon Oct 3 02:22:16 CEST 2011


Le dimanche 02 octobre 2011 à 22:03 +0000, Alejandro Moreno a écrit :
> Ok, first of all, not everybody has the resources to afford an
> "expert" to do something...
> besides, this is a university project, is not something that im doing
> for a company or something, hence im not getting an expert...thats the
> reason im in a forum, this is what they are for...otherwise i would
> have got an expert and not posting in forums
> 
> anyway...if someone wants to help me...this is what i got
> 
> my router is a ENHWI-N3, i've got its firewall disabled
> it's got DHCP server enabled, wan //dinamic ip address
> Lan// 192.168.0.1 subnet mask 255.255.255.0
> i tried to ping Centos ip adress 192.168.75.129 from the AP but is
> unreachable
> but when i do the ping to 127.0.0.1 it's alive
note: 
- doing a ping to 127.0.0.1 will always reply from any devices(in your
case the ENHWI-N3).
- LAN IP 192.168.0.1 with subnte allow you to communicate with local ip
from 192.168.0.1 to 192.168.0.254. 192.168.75.129 is out of range, so it
sounds logical to not havae any reply from ping! change your AP IP to
something like 192.168.75.1 will help you to get reply from your radius
server.
> so the radius server should it be 192.168.75.129 or 127.0.0.1?
> 
> In clients.conf i have
> 
> client 192.168.0.1 {
> 
> secret = xxxx
> nastype= other     
> }
> 
> 
> i did a nc -zu 192.168.01 1800 1820 and 1812 its working fine its
> succeeded 
> and i did it for 127.0.0.1 too and its fine.
> 
> so..this is it...i appreciate if someone could tell me what could it
> be wrong..
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html





More information about the Freeradius-Users mailing list