Hi people...

I had a similar problem when I tried out the freeradius-1.0.0-pre1 build
with fedora core 2... whenever I try to get my cisco AP to auth with
freeradius, I get the same unknown client message, and the IP is already
added in the clients.conf file...

Localhost works though, ports are configured... does anybody know why?
Perhaps I erred at some point of the installation?  But when I put it
back to 0.9.3, it worked fine...


Tim.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
prabhdeep
Sent: Monday, June 14, 2004 10:58 PM
To: [EMAIL PROTECTED]
Subject: (no subject)

Thanks Thor,

I tried 0.0.0.0/1, but it still does not work... I keep getting
following 
messages.
Just curious what the networking standard... I thought it was 0/8/16/24
or 
is it 1/8/16/24?

rad_recv: Accounting-Request packet from host 192.168.0.121:1024,
id=243, 
length=141
Ignoring request from unknown client 192.168.0.121:1024
--- Walking the entire request list ---
Nothing to do.  Sleeping until we see a request.
rad_recv: Access-Request packet from host 192.168.0.121:1024, id=206, 
length=228
Ignoring request from unknown client 192.168.0.121:1024

Thanks again.

prabh





 > Hi,
 >
 > How can one allow any NAS client to be authenticated as long as
secret
matches?
 >

client 0.0.0.0/1 {
     ...
}
client 128.0.0.0/1 {
     ...
}

 > 0.0.0.0/0 does not work in clients.conf.... there does not seem to be
any
 > default entry that I can set....
 > something like "if the IP does not match then use this".
 >
 > Thannk.
 >
 > with regards,
 > prabh
 >


- 
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html



-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to