Re: Ingoring unknown Client error.

[Gary McKinney]

Looks like the 'name' of the NAS in the 
clients.conf file is not correct or the shared (secret) password is not correct 
- careful of whitespace and non-printable characters in the clients.conf file or 
the PM3 - also, I think this is case sensitive as well...

gm..

  - Original Message - 
  From: 
  Alexander Lopez 
  
  To: [EMAIL PROTECTED] 
  
  Sent: Tuesday, June 29, 2004 10:40 
  PM
  Subject: Ingoring unknown Client 
  error.
  
  
  So I thought it was going to be 
  simple. Download, Complie install configure files and bam!! Radius, NOT 
  SO!!
  
  I am 
  running:
  [EMAIL PROTECTED] sbin]# `pwd`/radiusd 
  -v
  radiusd: FreeRADIUS Version 
  1.0.0-pre3, for host , built on Jun 28 2004 at 
  12:13:59
  
  When I start radiusd with 
  –X
  I get this when trying to 
  authenticate a dialup user from a Livingston PM3
  
  rad_recv: Access-Request packet 
  from host 216.22.88.240:1142, id=182, length=115
  Ignoring request from unknown 
  client 216.22.88.240:1142
  --- Walking the entire request 
  list ---
  Nothing to do. Sleeping 
  until we see a request.
  
  
  I have added the secret in the 
  clients.conf file, stopped and started the radiusd process. I have changed the 
  secret on the PM3 (just to make sure I knew what it 
  was)
  Funny thing is that the PM3 works 
  fine on my Sun box that I am trying to retire. (This is that last thing that 
  remains)
  
  This is what I have 
  done:
  
  Made sure that the PM3 is using 
  port 1812 (as per RFC)
  Made sure that the PM3 can ping 
  and has connectivity, (long shot, but wanted to rule the network 
  out)
  
  
  I don’t know what else to 
  check.. Do I just have a weird one??
  
  
  
  
  

Ingoring unknown Client error.

[Alexander Lopez]

So I thought it was going to be simple. Download, Complie
install configure files and bam!! Radius, NOT SO!!



I am running:

[EMAIL PROTECTED] sbin]# `pwd`/radiusd -v

radiusd: FreeRADIUS Version 1.0.0-pre3, for host , built on
Jun 28 2004 at 12:13:59



When I start radiusd with X

I get this when trying to authenticate a dialup user from a
Livingston PM3



rad_recv: Access-Request packet from host
216.22.88.240:1142, id=182, length=115

Ignoring request from unknown client 216.22.88.240:1142

--- Walking the entire request list ---

Nothing to do. Sleeping until we see a request.





I have added the secret in the clients.conf file, stopped
and started the radiusd process. I have changed the secret on the PM3 (just to
make sure I knew what it was)

Funny thing is that the PM3 works fine on my Sun box that I
am trying to retire. (This is that last thing that remains)



This is what I have done:



Made sure that the PM3 is using port 1812 (as per RFC)

Made sure that the PM3 can ping and has connectivity, (long
shot, but wanted to rule the network out)





I dont know what else to check.. Do I just have a weird
one??