Yes, I restarted it several times. 10.2.8.150 is the AP's address. I guess there is nothing wrong with the AP. Just a moment ago, I noticed that I can't start radiusd daemon with 'service radiusd start' command. It gives the following error: [root@moe raddb]# service radiusd start Starting RADIUS server: Tue Feb 27 21:44:38 2007 : Info: Starting - reading configuration files ... 6490:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:632:Expecting: CERTIFICATE 6490:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:632:Expecting: CERTIFICATE 6490:error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib:ssl_rsa.c:534: [FAILED] But I can start it with 'radiusd -X' Can the prooblem be related to that? By the way, I have signed a new certificate to be used in radius. But it seems okay. Thanks for any help, Onur. A.L.M.Buxey@lboro.ac.uk wrote: Hi,
Hello, I have configured freeRadius server and a Cisco AP350. When I run the server in debug mode, it prints 'unknown client', although the client is explicitely defined in clients.conf. Output is: rad_recv: Access-Request packet from host 10.2.8.150:1058, id=31, length=143 Ignoring request from unknown client 10.2.8.150:1058 --- Walking the entire request list --- Nothing to do. Sleeping until we see a request.
clients.conf entity is: client 10.2.8.150 { secret = testing123 shortname = tnl2-network }
Any idea on what's wrong?
have you restarted FreeRADIUS after adding it to clients.conf? alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html --------------------------------- Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A.